[NotInControl]

Originally Posted by codedr

Try running 'fsck' on the root filesystem as root.
# fsck -f /dev/root

When the error occurs, the fs will already be mounted read only.
The -f flag should force a check even though its an ext4 fs.

Ok. I will try to run that command and report back. Everytime the FS goes read-only, a reboot does not fix. It continues to start-up as read-only. Trying to remount only automatically goes back t read-only. I need to re-flash the drive and then will try again. I was going to try and boot off an SD card.

Originally Posted by Tom Bottiglieri

We had pretty bad luck with the reliability of the TK1. At one point, we had 2 that flat out refused to boot. I'd be careful if you decide to run this on your robot

Thanks for the warnings Tom, any idea what caused your failures? We used a beaglebone in the past with much success, but learned that the rootfs needs to be read-only to avoid intermittent power shutdowns from corrupting the disk. Typically we plan to run our TK1 in read-only mode, but right now, we keep it in write mode because were actively developing on it.

What did you do with the 2 that didn't boot. Did you contact NVIDIA somehow?

Originally Posted by marshall

Ouch...

We have not had those issues. Would highly recommend putting them in a case of some sort though. We also ran ours off of the VRM last year if that helps.

The TX1 is proving to be more of a challenge however... It seems very prone to power fluctuations.

I do have it in a case, we modified the 3D printed NVIDIA case, and keep it in there.