Re: Unable to access 3TB USB drive via IB-351

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 24 Oct 2011, Simon Detheridge wrote:

> Hello,
> 
> I'm having trouble accessing a 3TB external drive. I have an IcyBox IB-351 series (IB-351StU3-B) external USB SATA enclosures. When I connect a 3TB external drive to my server (Ubuntu Server 10.04) and try to access it, it hangs completely. For example, running parted, mounting a partition, or running badblocks. It just hangs and I usually have to kill -9 the process.
> 
> It works just fine when I use the 750GB drive in the enclosure. The enclosure and drive work just fine with a 3TB drive when hooked up to a Windows PC (Server 2008R2 64-bit). I have tried on two different Ubuntu servers with completely different chipsets, and I see the same results.
> 
> I've only used prebuilt kernel binaries from Ubuntu, including some backports. I've tried: 3.0.0-12, 2.6.32-30, 2.6.32-34, and 2.6.38-11. Results were the same on all versions. All were 64-bit.
> 
> Usually when I connect the external drive, I see something like this in dmesg:
> 
> [685772.270020] usb 1-4: new high speed USB device using ehci_hcd and address 6
> [685772.426961] usb 1-4: configuration #1 chosen from 1 choice
> [685772.427386] scsi4 : SCSI emulation for USB Mass Storage devices
> [685772.427509] usb-storage: device found at 6
> [685772.427514] usb-storage: waiting for device to settle before scanning
> [685777.421648] usb-storage: device scan complete
> [685781.621724] scsi 4:0:0:0: Direct-Access     WDC WD30 EZRX-00MMMB0     80.0 PQ: 0 ANSI: 2
> [685781.622341] sd 4:0:0:0: Attached scsi generic sg3 type 0
> [685781.626581] sd 4:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
> [685781.627079] sd 4:0:0:0: [sdc] 5860533165 512-byte logical blocks: (3.00 TB/2.72 TiB)
> [685781.627827] sd 4:0:0:0: [sdc] Write Protect is off
> [685781.627831] sd 4:0:0:0: [sdc] Mode Sense: 00 06 00 00
> [685781.627834] sd 4:0:0:0: [sdc] Assuming drive cache: write through
> [685781.632076] sd 4:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
> [685781.633201] sd 4:0:0:0: [sdc] Assuming drive cache: write through
> [685781.633450]  sdc: unknown partition table
> [685781.652453] sd 4:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
> [685781.653577] sd 4:0:0:0: [sdc] Assuming drive cache: write through
> [685781.653828] sd 4:0:0:0: [sdc] Attached SCSI disk
> [685812.071907] usb 1-4: reset high speed USB device using ehci_hcd and address 6
> [685844.101896] usb 1-4: reset high speed USB device using ehci_hcd and address 6
> [685876.100648] usb 1-4: reset high speed USB device using ehci_hcd and address 6
> [685908.100650] usb 1-4: reset high speed USB device using ehci_hcd and address 6
> [685940.101897] usb 1-4: reset high speed USB device using ehci_hcd and address 6
> [685972.160666] usb 1-4: reset high speed USB device using ehci_hcd and address 6
> [685973.316165] sd 4:0:0:0: [sdc] Unhandled error code
> [685973.316170] sd 4:0:0:0: [sdc] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
> [685973.316175] sd 4:0:0:0: [sdc] CDB: Read(16): 88 00 00 00 00 01 5d 50 a3 00 00 00
> [685973.316188] end_request: I/O error, dev sdc, sector 5860532992

> Any ideas as to what I can do to make this work?

The best way to start is to get a usbmon trace.  There are instructions 
in the kernel source file Documentation/usb/usbmon.txt.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux