RPi & USB HDD/SSD - USB Enclosure recommendation? (UAS uas_eh_abort_handler problems with current one)

[angriest]

Hi,

I got my RPi4 in the post yesterday, and once I'd realised it doesn't boot from USB out of the box (gah), I ran into a problem. I've got a :

WD Blue 500GB SSDhttps://www.amazon.co.uk/gp/product/B07 ... UTF8&psc=1
and
a Sabrent 2.5-Inch SATA to USB 3.0 enclosure https://www.amazon.co.uk/gp/product/B00 ... UTF8&psc=1.

Booting takes a long time, and looking through dmesg, there's a lot of

uas_eh_abort_handler

errors. I have no problems using the drive/enclosure in Windows 10, and from what I've read it's to do with the interface chip in the enclosure and the kernel and there is a workaround involving quirks to stop the drive using UAS, but I'd rather get a different enclosure that works fully.

Question: Are there any USB 3.0 to SATA enclosures/cables that are known to work without any problems using an SSD with the RPi?

[sling]

having the same problem with an orico usb3 case and kingston ssd on a pi4.
can't read/write any files over smb without these appearing and filetransfer hanging forever:

Code: Select all

[ 2805.042825] sd 0:0:0:0: [sda] tag#14 CDB: opcode=0x28 28 00 14 44 cf 80 00 01 00 00
[ 2805.043441] sd 0:0:0:0: [sda] tag#13 uas_eh_abort_handler 0 uas-tag 26 inflight: CMD IN
[ 2805.043454] sd 0:0:0:0: [sda] tag#13 CDB: opcode=0x28 28 00 14 44 ce 80 00 01 00 00
[ 2805.044043] sd 0:0:0:0: [sda] tag#12 uas_eh_abort_handler 0 uas-tag 25 inflight: CMD IN
[ 2805.044055] sd 0:0:0:0: [sda] tag#12 CDB: opcode=0x28 28 00 14 44 cd 80 00 01 00 00
[ 2805.044650] sd 0:0:0:0: [sda] tag#11 uas_eh_abort_handler 0 uas-tag 24 inflight: CMD IN
[ 2805.044662] sd 0:0:0:0: [sda] tag#11 CDB: opcode=0x28 28 00 14 44 cb 80 00 01 00 00
[ 2805.045263] sd 0:0:0:0: [sda] tag#10 uas_eh_abort_handler 0 uas-tag 23 inflight: CMD IN
[ 2805.045276] sd 0:0:0:0: [sda] tag#10 CDB: opcode=0x28 28 00 14 44 ca 80 00 01 00 00
[ 2805.045861] sd 0:0:0:0: [sda] tag#9 uas_eh_abort_handler 0 uas-tag 22 inflight: CMD IN
[ 2805.045873] sd 0:0:0:0: [sda] tag#9 CDB: opcode=0x28 28 00 14 44 c9 80 00 01 00 00
[ 2805.046461] sd 0:0:0:0: [sda] tag#8 uas_eh_abort_handler 0 uas-tag 21 inflight: CMD IN
[ 2805.046474] sd 0:0:0:0: [sda] tag#8 CDB: opcode=0x28 28 00 14 44 c8 80 00 01 00 00
[ 2805.047036] sd 0:0:0:0: [sda] tag#7 uas_eh_abort_handler 0 uas-tag 20 inflight: CMD IN
[ 2805.047047] sd 0:0:0:0: [sda] tag#7 CDB: opcode=0x28 28 00 14 44 c7 80 00 01 00 00
[ 2805.047632] sd 0:0:0:0: [sda] tag#6 uas_eh_abort_handler 0 uas-tag 19 inflight: CMD IN
[ 2805.047644] sd 0:0:0:0: [sda] tag#6 CDB: opcode=0x28 28 00 14 44 c6 80 00 01 00 00
[ 2805.048229] sd 0:0:0:0: [sda] tag#5 uas_eh_abort_handler 0 uas-tag 18 inflight: CMD IN
[ 2805.048240] sd 0:0:0:0: [sda] tag#5 CDB: opcode=0x28 28 00 14 44 c5 80 00 01 00 00
[ 2805.048811] sd 0:0:0:0: [sda] tag#4 uas_eh_abort_handler 0 uas-tag 17 inflight: CMD IN
[ 2805.048824] sd 0:0:0:0: [sda] tag#4 CDB: opcode=0x28 28 00 14 44 c3 80 00 00 80 00
[ 2805.049258] sd 0:0:0:0: [sda] tag#3 uas_eh_abort_handler 0 uas-tag 16 inflight: CMD IN
[ 2805.049272] sd 0:0:0:0: [sda] tag#3 CDB: opcode=0x28 28 00 14 44 c4 80 00 01 00 00
[ 2805.049887] sd 0:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 15 inflight: CMD IN
[ 2805.049900] sd 0:0:0:0: [sda] tag#2 CDB: opcode=0x28 28 00 14 44 c4 00 00 00 80 00
[ 2805.050314] sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 14 inflight: CMD IN
[ 2805.050326] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 14 44 c2 80 00 01 00 00
[ 2805.050842] sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 13 inflight: CMD IN
[ 2805.050854] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 14 44 c1 80 00 01 00 00
[ 2805.108997] scsi host0: uas_eh_device_reset_handler start
[ 2805.259569] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 2805.293556] scsi host0: uas_eh_device_reset_handler success
pi@commander:~ $ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c502 Logitech, Inc. Cordless Mouse & iTouch Keys
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[angriest]

