Posts: 2
Joined: Tue Nov 26, 2013 9:52 pm


Sat Nov 30, 2013 2:39 am

Thanks for the prompt replies.

Actually, I think I have resolved my problem. Before I could implement your
advice, I barely bumped the USB hub and the power failed. That led to a
corrupt SD card, and time spent rebuilding to the point where I could try
setting up to run my Pi from an ext HD. Once I replaced what was obviously a
flaky USB Hub, the problems I described in my first post went away.

So, again, thank you all so much for your attempts to help me. I do think,
however, that it was all down to a faulty USB Hub. For anyone who has similar
issues, if you can, swap out your hub, just to be sure that's not the problem.

Thanks again!

(Cross-posted to:
The Raspberry Pi Hobbyist: Running From an External Hard Drive ... drive.html)

User avatar
Posts: 114
Joined: Thu Sep 20, 2012 4:52 pm
Location: Williamsburg, VA, USA
Contact: Website


Sat Nov 30, 2013 2:53 pm

The poster that I was responding to now reports that his problem seems to have been caused by a flaky USB hub.
- Ted B. Hale

Posts: 6
Joined: Tue Aug 20, 2013 1:33 am


Sun Apr 12, 2015 2:24 am

When I did a sudo e2fck /dev/sda1, got thousands of errors, yes all of them, did all proper commands. Went to reboot and got hundreds of errors. boots to command line with no wifi. All corrupted.

Posts: 79
Joined: Fri Jul 26, 2013 8:55 pm


Tue Apr 19, 2016 5:26 am

I know this is an old thread, but still useful. It would be best to actually specify the uuid via UUID="xxxxxxxxxxx" in fstab. If you were to plug in another USB device such as a USB thumb drive, when you boot again you don't know which it will try to mount first, so /dev/sda1 may have suddenly become the USB thumb drive and guess what - no boot! By specifying the UUID instead you can be sure it is always use the correct drive.

This same change applies to cmdline.txt - changes /dev/sdax to UUID="xxxxxxxxxxxx" and it will always try to boot using the hard disk.

Return to “Beginners”