Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

USB JBOD Drive Mount Issues After Upgrade to 7.0/7.0.1

Featured Replies

So just to start off i am aware USB JBOD devices are not recommend however i have been using my current setup with issues on Unraid 6 for a number of years.

 

After upgrading to version 7 I am having an issue where my two pool drives are both visible but only one can be mounted or loaded into a new config the other drive appears in the device list but cannot be mounted with configured both theses drives are in a usb 3.1 JBOD  yolltamaster drive enclosure that i have been using with no issues for 12 months and it all goes back to working if i downgrade to 6.12.

 

I believe this error is the likely cause but i'm not sure how to go about fixing it.

"Read SCT Status failed: scsi error device will be ready soon
Wt Cache Reorder: Unknown (SCT Feature Control command failed)'

 

I've also attached full diagnostics

 

image.thumb.png.eff19172a782dafa31a7d59e8120bc31.png

therepository-diagnostics-20250310-1718.zip

Solved by JorgeB

  • Community Expert

Post the output from

lsusb -vt

 

  • Author
1 hour ago, JorgeB said:

Post the output from

lsusb -vt

 

 

Here you go

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/3p, 20000M/x2
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 2109:2822 VIA Labs, Inc.
        |__ Port 003: Dev 005, If 0, Class=Hub, Driver=hub/4p, 480M
            ID 2109:2822 VIA Labs, Inc.
    |__ Port 009: Dev 003, If 0, Class=Mass Storage, Driver=usb-storage, 480M
        ID 058f:6387 Alcor Micro Corp. Flash Drive
    |__ Port 010: Dev 004, If 0, Class=Wireless, Driver=btusb, 480M
        ID 0e8d:c616 MediaTek Inc.
    |__ Port 010: Dev 004, If 1, Class=Wireless, Driver=btusb, 480M
        ID 0e8d:c616 MediaTek Inc.
    |__ Port 010: Dev 004, If 2, Class=Wireless, Driver=[none], 480M
        ID 0e8d:c616 MediaTek Inc.
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 10000M
        ID 2109:0822 VIA Labs, Inc.
        |__ Port 003: Dev 003, If 0, Class=Hub, Driver=hub/4p, 10000M
            ID 2109:0822 VIA Labs, Inc.
            |__ Port 001: Dev 004, If 0, Class=Mass Storage, Driver=uas, 10000M
                ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
            |__ Port 002: Dev 005, If 0, Class=Mass Storage, Driver=uas, 10000M
                ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
            |__ Port 003: Dev 006, If 0, Class=Mass Storage, Driver=uas, 10000M
                ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor

 

  • Community Expert
  • Solution

Go to the syslinux config, and add a USB quirk after /bzroot, like the example below, but with 2109:0715:u

 

uasp add quirk.JPG

  • Author
26 minutes ago, JorgeB said:

Go to the syslinux config, and add a USB quirk after /bzroot, like the example below, but with 2109:0715:u

 

uasp add quirk.JPG

The seems to have done the trick I orginally had it on a new line which did not work. But moving it to the same line got it working.

 

What does usb_storage.quirks do?

  • Community Expert

Unraid 7.x includes a new USB driver, which should be faster and also supports trim, but some devices try to use and don't really support it, that quirk makes v7.x use the older USB storage driver that was used with 6.12

  • Author
52 minutes ago, JorgeB said:

Unraid 7.x includes a new USB driver, which should be faster and also supports trim, but some devices try to use and don't really support it, that quirk makes v7.x use the older USB storage driver that was used with 6.12

That makes sense thanks for all your help

  • 5 months later...
On 3/10/2025 at 12:28 PM, JorgeB said:

Gehen Sie zur syslinux-Konfiguration und fügen Sie eine USB-Macke nach /bzroot hinzu, wie im folgenden Beispiel, jedoch mit 2109:0715:u

 

uasp add quirk.JPG

Morning, I have the same problem.

Here’s my output—could you also tell me what the values would be for me?
I’d rather not do something wrong and break something right away.
Installed is a CENMATE 4-bay external enclosure.

