hi everyone,
I got a custom board in my hand with Jetpack3.3 TX2. Sometimes, dmesg output some filesystem error,but filesystem not crashed.
[ 306.149306] EXT4-fs (mmcblk0p1): error count since last fsck: 14
[ 306.155347] EXT4-fs (mmcblk0p1): initial error at time 1567760355: ext4_journal_check_start:56
[ 306.163996] EXT4-fs (mmcblk0p1): last error at time 1568605091: ext4_remount:4683
I have modify the USB lane mampping, from default 2 to 6, ODMDATA=0x3090000.
There is something output when doing “lspci”
00:01.0 PCI bridge: NVIDIA Corporation Device 10e5 (rev a1)
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a808.
Are these error logs critical or neglectable?
The corrupt filesystem should be considered a serious issue, although whatever is corrupt may be something you don’t need. Hard to say.
Normally one would use a clean shutdown of a system. As the filesystem syncs the journal is removed. In an unclean shutdown the journal remains. Then upon reboot, the journal is replayed in reverse to remove the uncommitted writes which would cause corruption. At some point the incorrect shutdown can produce errors which exceed the ability of the journal in protecting against corruption. This is the case for you…the journal is not able to correct for the numerous errors.
I see nothing wrong on the lspci, it just lists two devices. To see errors with advanced error reporting you’d need to use “sudo lspci -vvv”. However, unless mmcblk0p1 is mounted on a PCI device, then this isn’t going to be related to the filesystem (though malfunctioning PCI devices could cause an unclean shutdown).
Same for USB…unless mmcblk0p1 is mounted on USB, then this won’t be related to the filesystem corruption (but it could be a cause of unclean shutdown).
To complicate matters, if USB or PCI drivers are what is corrupt, then this might increase the unclean shutdowns and blame USB or PCI when it is really a corrupt driver. I doubt this is occurring, this is just a small possibility.
My advice: Clean install. Even if you could fsck and make the filesystem non-corrupt, this would still leave parts of the filesystem missing. Make sure shutdowns are clean. If a crash condition is causing failed shutdown, then find out what the cause is before continuing.