USB drive controller connects as usb-storage rather than uas

bubbagump · 03-16-2021, 03:36 PM

I have a JMicro JMS567A and JMB393B based drive enclosure (Syba 5 bay). It supposedly supports UASP in Linux. However, I can't get this thing to use the UAS driver for the life of me and thus the performance is crud.

Dmesg shows:

Code:

[    1.803443] usb 6-2: Product: Syba USB Device
[    1.804175] usb 6-2: Manufacturer: JMicron
[    1.804895] usb 6-2: SerialNumber: DD2020052718E
[    1.806185] usb-storage 6-2:1.0: USB Mass Storage device detected
[    1.807071] usb-storage 6-2:1.0: Quirks match for vid 152d pid 0567: 5000000
[    1.807807] scsi host4: usb-storage 6-2:1.0

So I thought creating a udev file would make this go.

Code:

/etc/udev/rules.d/99-syba.rules 

ACTION=="add", ATTRS{idVendor}=="152d", ATTRS{idProduct}=="0567", RUN+="/sbin/modprobe uas" RUN+="/bin/sh -c 'echo 152d 0567 > /sys/bus/usb/drivers/uas/new_id'"

I even ran 'echo 152d 0567 > /sys/bus/usb/drivers/uas/new_id' manually and unplugged/replugged to see if that helped. It didn't.

Any ideas? Any obvious typos or something I screwed up? Thanks!

Emerson · 03-16-2021, 04:42 PM

Assuming your kernel supports UAS you should at least see UAS connection attempt, if you are plugging it to a USB-3 port. UAS won't be loaded for USB-2.

bubbagump · 03-16-2021, 05:04 PM

This makes me think this is a BIOS thing then as it’s the one and only port, it’s blue and the specs say USB 3.1 as well lsusb shows it as a USB 3 controller. I didn’t realize I should see attempts. This is good info, thank you!

Emerson · 03-16-2021, 05:14 PM

I have a device here, this is what I get when I plug it into USB-3 port, there is an attempt registered.

Code:

[420947.369606] usb 2-6: new SuperSpeed Gen 1 USB device number 19 using xhci_hcd
[420947.383970] usb 2-6: UAS is ignored for this device, using usb-storage instead
[420947.384002] usb 2-6: UAS is ignored for this device, using usb-storage instead
[420947.384008] usb-storage 2-6:1.0: USB Mass Storage device detected
[420947.384292] usb-storage 2-6:1.0: Quirks match for vid 2537 pid 1068: 800000
[420947.384386] scsi host6: usb-storage 2-6:1.0

bubbagump · 03-16-2021, 08:26 PM

Yeah, no dice at all. Everything seems right in the BIOS. Another UAS device works as UAS in the same port. I'm stumped. This is a fresh unplug/plugin after running

Code:

echo 152d 0567 > /sys/bus/usb/drivers/uas/new_id

So as you can see, there is no "UAS is ignored for this device" line here.

Code:

[ 2223.452767] usb 4-2: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 2223.477745] usb 4-2: New USB device found, idVendor=152d, idProduct=0567, bcdDevice=62.03
[ 2223.477773] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2223.477790] usb 4-2: Product: Syba USB Device
[ 2223.477802] usb 4-2: Manufacturer: JMicron
[ 2223.477812] usb 4-2: SerialNumber: DD2020052718E
[ 2223.478451] usb-storage 4-2:1.0: USB Mass Storage device detected
[ 2223.478731] usb-storage 4-2:1.0: Quirks match for vid 152d pid 0567: 5000000
[ 2223.478847] scsi host5: usb-storage 4-2:1.0
[ 2224.493026] scsi 5:0:0:0: Direct-Access     KINGSTON  SA400S37120G    6203 PQ: 0 ANSI: 6
[ 2224.493365] scsi 5:0:0:1: Direct-Access     ST8000DM 004-2CX188       6203 PQ: 0 ANSI: 6
[ 2224.493551] scsi 5:0:0:2: Direct-Access     ST8000DM 004-2CX188       6203 PQ: 0 ANSI: 6
[ 2224.493730] scsi 5:0:0:3: Direct-Access     KINGSTON  SA400S37120G    6203 PQ: 0 ANSI: 6
[ 2224.493905] scsi 5:0:0:0: Attached scsi generic sg2 type 0
[ 2224.494144] scsi 5:0:0:1: Attached scsi generic sg3 type 0
[ 2224.494379] scsi 5:0:0:2: Attached scsi generic sg4 type 0
[ 2224.494548] scsi 5:0:0:3: Attached scsi generic sg5 type 0
[ 2224.495349] sd 5:0:0:0: [sdh] 234441648 512-byte logical blocks: (120 GB/112 GiB)
[ 2224.495738] sd 5:0:0:1: [sdi] Very big device. Trying to use READ CAPACITY(16).
[ 2224.496055] sd 5:0:0:3: [sdk] 234441648 512-byte logical blocks: (120 GB/112 GiB)
[ 2224.496241] sd 5:0:0:2: [sdj] Very big device. Trying to use READ CAPACITY(16).
[ 2224.496371] sd 5:0:0:2: [sdj] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
[ 2224.496404] sd 5:0:0:2: [sdj] 4096-byte physical blocks
[ 2224.496664] sd 5:0:0:2: [sdj] Write Protect is off
[ 2224.496678] sd 5:0:0:2: [sdj] Mode Sense: 2b 00 00 00
[ 2224.496883] sd 5:0:0:2: [sdj] No Caching mode page found
[ 2224.496896] sd 5:0:0:2: [sdj] Assuming drive cache: write through
[ 2224.497030] sd 5:0:0:1: [sdi] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
[ 2224.497048] sd 5:0:0:1: [sdi] 4096-byte physical blocks
[ 2224.497263] sd 5:0:0:1: [sdi] Write Protect is off
[ 2224.497275] sd 5:0:0:1: [sdi] Mode Sense: 2b 00 00 00
[ 2224.497478] sd 5:0:0:1: [sdi] No Caching mode page found
[ 2224.497490] sd 5:0:0:1: [sdi] Assuming drive cache: write through
[ 2224.497765] sd 5:0:0:3: [sdk] Write Protect is off
[ 2224.497783] sd 5:0:0:3: [sdk] Mode Sense: 2b 00 00 00
[ 2224.498906] sd 5:0:0:0: [sdh] Write Protect is off
[ 2224.498922] sd 5:0:0:0: [sdh] Mode Sense: 2b 00 00 00
[ 2224.499131] sd 5:0:0:3: [sdk] No Caching mode page found
[ 2224.499147] sd 5:0:0:3: [sdk] Assuming drive cache: write through
[ 2224.499346] sd 5:0:0:0: [sdh] No Caching mode page found
[ 2224.499361] sd 5:0:0:0: [sdh] Assuming drive cache: write through
[ 2224.525166]  sdk: sdk1 sdk9
[ 2224.525694]  sdh: sdh1 sdh9
[ 2224.526478] sd 5:0:0:3: [sdk] Attached SCSI disk
[ 2224.527110] sd 5:0:0:0: [sdh] Attached SCSI disk
[ 2224.659737]  sdj: sdj1 sdj9
[ 2224.659984]  sdi: sdi1 sdi9
[ 2224.662559] sd 5:0:0:2: [sdj] Attached SCSI disk
[ 2224.663753] sd 5:0:0:1: [sdi] Attached SCSI disk

Emerson · 03-16-2021, 09:57 PM

Another device works then it cannot be your computer, bad cable?

computersavvy · 03-16-2021, 10:03 PM

So it is seeing the drive and attempts to configure it.

What size is the drive?
From those messages it seems to be an 8 TB drive and the OS seems unable to configure a drive of that size. Are you certain that device will support an 8 TB drive?

The link you posted shows that it supports up to 6 TB drives.

bubbagump · 03-16-2021, 10:07 PM

And lower on the page it says 8TB. Hrm.

computersavvy · 03-17-2021, 11:25 AM

Can you point out where it says 8 TB drives are supported?

I see this

Code:

- Supports all brands of 2.5" and 3.5" SATA I/II/III hard disk drive up to 6TB per drive up to 5 x 6TB. Support hard drive transfer rate up to SATA III
- Raid Support: RAID 0, RAID 1, RAID 3, RAID 5, Raid 10, SPAN, and JBOD
- eSATA interface requires Port Multiplier w/FIS-based switching on main computer to enable access to multiple HDDs simultaneously

and can find no other reference to the drives supported anywhere on that page.

I suspect your 8TB drive is not physically supported in that enclosure.

bubbagump · 03-17-2021, 11:37 AM

I'm looking at this. And their Amazon listing shows 10TB. FWIW, the 120GB drives don't negotiate UAS either. The 8TB do work though - just the controller won't go UAS if that makes sense. I can read and write and fio abuse the 8TBs no sweat. The performance just sucks as no UAS.

computersavvy · 03-18-2021, 02:10 PM

So both of those last two links are from 3rd parties and not the original from the manufacturer like you put into the first post.
I suspect the failure of UAS is due to bios and/or OS incompatibility with the drive hardware on the NAS side.

bubbagump · 03-18-2021, 02:27 PM

The first link is on the manufacture’s page.... scroll down. Actually, here's a GIF so you don't have to.

None of this explains why I get the same behavior with 120GB drives.

Emerson · 03-18-2021, 02:48 PM

I get the negotiation regardless whether there is drive connected or not. We know your computer and USB port can do it, remains the cable and Syba electronics. When I had printer trouble I installed W7 in a VM for testing it, maybe you should do the same.

Emerson · 03-18-2021, 10:55 PM

Thanks to you I had a closer look at my dock and discovered it has bad USB port, computer attempts UAS but fails because the USB-3 connection is crippled somehow, when I yank the cable it spits errors into dmesg. As a workaround I wanted to use eSATA, but found my current motherboard has no eSATA port. Headed to eBay and bought a SATA to eSATA adapter, it is a bracket which goes to the back of the case, cost less than $4 shipped.