USB3-SATA-UASP1stops responding under heavy use


#1

After some time my USB3-SATA-UASP1stops responding. The led goes red/blue and stays there solidly. The drive gets quite hot. Is it recommended to use additional cooling when using a drive for an extended period of time?


#2

Hi Ryan,

Thanks for contacting Plugable Support, I’ll be able to help. There’s no need for any additional cooling when using the Plugable USB3-SATA-UASP1, it’s normal for the drives to feel hot to the touch. It can be surprising how hot but it is normal and hard drives are actually one of the major sources of heat in a system.

We’ve opted for an open design on the USB3-SATA-UASP1 to allow increased air flow without any additional cooling necessary.

It’s not normal for the drive to stop responding however, so let’s work on troubleshooting that issue. Can you say a bit more detail about what’s happening when the drive stops responding?

Is the drive in the middle of a backup? Is it idle? What operating system are running? Does the same thing happen on more than one drive?

Let me know these additional details and we’ll figure out the best next steps.

Thanks,
Jerome.


#3

I’m using linux, specifically Ubuntu 12.04.2 LTS.

What I’m actually doing is I’ve got 2 of docks with drives in them and I’m using rsync to consolidate files from one drive to the other so that I can have 1 full drive and one empty on. I’m using rsync to do the the transfer.

From dmesg logs it looks like there was a medium error and the device gets stuck. Yet if I power off the drive and let it sit to cool down and retry there’s no problem. I’m even using “rsync -c” which rereads every byte of data and make sure that the copies match. This is why I suspect a temperature issue.

Here seems to be the dmesg logs that correspond to what the OS is doing:

[172630.220074] usb 2-4: new high-speed USB device number 23 using ehci_hcd
[172630.364123] scsi29 : usb-storage 2-4:1.0
[172631.368199] scsi 29:0:0:0: Direct-Access Plugable USB3-SATA-UASP1 0 PQ: 0 ANSI: 6
[172631.368646] sd 29:0:0:0: Attached scsi generic sg4 type 0
[172631.373824] sd 29:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
[172631.374187] sd 29:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[172631.374190] sd 29:0:0:0: [sdb] 4096-byte physical blocks
[172631.375071] sd 29:0:0:0: [sdb] Write Protect is off
[172631.375076] sd 29:0:0:0: [sdb] Mode Sense: 43 00 00 00
[172631.375945] sd 29:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[172631.377309] sd 29:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
[172639.641115] sdb: sdb1
[172639.642946] sd 29:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
[172639.645199] sd 29:0:0:0: [sdb] Attached SCSI disk

[172853.789397] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[172976.312044] usb 2-1: new high-speed USB device number 24 using ehci_hcd
[172976.448352] scsi30 : usb-storage 2-1:1.0
[172977.451642] scsi 30:0:0:0: Direct-Access Plugable USB3-SATA-UASP1 0 PQ: 0 ANSI: 6
[172977.453199] sd 30:0:0:0: Attached scsi generic sg2 type 0
[172977.456143] sd 30:0:0:0: [sdd] Spinning up disk…ready
[172991.522410] sd 30:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16).
[172991.522775] sd 30:0:0:0: [sdd] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[172991.522779] sd 30:0:0:0: [sdd] 4096-byte physical blocks
[172991.523646] sd 30:0:0:0: [sdd] Write Protect is off
[172991.523650] sd 30:0:0:0: [sdd] Mode Sense: 43 00 00 00
[172991.524528] sd 30:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[172991.525644] sd 30:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16).
[172991.590459] sdd: sdd1
[172991.591631] sd 30:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16).
[172991.593513] sd 30:0:0:0: [sdd] Attached SCSI disk
[177683.920147] usb 2-4: reset high-speed USB device number 23 using ehci_hcd
[177715.024055] usb 2-4: reset high-speed USB device number 23 using ehci_hcd
[177746.000043] usb 2-4: reset high-speed USB device number 23 using ehci_hcd

[189338.960081] usb 2-4: reset high-speed USB device number 23 using ehci_hcd
[189369.936235] usb 2-4: reset high-speed USB device number 23 using ehci_hcd
[189400.976047] usb 2-4: reset high-speed USB device number 23 using ehci_hcd
[189432.016059] usb 2-4: reset high-speed USB device number 23 using ehci_hcd
[189462.992077] usb 2-4: reset high-speed USB device number 23 using ehci_hcd
[189493.968066] usb 2-4: reset high-speed USB device number 23 using ehci_hcd
[189494.101503] sd 29:0:0:0: [sdb] Unhandled error code
[189494.101507] sd 29:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
[189494.101510] sd 29:0:0:0: [sdb] CDB: Read(10): 28 00 3d 2c 33 00 00 00 f0 00
[189494.101518] end_request: I/O error, dev sdb, sector 1026306816
[189496.598517] sd 29:0:0:0: [sdb] Unhandled sense code
[189496.598523] sd 29:0:0:0: [sdb] Result: hostbyte=invalid driverbyte=DRIVER_SENSE
[189496.598528] sd 29:0:0:0: [sdb] Sense Key : Medium Error [current]
[189496.598534] sd 29:0:0:0: [sdb] Add. Sense: Unrecovered read error
[189496.598540] sd 29:0:0:0: [sdb] CDB: Read(10): 28 00 3d 2c 33 60 00 00 08 00
[189496.598552] end_request: critical target error, dev sdb, sector 1026306912
[189499.075387] sd 29:0:0:0: [sdb] Unhandled sense code
[189499.075391] sd 29:0:0:0: [sdb] Result: hostbyte=invalid driverbyte=DRIVER_SENSE
[189499.075394] sd 29:0:0:0: [sdb] Sense Key : Medium Error [current]
[189499.075398] sd 29:0:0:0: [sdb] Add. Sense: Unrecovered read error
[189499.075402] sd 29:0:0:0: [sdb] CDB: Read(10): 28 00 3d 2c 33 60 00 00 08 00
[189499.075409] end_request: critical target error, dev sdb, sector 1026306912
[192080.861016] sd 29:0:0:0: timing out command, waited 360s
[192702.021135] sd 29:0:0:0: timing out command, waited 360s
[193513.889045] sd 29:0:0:0: timing out command, waited 360s
[193873.893119] sd 29:0:0:0: timing out command, waited 360s


#4

Hi Ryan,

Thanks for sending in these extra details. Based on some of the messages there it looks like one of your drives may have some bad sectors:

189496.598534] sd 29:0:0:0: [sdb] Add. Sense: Unrecovered read error
[189496.598540] sd 29:0:0:0: [sdb] CDB: Read(10): 28 00 3d 2c 33 60 00 00 08 00
[189496.598552] end_request: critical target error, dev sdb, sector 1026306912

You may be able to work around them by using some of the built in file system tool on Ubuntu.

Something like

sudo e2fsck -c -c -k -v /dev/sdXX
Run this against the drive when it is unmounted with //dev/sdXX pointing to the drive that was locking up.

e2fsck may be able to mark the bad sectors so they’ll be skipped next time but you should see some messages about problem sectors.

If possible try another drive as well.

Let me know how it goes.

Thanks,
Jerome.

Plugable Technologies


#5