image.png


root@Tower:~# lsusb -vt

/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M

ID 1d6b:0002 Linux Foundation 2.0 root hub

|__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/5p, 480M

ID 0bda:5423 Realtek Semiconductor Corp.

|__ Port 002: Dev 005, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M

ID 1b1f:c020 eQ-3 Entwicklung GmbH HmIP-RFUSB

|__ Port 003: Dev 003, If 0, Class=Mass Storage, Driver=usb-storage, 480M

ID 058f:6387 Alcor Micro Corp. Flash Drive

/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M

ID 1d6b:0003 Linux Foundation 3.0 root hub

|__ Port 003: Dev 002, If 0, Class=Hub, Driver=hub/4p, 10000M

ID 0bda:0423 Realtek Semiconductor Corp.

|__ Port 001: Dev 003, If 0, Class=Mass Storage, Driver=uas, 10000M

ID 04e8:61fb Samsung Electronics Co., Ltd

|__ Port 003: Dev 004, If 0, Class=Mass Storage, Driver=uas, 5000M

ID 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge

Edited by SvensenDE

  • Community Expert

The enclosure should be 152d:0567. If you also want to use the regular USB storage driver for the Samsung SSD also add 04e8:61fb, so for both it would be:

usb_storage.quirks=152d:0567:u,04e8:61fb:u

28 minutes ago, JorgeB said:

The enclosure should be 152d:0567. If you also want to use the regular USB storage driver for the Samsung SSD also add 04e8:61fb, so for both it would be:

usb_storage.quirks=152d:0567:u,04e8:61fb:u

So, the Samsung SSD was already working before.
This is about the HDD, and I think this here is “JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge”.

Edited by SvensenDE

  • Community Expert
57 minutes ago, SvensenDE said:

This is about the HDD

Just add that one then: usb_storage.quirks=152d:0567:u

I will test this as soon as the parity test is completed, otherwise it will start over.
Once it is completed, I will test it and report back.

11 hours ago, JorgeB said:

Just add that one then: usb_storage.quirks=152d:0567:u


Good morning from Germany,

Thank you very much for your help, it worked.

  • 2 months later...

I solved this problem in 7.1.4, and now, after updating to 7.2.2 I am having the same problem again, but just with one HDD.

LOOK: https://ibb.co/JR64QFQM

I did this in 7.1.4., but now it is generating problem with one hdd: I ran lsusb and confirmed that both of my USB enclosures report the same chipset and USB ID: 2109:0715 (VIA Labs, Inc. VL817 SATA Adaptor). So it looks like both enclosures share this VID:PID. I’ll go into the Syslinux Configuration in Unraid (Main > Flash > Syslinux Configuration) and modify the append line to: append initrd=/bzroot usb_storage.quirks=2109:0715:u, then save and reboot.

  • Community Expert

Please post the diagnostics and the output from lsusb -vt

5 hours ago, JorgeB said:

Please post the diagnostics and the output from lsusb -vt

I am back in 7.1.4. because nothing worked on 7.2.2. Probably i will update on the future, but i need stability right now. Is it possible that the quirk doesn't work on this new version? It was strange the problem, just one hdd and not the rest. I use two fantec cases, and the problem was with just one disk. Thanks.

  • Community Expert
54 minutes ago, Theonor said:

Is it possible that the quirk doesn't work on this new version?

It should still work, but would need the diags and that output to see what's going on.

  • 1 month later...

hey guys, i need some help with my Orico Macdata 5-bay das.

I'm using it on an hp elitedesk g2 mini with unraid, but i have a big issue with duplicate serial IDs.

The das uses the VIA VL817 chip (ID 2109:0715) and i've already tried the "quirk" fix but it didn't change the serials...

Also, right now it's running at 480M (usb 2.0) even though it's a usb-c connection. i have a new usb 3.2 cable coming tomorrow to see if more speed helps, but i'm worried about the serials.

Here are some commands i ran:

