Corrupted SD cards 2

Board has been powered on over the weekend.

[252264.475965] EXT4-fs warning: 26881 callbacks suppressed
[252264.475972] EXT4-fs warning (device nvme0n1p1): dx_probe:767: inode #2762639: lblock 0: comm nvmemwarning.sh: error -5 reading directory block
[252264.494772] EXT4-fs warning (device nvme0n1p1): dx_probe:767: inode #2762639: lblock 0: comm nvmemwarning.sh: error -5 reading directory block
[252264.508049] EXT4-fs warning (device nvme0n1p1): dx_probe:767: inode #2762639: lblock 0: comm nvmemwarning.sh: error -5 reading directory block
[252264.521321] EXT4-fs warning (device nvme0n1p1): dx_probe:767: inode #2762639: lblock 0: comm nvmemwarning.sh: error -5 reading directory block
[252264.528056] EXT4-fs warning (device nvme0n1p1): dx_probe:767: inode #1835009: lblock 0: comm gmain: error -5 reading directory block
[252264.534600] EXT4-fs warning (device nvme0n1p1): dx_probe:767: inode #2762639: lblock 0: comm nvmemwarning.sh: error -5 reading directory block
[252264.560236] EXT4-fs warning (device nvme0n1p1): dx_probe:767: inode #2762639: lblock 0: comm nvmemwarning.sh: error -5 reading directory block
[252264.573500] EXT4-fs warning (device nvme0n1p1): dx_probe:767: inode #2762639: lblock 0: comm nvmemwarning.sh: error -5 reading directory block
[252264.588396] EXT4-fs warning (device nvme0n1p1): dx_probe:767: inode #2760658: lblock 0: comm nvmemwarning.sh: error -5 reading directory block
[252264.588414] EXT4-fs warning (device nvme0n1p1): dx_probe:767: inode #2760658: lblock 0: comm nvmemwarning.sh: error -5 reading directory block
[252269.466195] ------------[ cut here ]------------
[252269.471093] WARNING: CPU: 3 PID: 2152 at fs/fs-writeback.c:2307 __mark_inode_dirty+0x49c/0x4b0
[252269.480265] ---[ end trace 8298af14253c9882 ]---

I can’t check the full dmesg since nothing works anymore.

Is this an SD card or an NVMe? The messages suggest a failed NVMe. Regardless of whether it is SD or NVMe, it looks to be corrupted beyond usefulness. This might be an actual device failure, or it might be caused by a lot of improper shutdowns (that much corruption is unlikely from a single improper shutdown unless it was done during a very large write). If it is possible to put this device on a Linux host PC, then you might be able to get more information, but I will suggest that it isn’t possible to save the data even if the device is still functioning. There are ways to preserve this with dd and you might get the ability to investigate through that, but you will be flashing again.

Solid state devices do fail even under normal circumstances. Power spikes can destroy devices. Sometimes a power brownout/undervoltage is the worst circumstance because a device will continue functioning while data just corrupts worse and worse.

There is known issue on Orin Nano devkit sdcard module. Please boot from usb instead.

Sorry. This was with NVMe. Funny thing, after a reboot it managed to fix itself. There were no improper shutdowns, as I said the device was just powered on over the weekend.

It sounds like the bug @WayneWWW mentions might be a problem with a recurring corruption if you are booting from NVMe. If the “repaired” device continues to re-corrupt you might want to post a thread again specific to that bug.

1 Like

If this is from nvme, then it is separate one which may not be a common bug. No other users reporting this.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.