Hi,

Update - I've found a USB 3.0 enclosure that doesn't have all the uas_eh_abort_handler errors, and my RPi4 boots in lightning quick time. For reference:


Inateck 2.5 Hard Drive Enclosure, USB 3.0 External Hard Drive Case, FE2004https://www.amazon.co.uk/gp/product/B00 ... UTF8&psc=1

causes no problems (I saw this tipped off elsewhere, can't remember where, but wasn't easy to Google, so leaving here for ease of finding for others). Please feel free to share any other enclosures that are problem free.

[cantanko]

Also have that Sabrent unit - works fine under Windows 10 and MacOS, but the Pi 4 really hates it - I'd avoid it for the moment...

Code: Select all

Jun 28 22:23:53 openhab kernel: [21862.948863] usb 2-1: new SuperSpeed Gen 1 USB device number 7 using xhci_hcd
Jun 28 22:23:53 openhab kernel: [21862.979991] usb 2-1: New USB device found, idVendor=152d, idProduct=1561, bcdDevice= 2.04
Jun 28 22:23:53 openhab kernel: [21862.980007] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 28 22:23:53 openhab kernel: [21862.980020] usb 2-1: Product: SABRENT
Jun 28 22:23:53 openhab kernel: [21862.980032] usb 2-1: Manufacturer: SABRENT
Jun 28 22:23:53 openhab kernel: [21862.980044] usb 2-1: SerialNumber: DB9876543214E
Jun 28 22:23:53 openhab kernel: [21862.988365] scsi host0: uas
Jun 28 22:23:53 openhab kernel: [21862.990205] scsi 0:0:0:0: Direct-Access     SABRENT                   0204 PQ: 0 ANSI: 6
Jun 28 22:23:53 openhab kernel: [21862.991550] sd 0:0:0:0: Attached scsi generic sg0 type 0
Jun 28 22:24:01 openhab mtp-probe: checking bus 2, device 7: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-1"
Jun 28 22:24:01 openhab mtp-probe: bus: 2, device: 7 was not an MTP device
Jun 28 22:24:01 openhab mtp-probe: checking bus 2, device 7: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-1"
Jun 28 22:24:01 openhab mtp-probe: bus: 2, device: 7 was not an MTP device
Jun 28 22:24:03 openhab kernel: [21872.991773] sd 0:0:0:0: [sda] Spinning up disk...
Jun 28 22:24:05 openhab kernel: [21874.428832] .ready
Jun 28 22:24:05 openhab kernel: [21874.430249] sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/233 GiB)
Jun 28 22:24:05 openhab kernel: [21874.430264] sd 0:0:0:0: [sda] 4096-byte physical blocks
Jun 28 22:24:05 openhab kernel: [21874.430477] sd 0:0:0:0: [sda] Write Protect is off
Jun 28 22:24:05 openhab kernel: [21874.431383] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jun 28 22:24:05 openhab kernel: [21874.432074] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
Jun 28 22:24:05 openhab kernel: [21874.438097]  sda: sda1 sda2
Jun 28 22:24:05 openhab kernel: [21874.441133] sd 0:0:0:0: [sda] Attached SCSI disk
Jun 28 22:24:35 openhab kernel: [21904.929427] sd 0:0:0:0: [sda] tag#3 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD IN
Jun 28 22:24:35 openhab kernel: [21904.929445] sd 0:0:0:0: [sda] tag#3 CDB: opcode=0x28 28 00 1d 1c 55 e8 00 00 18 00
Jun 28 22:24:35 openhab kernel: [21904.929583] sd 0:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
Jun 28 22:24:35 openhab kernel: [21904.929597] sd 0:0:0:0: [sda] tag#2 CDB: opcode=0x85 85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00
Jun 28 22:24:35 openhab kernel: [21904.969446] scsi host0: uas_eh_device_reset_handler start
Jun 28 22:24:35 openhab kernel: [21905.120286] usb 2-1: reset SuperSpeed Gen 1 USB device number 7 using xhci_hcd
Jun 28 22:24:36 openhab kernel: [21905.155443] scsi host0: uas_eh_device_reset_handler success
Jun 28 22:25:07 openhab kernel: [21936.290043] sd 0:0:0:0: [sda] tag#9 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
Jun 28 22:25:07 openhab kernel: [21936.290061] sd 0:0:0:0: [sda] tag#9 CDB: opcode=0x28 28 00 00 00 82 08 00 01 f8 00
Jun 28 22:25:07 openhab kernel: [21936.290282] sd 0:0:0:0: tag#4 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD
Jun 28 22:25:07 openhab kernel: [21936.290295] sd 0:0:0:0: tag#4 CDB: opcode=0x0 00 00 00 00 00 00
Jun 28 22:25:09 openhab kernel: [21938.690114] sd 0:0:0:0: [sda] tag#5 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN
Jun 28 22:25:09 openhab kernel: [21938.690132] sd 0:0:0:0: [sda] tag#5 CDB: opcode=0x28 28 00 00 00 04 08 00 03 f8 00
Jun 28 22:25:09 openhab kernel: [21938.730111] scsi host0: uas_eh_device_reset_handler start
Jun 28 22:25:09 openhab kernel: [21938.880956] usb 2-1: reset SuperSpeed Gen 1 USB device number 7 using xhci_hcd
Jun 28 22:25:09 openhab kernel: [21938.916100] scsi host0: uas_eh_device_reset_handler success
Jun 28 22:25:40 openhab kernel: [21969.570699] sd 0:0:0:0: [sda] tag#13 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD IN
Jun 28 22:25:40 openhab kernel: [21969.570717] sd 0:0:0:0: [sda] tag#13 CDB: opcode=0x28 28 00 1d 1c 4f 88 00 00 68 00
Jun 28 22:28:07 openhab kernel: [22116.753716] hdparm          D    0  6467   5958 0x00000000
Jun 28 22:28:07 openhab kernel: [22116.753761] [<c0990864>] (__schedule) from [<c0990ed4>] (schedule+0x50/0xa8)
Jun 28 22:28:07 openhab kernel: [22116.753781] [<c0990ed4>] (schedule) from [<c0994e7c>] (schedule_timeout+0x200/0x428)
Jun 28 22:28:07 openhab kernel: [22116.753799] [<c0994e7c>] (schedule_timeout) from [<c09913cc>] (io_schedule_timeout+0x28/0x48)
Jun 28 22:28:07 openhab kernel: [22116.753818] [<c09913cc>] (io_schedule_timeout) from [<c0991da4>] (wait_for_common_io.constprop.2+0xd0/0x168)
Jun 28 22:28:07 openhab kernel: [22116.753836] [<c0991da4>] (wait_for_common_io.constprop.2) from [<c0991e74>] (wait_for_completion_io+0x1c/0x20)
Jun 28 22:28:07 openhab kernel: [22116.753855] [<c0991e74>] (wait_for_completion_io) from [<c05b823c>] (submit_bio_wait+0x70/0x94)
Jun 28 22:28:07 openhab kernel: [22116.753875] [<c05b823c>] (submit_bio_wait) from [<c05c7bc8>] (blkdev_issue_flush+0x90/0xb8)
Jun 28 22:28:07 openhab kernel: [22116.753894] [<c05c7bc8>] (blkdev_issue_flush) from [<c03f0588>] (blkdev_fsync+0x48/0x58)
Jun 28 22:28:07 openhab kernel: [22116.753913] [<c03f0588>] (blkdev_fsync) from [<c03e70c4>] (vfs_fsync_range+0x68/0x98)
Jun 28 22:28:07 openhab kernel: [22116.753930] [<c03e70c4>] (vfs_fsync_range) from [<c03e717c>] (do_fsync+0x4c/0x74)
Jun 28 22:28:07 openhab kernel: [22116.753947] [<c03e717c>] (do_fsync) from [<c03e7488>] (sys_fsync+0x1c/0x20)
Jun 28 22:28:07 openhab kernel: [22116.753966] [<c03e7488>] (sys_fsync) from [<c0201000>] (ret_fast_syscall+0x0/0x28)
Jun 28 22:28:07 openhab kernel: [22116.753977] Exception stack(0xd9b29fa8 to 0xd9b29ff0)
Jun 28 22:28:07 openhab kernel: [22116.753991] 9fa0:                   00000003 0003a458 00000003 00200000 0000006c 00000000
Jun 28 22:28:07 openhab kernel: [22116.754005] 9fc0: 00000003 0003a458 0001d1c5 00000076 00000001 00000000 00000000 0003a008
Jun 28 22:28:07 openhab kernel: [22116.754017] 9fe0: 00039ec8 befafea8 00013328 b6ecc8a4