root@tender:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 004: ID ffff:5678 USB Disk 2.0
Bus 001 Device 016: ID 2109:2822 VIA Labs, Inc. USB2.0 Hub             
Bus 001 Device 017: ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
Bus 001 Device 018: ID 2109:2822 VIA Labs, Inc. USB2.0 Hub             
Bus 001 Device 019: ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
Bus 001 Device 020: ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
Bus 001 Device 021: ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
root@tender:~# lsusb -vt
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 007: Dev 002, If 0, Class=Wireless, Driver=[none], 12M
        ID 8087:0a2b Intel Corp. Bluetooth wireless interface
    |__ Port 007: Dev 002, If 1, Class=Wireless, Driver=[none], 12M
        ID 8087:0a2b Intel Corp. Bluetooth wireless interface
    |__ Port 009: Dev 016, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 2109:2822 VIA Labs, Inc. 
        |__ Port 002: Dev 017, If 0, Class=Mass Storage, Driver=usb-storage, 480M
            ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
        |__ Port 003: Dev 018, If 0, Class=Hub, Driver=hub/4p, 480M
            ID 2109:2822 VIA Labs, Inc. 
            |__ Port 001: Dev 019, If 0, Class=Mass Storage, Driver=usb-storage, 480M
                ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
            |__ Port 002: Dev 020, If 0, Class=Mass Storage, Driver=usb-storage, 480M
                ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
            |__ Port 003: Dev 021, If 0, Class=Mass Storage, Driver=usb-storage, 480M
                ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
    |__ Port 013: Dev 004, If 0, Class=Mass Storage, Driver=usb-storage, 480M
        ID ffff:5678  
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/10p, 5000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
root@tender:~# cat /proc/cmdline
BOOT_IMAGE=/bzimage initrd=/bzroot usb_storage.quirks=2109:0715:u
root@tender:~# ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root  9 Jan 19 23:34 ata-CT500BX500SSD1_2428E8BAE1BC -> ../../sdc
lrwxrwxrwx 1 root root 10 Jan 19 23:34 ata-CT500BX500SSD1_2428E8BAE1BC-part1 -> ../../sdc1
lrwxrwxrwx 1 root root  9 Jan 19 23:51 ata-ST4000VN006-3CW104_WW690QV5 -> ../../sdf
lrwxrwxrwx 1 root root 10 Jan 19 23:51 ata-ST4000VN006-3CW104_WW690QV5-part1 -> ../../sdf1
lrwxrwxrwx 1 root root  9 Jan 19 23:51 usb-ST4000VN_006-3CW104_000000123AE8-0:0 -> ../../sde
lrwxrwxrwx 1 root root 10 Jan 19 23:51 usb-ST4000VN_006-3CW104_000000123AE8-0:0-part1 -> ../../sde1
lrwxrwxrwx 1 root root  9 Jan 19 23:34 usb-VendorCo_ProductCode_56146AFE0BBF0F71-0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 Jan 19 23:34 usb-VendorCo_ProductCode_56146AFE0BBF0F71-0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root  9 Jan 19 23:51 usb-WDC_WD40_EZRZ-00GXCB0_000000123AE8-0:0 -> ../../sdg
lrwxrwxrwx 1 root root 10 Jan 19 23:51 usb-WDC_WD40_EZRZ-00GXCB0_000000123AE8-0:0-part1 -> ../../sdg1
lrwxrwxrwx 1 root root  9 Jan 19 23:51 wwn-0x5000c501137ed164 -> ../../sdf
lrwxrwxrwx 1 root root 10 Jan 19 23:51 wwn-0x5000c501137ed164-part1 -> ../../sdf1
lrwxrwxrwx 1 root root  9 Jan 19 23:34 wwn-0x500a0751e8bae1bc -> ../../sdc
lrwxrwxrwx 1 root root 10 Jan 19 23:34 wwn-0x500a0751e8bae1bc-part1 -> ../../sdc1

There is any way to force this orico das to show the real serials on linux? on windows it works fine and i can see all individual drives...

Please let me know,!
Many thanks :)

Ps: i'm on the latest unraid 7.2.3

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.