Ask Your Question

USB3 external drive caddy goes offline after a while

asked 2016-05-17 03:08:10 -0500

JetStream gravatar image

updated 2016-06-18 18:34:29 -0500

I noticed that my ORICO 2588US3 Portable USB 2.5 3.0 SATA external HDD enclosure is going offline after a period of idle when connected to USB3 ports on my laptops (one runs Fedore 21, the other Fedora 23). After plugging in the drive I can read/write to it immediately after, but if left idle for a little while the device goes offline without telling the system. If an attempt is made to access a file on the external drive, the system reports that the location is not available.

This doesn't happen when it is connected to an USB2 port.

Could this be some energy saving feature in the USB3 ports that is causing this?

I'll post more info that I spot. If you would like me to execute any command and report output, please let me know.

dmesg output

[ 9448.672288] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
[ 9448.684149] usb 2-2: New USB device found, idVendor=357d, idProduct=7788
[ 9448.684154] usb 2-2: New USB device strings: Mfr=10, Product=11, SerialNumber=3
[ 9448.684156] usb 2-2: Product: USB to ATA/ATAPI Bridge
[ 9448.684158] usb 2-2: Manufacturer: JMicron
[ 9448.684159] usb 2-2: SerialNumber: 000012345678
[ 9448.699991] usbcore: registered new interface driver usb-storage
[ 9448.703525] scsi host4: uas
[ 9448.704366] usbcore: registered new interface driver uas
[ 9448.705036] scsi 4:0:0:0: Direct-Access     TOSHIBA  MQ01XXXNNN       0100 PQ: 0 ANSI: 6
[ 9448.707804] sd 4:0:0:0: Attached scsi generic sg1 type 0
[ 9448.708435] sd 4:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 9448.708437] sd 4:0:0:0: [sdb] 4096-byte physical blocks
[ 9448.711541] sd 4:0:0:0: [sdb] Write Protect is off
[ 9448.711544] sd 4:0:0:0: [sdb] Mode Sense: 67 00 10 08
[ 9448.712759] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 9448.788026]  sdb: sdb1
[ 9448.794082] sd 4:0:0:0: [sdb] Attached SCSI disk
[ 9449.625260] EXT4-fs (sdb1): recovery complete
[ 9449.625390] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)


based on @archuserer's inputs, either this caddy does not support UASP or the uas driver has issues handling this product. So a quirk is registered for specific handling of this device.

backup initramfs (falback option)

sudo cp /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-backup.img


options usb-storage quirks=357d:7788:u

followed by regeneration of initramfs:

sudo dracut -f

rebooted and plugged in the USB3 drive, need to watch a bit to see the drive stays. From dmesg:

[  157.59] usb 4-1.1: New USB device found, idVendor=357d, idProduct=7788
[  157.59] usb 4-1.1: UAS is blacklisted for this device, using usb-storage instead
[  157.59] usb-storage 4-1.1:1.0: Quirks match for vid 357d pid 7788: 800000
[  157.59] scsi host7: usb-storage 4-1.1:1.

=== Below information is probably not ... (more)

edit retag flag offensive close merge delete


Most likely an energy saving feature. Does anything show up in dmesg when it goes idle or when you try to access it again? Does the hard drive spin down?

ssieb gravatar imagessieb ( 2016-05-18 13:53:17 -0500 )edit

Just noticed that this and another USB3 external drive that disconnect have the same Toshiba drive.

If I can lay my hands on another HDD/SDD, I'll check out if this is down to the drive instead of the caddy/Linux.

JetStream gravatar imageJetStream ( 2016-06-09 17:51:51 -0500 )edit

@archuserer, if you put your comment in as an answer, I'll accept it (can't convert your comment)

JetStream gravatar imageJetStream ( 2016-06-11 23:39:45 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2016-06-10 20:31:49 -0500

updated 2016-06-11 18:46:07 -0500

I recently purchased the exact same enclosure and ran in to the same problem. I had to create /etc/modprobe.d/uas.conf and add:

options usb-storage quirks=357d:7788:u

and then I rebuilt the initrd and rebooted. More info can be at:

I don't use fedora, but it should work just the same for you.

The problem is the uas module. The quirks=357d:7788:u is your vendor id and product id.

edit flag offensive delete link more


May be a stop-gap solution till the caddy / uas driver support is addressed. Does the job.

JetStream gravatar imageJetStream ( 2016-06-13 13:00:38 -0500 )edit

@archuserer Thanks a lot, that really helped me. Are you sure rebuilding initrd is necessary, though? I've added the file, called rmmod a couple of time (not sure that was necessary either), plugged the caddy in again, and it got set up in quirks mode, according to dmesg.

Dmitry Gutov gravatar imageDmitry Gutov ( 2016-09-02 20:35:01 -0500 )edit

Never mind. It's needed so that the solution still works after the reboot.

Dmitry Gutov gravatar imageDmitry Gutov ( 2016-09-04 15:23:31 -0500 )edit

Question Tools

1 follower


Asked: 2016-05-17 03:08:10 -0500

Seen: 640 times

Last updated: Jun 18 '16