[PhatFil]

Hi,

Update - I've found a USB 3.0 enclosure that doesn't have all the uas_eh_abort_handler errors, and my RPi4 boots in lightning quick time. For reference:


Inateck 2.5 Hard Drive Enclosure, USB 3.0 External Hard Drive Case, FE2004https://www.amazon.co.uk/gp/product/B00 ... UTF8&psc=1

causes no problems (I saw this tipped off elsewhere, can't remember where, but wasn't easy to Google, so leaving here for ease of finding for others). Please feel free to share any other enclosures that are problem free.

Thanks for the tip/link...

[ezstyles]

Hi,

Update - I've found a USB 3.0 enclosure that doesn't have all the uas_eh_abort_handler errors, and my RPi4 boots in lightning quick time. For reference:


Inateck 2.5 Hard Drive Enclosure, USB 3.0 External Hard Drive Case, FE2004https://www.amazon.co.uk/gp/product/B00 ... UTF8&psc=1

causes no problems (I saw this tipped off elsewhere, can't remember where, but wasn't easy to Google, so leaving here for ease of finding for others). Please feel free to share any other enclosures that are problem free.

I bought one of these enclosures to try and am still having the same issues. The search continues

[GTom4544]

Have you found your ideal candidate? I started looking at cheap usb-sata cables on fleabay and Ali, wondering if anyone has experience with one or more of these types?: https://www.ebay.com/sch/i.html?_from=R ... nc&_udhi=6

[pidd]

There are loads of recommendations on USB3 to Sata adaptors on the forum that work, I do like the spirit of adventure that takes people to try out other adaptors.

Eluteng is the one recommend the most times, so I went and bought them - I'm not so adventurous when it comes to wasting more of my time.