External USB HD works at first, then stops after creating FS??
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
External USB HD works at first, then stops after creating FS??
Hi all,
I'm having a strange problem with a 320 GB IDE hard drive in a USB enclosure...
Quick background: I'm running Ubuntu 7.04 server edition, kernel 2.6.20-15-server. When I first booted up the computer, with the new HD attached, it worked fine and assigned the external USB drive to /dev/sdb.
So I created a single primary Linux partition via fdisk - no problem. Then I created an ext3 filesystem by typing 'sudo mkfs.ext3 /dev/sdb1'. That also completed successfully, no problem.
Then I rebooted the computer. Here is where the problems started. After the reboot, I noticed that there was no /dev/sdb or /dev/sdb1 device anymore. I looked in the syslog and found this:
---
usb 4-3: device descriptor read/64, error -71
usb 4-3: new high speed USB device using ehci_hcd and address 3
usb 4-3: device descriptor read/64, error -71
usb 4-3: device descriptor read/64, error -71
usb 4-3: new high speed USB device using ehci_hcd and address 4
usb 4-3: device not accepting address 4, error -71
usb 4-3: new high speed USB device using ehci_hcd and address 5
usb 4-3: device not accepting address 5, error -71
---
I rebooted several times, leaving the USB hard drive plugged in and turned on, and this kept happening. The weird part is, if I turn the drive off and on again, then it works and /dev/sdb and /dev/sdb1 show up in my filesystem.
I decided to go back and redo it, rebooting at each stage. Here are the results:
Booting up with the drive empty and unpartitioned: Works, /dev/sdb is there
Create Linux primary partition (320 GB), reboot: Works, /dev/sdb and /dev/sdb1 are there
Create ext3 filesystem, reboot: Doesn't work! This is where I get the errors listed above. Turning the drive off and on again fixes the problem.
Does anyone have any idea what could cause this? I wouldn't mind having to turn the drive off and on but this is going to be a server machine and if I have to reboot it remotely, all my files on the drive will be inaccessible. Any ideas would be greatly appreciated!
I remember a similar problem in an old Fedora release. The issue there was that the system wasn't allowing enough time for the device to settle at boot. It seems that some external devices take a few extra seconds to spin up at boot, but the system skips them when they don't respond.
You can test this by recreating the problem, then:
In case anyone was interested, the cause seems to be that the USB enclosure I was using was a piece of junk. I bought a new I/O Magic one at Staples yesterday, put my hard drive in there, and it seems to be working flawlessly now!
I occasionally still get the "error -71" message at bootup, but the drive still gets recognized eventually.
Updating to a more current udev and/or kernel should correct the problem. It looks like there is a bug report covering this issue in the Suse Bugzilla.
Cool, thanks, that's probably the issue.
Well, it is unfixed in lates SuSE with latest updates.
Me, personally, I'd not install that libs from "beta" something.
Hopefully an official update will come through in the next weeks.
Cheers, Tom.
Hmm, mounting worked now, as reported, but the 25G copy job
I started yesterday evening was still running this morning,
so there must be a huge performance penalty to using this
"workaround"...
It sounds like the port you are using is not running at USB 2.0 speed. When the device was plugged in do you see a "high speed" message in the log? For example:
Quote:
new high speed USB device using ehci_hcd and address 3
Yes, all worked well with previous kernels, so it can't be hardware.
Please see above, I'd think that using "full speed" instead
of "high speed" is the penalty for unloading the module.
With with "high speed" it doesn't work at all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.