USB problems..

[UnaClocker]

This has happend twice now, my USB hard drive seems to lock up. Here's the syslog output from the time it first noted a problem.

Code:

Jan  7 19:10:38 sheeva kernel: usb 1-1: reset high speed USB device using orion-ehci and address 7
Jan  7 19:10:49 sheeva kernel: usb 1-1: reset high speed USB device using orion-ehci and address 7
Jan  7 19:11:25 sheeva kernel: usb 1-1: reset high speed USB device using orion-ehci and address 7
Jan  7 19:11:26 sheeva kernel: usb 1-1: device descriptor read/64, error -71
Jan  7 19:11:26 sheeva kernel: usb 1-1: device descriptor read/64, error -71
Jan  7 19:11:26 sheeva kernel: usb 1-1: reset high speed USB device using orion-ehci and address 7
Jan  7 19:11:26 sheeva kernel: usb 1-1: device descriptor read/64, error -71
Jan  7 19:11:26 sheeva kernel: usb 1-1: device descriptor read/64, error -71
Jan  7 19:11:27 sheeva kernel: usb 1-1: reset high speed USB device using orion-ehci and address 7
Jan  7 19:11:27 sheeva kernel: usb 1-1: device not accepting address 7, error -71
Jan  7 19:11:27 sheeva kernel: usb 1-1: reset high speed USB device using orion-ehci and address 7
Jan  7 19:11:28 sheeva kernel: usb 1-1: device not accepting address 7, error -71
Jan  7 19:11:28 sheeva kernel: usb 1-1: USB disconnect, address 7
Jan  7 19:11:28 sheeva kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Jan  7 19:11:28 sheeva kernel: sd 1:0:0:0: [sda] Unhandled error code
Jan  7 19:11:28 sheeva kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
Jan  7 19:11:28 sheeva kernel: sd 1:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 73 3c 97 8f 00 00 40 00
Jan  7 19:11:28 sheeva kernel: end_request: I/O error, dev sda, sector 1933350799
Jan  7 19:11:28 sheeva kernel: usb 1-1: new high speed USB device using orion-ehci and address 8
Jan  7 19:11:28 sheeva kernel: usb 1-1: device descriptor read/64, error -71
Jan  7 19:11:28 sheeva kernel: usb 1-1: device descriptor read/64, error -71
Jan  7 19:11:28 sheeva kernel: usb 1-1: new high speed USB device using orion-ehci and address 9
Jan  7 19:11:29 sheeva kernel: usb 1-1: device descriptor read/64, error -71

At this point, the access light on my USB hard drive was on solid.. I've used this USB hard drive with PC based Linux servers for years, no problems. It's definitely not the drive. So I powered it down, and then powered it back up. I could not get it to mount.. This is why...

Code:

Jan  7 19:15:53 sheeva kernel: usb 1-1: new high speed USB device using orion-ehci and address 12
Jan  7 19:15:53 sheeva kernel: usb 1-1: configuration #1 chosen from 1 choice
Jan  7 19:15:53 sheeva kernel: scsi2 : SCSI emulation for USB Mass Storage devices
Jan  7 19:15:53 sheeva kernel: usb-storage: device found at 12
Jan  7 19:15:53 sheeva kernel: usb-storage: waiting for device to settle before scanning
Jan  7 19:15:58 sheeva kernel: scsi 2:0:0:0: Direct-Access     ST310003 33AS                  PQ: 0 ANSI: 2 CCS
Jan  7 19:15:58 sheeva kernel: sd 2:0:0:0: Attached scsi generic sg0 type 0
Jan  7 19:15:58 sheeva kernel: sd 2:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Jan  7 19:15:58 sheeva kernel: usb-storage: device scan complete
Jan  7 19:15:58 sheeva kernel: sd 2:0:0:0: [sdb] Write Protect is off
Jan  7 19:15:58 sheeva kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 38 00 00
Jan  7 19:15:58 sheeva kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
Jan  7 19:15:58 sheeva kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
Jan  7 19:15:58 sheeva kernel: sdb: sdb1
Jan  7 19:15:58 sheeva kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
Jan  7 19:15:58 sheeva kernel: sd 2:0:0:0: [sdb] Attached SCSI disk

It came up as SDB rather than SDA... That's a bit of a problem, I don't know of a way to make the machine mount that drive to the same place if the letters keep changing.. I'd like to resolve this without rebooting..
edit: Looks like I was able to get SDA back by shutting down all of the processes that used that drive, and umounting it while it was unplugged, then plugging it back in.. I really wonder why it's crashing like that though. That's gotta be hard on the EXT2 file system.

[pingtoo]

I have see this happen to me before but it is NSLU2 and X86, this is long time ago, at kernel level around 2.6.9 and 2.6.18. It always happen when I use the USB disk with a lots of I/O, especially with multiple processes access the usb disk concurrently.

Hope this help

[UnaClocker]

Good to know.. I'm on 2.6.32.2, and definitely using lots of I/O.. I have torrents downloading to it, it's streaming 720p to my PS3, and some smaller video to XBMC in the kids room. I was connect via smb to it from at least one of my PC's, but I don't think I was pulling any files at the time.. Hmm..

[Legolas]

Good to know.. I'm on 2.6.32.2, and definitely using lots of I/O.. I have torrents downloading to it, it's streaming 720p to my PS3, and some smaller video to XBMC in the kids room. I was connect via smb to it from at least one of my PC's, but I don't think I was pulling any files at the time.. Hmm..

Hi Unaclocker
   Wondering if you have found a solution to your problem?  I am not plagued by the exact same problem.
Please see the thread I have opened:

http://plugcomputer.org/plugforum/index.php?topic=1806.0

Your input would be most valuable.

[birdman]

It came up as SDB rather than SDA... That's a bit of a problem, I don't know of a way to make the machine mount that drive to the same place if the letters keep changing..

Don't mount it by device name (Windows uses letters!).
My fstab file has this:

Code:

LABEL=LinMax    /media/LinMax   ext3    users,noauto,exec

[Legolas]

It came up as SDB rather than SDA... That's a bit of a problem, I don't know of a way to make the machine mount that drive to the same place if the letters keep changing..

Don't mount it by device name (Windows uses letters!).
My fstab file has this:

Code:

LABEL=LinMax    /media/LinMax   ext3    users,noauto,exec

Thanks.  I should try this.  For now, connecting my HDD to a PC and making some writes to it and then
reconnecting to the Plug solved my problem.

[birdman]

Thanks.  I should try this.  For now, connecting my HDD to a PC and making some writes to it and then
reconnecting to the Plug solved my problem.

I suspect just the disconnect and reconnect did it with /dev/sda being free on the reconnect.
I should also have mentioned that the Label part is something you apply using

tune2fs -L LabelName /dev/sdx