My BBB card keeps getting a corrupt file system. I see this from detaching the BBB and using a serial debugger cable. Output below.
I can reload the image from a SD card, and after a few reboots, it seems to work. My problem is that after another 5-10 startups, the currupsion is back, and the ROV will not start.
I suspect I’ll have to get another BBB. Can this be confirmed? Or is there anything else I can do, like formatting the internal drive? (Unless that is already done through the flash reload)
I will try to work with the OS running of the SD card for a while, but I’d really like to get this back up running…
- The Blue User LEDs are flashing a bit, but no cyclone
- The main LEDs (headlights) are flashing on and off
- The output from the serial debugger looks like this:
[ ok ] Setting parameters of disc: (none).
[ 8.126835] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[…] Checking root file system…fsck from util-linux 2.20.1
rootfs contains a file system with errors, check forced.
rootfs: Unattached inode 37570
rootfs: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck died with exit status 4
failed (code 4).
[…] An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be perfo[FAILin maintenance mode with the root filesystem mounted in read-only mode. … failed!
[…] The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. After performing system maintenance, press CONTROL-D[warnerminate the maintenance shell and restart the system. … (warning).
Give root password for maintenance
(or type Control-D to continue):