The last friday we had a power outage in our lab. When booting our Jetson-TK1 kit, we discovered that there were file system errors in the root fs (/dev/mmcblk0p1).
Following the specifications here:
we then read out the entire system.img partition, mounted it, run e2fsck -c -f -p, and re-write it back to the Jetson-TK1.
While this temporarily fixed the issues we were seeing, we still get a corrupted file system after 1-2 days of normal usage. It was evident today, because we were no longer able to ssh into the Jetson-TK1 - our user was gone, and by checking the local display we found we had a lot of inode errors. Very interesting…
I think the flash memory is bad, but I was wondering if anyone can come with some suggestions / comments? I am currently running badblocks -w /dev/mmcblk0p1 directly on the Jetson-TK1 (booting from SDMMC), but I am open for input.