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.

Unraid 7 Assigning different drive ids with each boot

Featured Replies

Hello unraiders,

 

I upgraded to 7.0 a few weeks ago and I have found that every time I reboot my drive ids change.  The first time it was my parity drive, so I let it rebuild parity, no big deal.  The second time it was a data disk, so it had to rebuild. 

 

You'll see in the attached screenshot that my parity drive has replaced the drive serial number with:

00000000000000001 and it should be ST18000NT001-3LU101_ZR5A9CP4..  The next boot it might be disk 1 or disk2 that goes wonky.   I've shutdown, reset all drive, and connections.  

 

 

Capture.JPG.4e78a75f5c3e033b22d7cfb398de5ecd.JPG

 

I have a very small minimalist type setup, but it has worked for my needs for several years.  

CPU is a Beelink SEi11 

4 slot Probox enclosure connected via USB-C

3 - 18tb Seagate drives

1 - 2tb SSD for cache

 

I did some searches and saw that USB is not recommended, but it has worked flawlessly for me up to unraid 7.   I looked for any firmware updates for my beelink usb and didn't find anything.  Is there any way to manual update the drive serial numbers that unraid sees so they remain static?

 

Thanks for your help.

 

  • Community Expert

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread taken when you next encounter the problem.It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

  • Community Expert

This can happen with USB enclosures that are not fully compatible with the newer UASP driver, disabling it should resolve it, post the output from:

 

lsusb -vt

 

  • Author

Here is the output, but it may not show anything now.  I reverted back to 6.12.14 and all my drives are recognized correctly.

 

Quote

/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/4p, 10000M
        ID 2109:8822 VIA Labs, Inc.
        |__ Port 1: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 10000M
            ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
        |__ Port 2: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 10000M
            ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
        |__ Port 3: Dev 5, If 0, Class=Mass Storage, Driver=usb-storage, 10000M
            ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
        |__ Port 4: Dev 6, If 0, Class=Mass Storage, Driver=usb-storage, 10000M
            ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M
        ID 0781:5575 SanDisk Corp. Cruzer Glide
    |__ Port 3: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 1a40:0101 Terminus Technology Inc. Hub
        |__ Port 1: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
            ID 1a86:e050 QinHeng Electronics
        |__ Port 1: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M
            ID 1a86:e050 QinHeng Electronics
        |__ Port 1: Dev 5, If 2, Class=Human Interface Device, Driver=usbhid, 12M
            ID 1a86:e050 QinHeng Electronics
        |__ Port 1: Dev 5, If 3, Class=Human Interface Device, Driver=usbhid, 12M
            ID 1a86:e050 QinHeng Electronics
    |__ Port 4: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 051d:0002 American Power Conversion Uninterruptible Power Supply
    |__ Port 5: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M
        ID 2109:2822 VIA Labs, Inc.
        |__ Port 5: Dev 10, If 0, Class=, Driver=, 480M
            ID 2109:8818 VIA Labs, Inc.
    |__ Port 10: Dev 8, If 0, Class=Wireless, Driver=btusb, 12M
        ID 8087:0026 Intel Corp. AX201 Bluetooth
    |__ Port 10: Dev 8, If 1, Class=Wireless, Driver=btusb, 12M
        ID 8087:0026 Intel Corp. AX201 Bluetooth
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
 

 

Edited by jeff_screws

  • Community Expert

It would be better from v7, but try adding a quirk to the default boot mode with 2109:0715:u, like below but with the correct ID:

 

uasp add quirk.JPG

  • Author

Thanks.  Just to clarify I add that with the correct id for my USB flash boot device?

  • Community Expert

Yes, click on the flash then scroll down to syslinux configuration.

  • 3 months later...
  • Author

Sorry I didn't try this sooner, but I updated to 7.0.1 this morning and this is still an issue.  So I added the quirk and my drives are still not identified with the full names.  I've attached my diagnostics.  Is there any other course of action?  Should I pass the quirk for each drive?

tower-diagnostics-20250512-1133.zip

 

 

lsusb -t output

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 480M
    |__ Port 003: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 001: Dev 005, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 001: Dev 005, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 001: Dev 005, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 001: Dev 005, If 3, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 004: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 005: Dev 006, If 0, Class=Hub, Driver=hub/5p, 480M
        |__ Port 005: Dev 010, If 0, Class=[unknown], Driver=[none], 480M
    |__ Port 010: Dev 008, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 010: Dev 008, If 1, Class=Wireless, Driver=btusb, 12M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    |__ Port 003: Dev 002, If 0, Class=Hub, Driver=hub/4p, 10000M
        |__ Port 001: Dev 003, If 0, Class=Mass Storage, Driver=uas, 10000M
        |__ Port 002: Dev 004, If 0, Class=Mass Storage, Driver=uas, 10000M
        |__ Port 003: Dev 005, If 0, Class=Mass Storage, Driver=uas, 10000M
        |__ Port 004: Dev 006, If 0, Class=Mass Storage, Driver=uas, 10000M
 

Edited by jeff_screws
add lsusb output

  • Author

I had the wrong device id.  This worked.

 

usb_storage.quirks=2109:0715:u

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.