I'm building a backup unraid server using a mini PC and this 5 bay 3.5 inch enclosure from Sabrent. After OS install, initializing the array starts building parity and this may work fine for several hours until it fails. 

 

Oct  2 22:49:38 UNDEV kernel: usb 10-2: USB disconnect, device number 2
Oct  2 22:49:38 UNDEV kernel: usb 10-2.2: USB disconnect, device number 3
Oct  2 22:49:38 UNDEV kernel: sd 1:0:0:0: [sda] tag#16 uas_zap_pending 0 uas-tag 2 inflight: CMD 
Oct  2 22:49:38 UNDEV kernel: sd 1:0:0:0: [sda] tag#16 CDB: opcode=0x88 88 00 00 00 00 00 0c 3b 43 f0 00 00 02 88 00 00
Oct  2 22:49:38 UNDEV kernel: sd 1:0:0:0: [sda] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=0s
Oct  2 22:49:38 UNDEV kernel: sd 1:0:0:0: [sda] tag#16 CDB: opcode=0x88 88 00 00 00 00 00 0c 3b 43 f0 00 00 02 88 00 00

Here is the current USB stack
root@UNDEV:~# lsusb -t
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ehci-pci/6p, 480M
    |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 480M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=ehci-pci/6p, 480M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 006.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 007.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 008.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 009.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 003: Dev 004, If 0, Class=Hub, Driver=hub/4p, 480M
    |__ Port 009: Dev 003, If 0, Class=Mass Storage, Driver=usb-storage, 480M
/:  Bus 010.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    |__ Port 002: Dev 009, If 0, Class=Hub, Driver=hub/4p, 10000M
        |__ Port 002: Dev 010, If 0, Class=Mass Storage, Driver=uas, 10000M
        |__ Port 003: Dev 011, If 0, Class=Hub, Driver=hub/4p, 10000M
            |__ Port 001: Dev 012, If 0, Class=Mass Storage, Driver=uas, 10000M
            |__ Port 002: Dev 013, If 0, Class=Mass Storage, Driver=uas, 10000M
            |__ Port 003: Dev 014, If 0, Class=Mass Storage, Driver=uas, 10000M
            |__ Port 004: Dev 015, If 0, Class=Mass Storage, Driver=uas, 10000M
/:  Bus 011.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 480M
/:  Bus 012.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 5000M

I have tried to use "USB quirks" without success and I am not sure if I am missing something.

 

On my syslinux configuration, I added this, then rebooted, "create new configuration", setup array again and let it parity sync only for it to fail again. This enclosure has a USB hub also, do I need to use a quick on that PCI id too? 

 

label Unraid OS
  menu default
  kernel /bzimage
  append initrd=/bzroot usb-storage.quirks=174c:55aa:u

 

Thanks

undev-diagnostics-20241003-1047.zip

UBS is not recommended for array or pools, one of the reasons is because they have a tendency to drop offline, and using the old storage driver may not help, but you can try, quirk appears to be working, post the current 

lsusb -t

output, is the one posted current? It appears to be working in the syslog:

 

Oct  3 10:36:27 UNDEV kernel: usb 10-2.3.2: UAS is ignored for this device, using usb-storage instead

 

 

Are you running Unraid in a VM? I note the BIOS Model says Q35-9.0 and various other VM related devices..

 

I had issues with my USB enclosure passed through Proxmox on an Unraid VM (trialling Unraid 7 beta) with it dropping the odd disk..

 

Additionally, I have just finished using the same enclosure on a native Unraid server to pre-clear 3 x 14TB disks, then transfer 22TB of data and now in the last 5% of building parity, so around 7 days solid of hard use and no issues, it's a Terramaster D6-320 which looks to have the same ASM1051/ASM1153 chipset reported..

I haven't used any 'quirk' boot extension either, since it worked so well on pre-clearing I didn't want to chance it..

 

Apologies if I'm just muddying the waters out ignorance, I just had a similar issues once and wondered if it might be helpful.

 

 

 

Edited October 3, 20241 yr by Snubbers

13 minutes ago, Snubbers said:

Are you running Unraid in a VM? I note the BIOS Model says Q35-9.0 and various other VM related devices..

That's a good observation, and an additional layer that can also cause issues.

6 hours ago, Snubbers said:

Are you running Unraid in a VM? I note the BIOS Model says Q35-9.0 and various other VM related devices..

 

I had issues with my USB enclosure passed through Proxmox on an Unraid VM (trialling Unraid 7 beta) with it dropping the odd disk..

 

Additionally, I have just finished using the same enclosure on a native Unraid server to pre-clear 3 x 14TB disks, then transfer 22TB of data and now in the last 5% of building parity, so around 7 days solid of hard use and no issues, it's a Terramaster D6-320 which looks to have the same ASM1051/ASM1153 chipset reported..

I haven't used any 'quirk' boot extension either, since it worked so well on pre-clearing I didn't want to chance it..

 

Apologies if I'm just muddying the waters out ignorance, I just had a similar issues once and wondered if it might be helpful.

 

 

 

Yes, I am actually testing Unraid 7 on a Proxmox VM and I am passing thru the entire USB 3.2 controller.

 

On Proxmox host I am doing explicit USB detection blacklisting and driver blacklisting in combination, so disks never show up in proxmox by mistake. This is working, as I originally saw the problem was that disks were showing up in proxmox non-exclusively.

 

root@MS1:~# cat /etc/udev/rules.d/99-ignore-usb-device.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="2109", ATTR{idProduct}=="0822", ATTR{authorized}="0"
SUBSYSTEM=="usb", ATTR{idVendor}=="174c", ATTR{idProduct}=="55aa", ATTR{authorized}="0"
SUBSYSTEM=="usb", ATTR{idVendor}=="2109", ATTR{idProduct}=="2822", ATTR{authorized}="0"

root@MS1:~# cat /etc/modprobe.d/blacklist-usbstorage.conf
blacklist usb-storage
root@MS1:~# lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/3p, 20000M/x2
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
root@MS1:~#

 

7 hours ago, JorgeB said:

UBS is not recommended for array or pools, one of the reasons is because they have a tendency to drop offline, and using the old storage driver may not help, but you can try, quirk appears to be working, post the current 

lsusb -t

output, is the one posted current? It appears to be working in the syslog:

 

Oct  3 10:36:27 UNDEV kernel: usb 10-2.3.2: UAS is ignored for this device, using usb-storage instead

 

 

Yes, the quirk is working and I had checked it by running `cat /sys/module/usb_storage/parameters/quirks` which returned the quirk setting.

I have also experimented by removing the quirk and do notice the error messages change and say UAS driver in use.

 

Oct  3 18:27:27 UNDEV kernel: usb 10-1: USB disconnect, device number 2
Oct  3 18:27:27 UNDEV kernel: usb 10-1.2: USB disconnect, device number 3
Oct  3 18:27:27 UNDEV kernel: sd 1:0:0:0: [sda] tag#4 uas_zap_pending 0 uas-tag 1 inflight: CMD 
Oct  3 18:27:27 UNDEV kernel: sd 1:0:0:0: [sda] tag#4 CDB: opcode=0x88 88 00 00 00 00 00 00 5e 80 90 00 00 02 a0 00 00
Oct  3 18:27:27 UNDEV kernel: sd 1:0:0:0: [sda] tag#7 uas_zap_pending 0 uas-tag 2 inflight: CMD 
Oct  3 18:27:27 UNDEV kernel: sd 1:0:0:0: [sda] tag#7 CDB: opcode=0x88 88 00 00 00 00 00 00 5e 83 30 00 00 01 f8 00 00
Oct  3 18:27:27 UNDEV kernel: sd 1:0:0:0: [sda] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=0s
Oct  3 18:27:27 UNDEV kernel: sd 1:0:0:0: [sda] tag#4 CDB: opcode=0x88 88 00 00 00 00 00 00 5e 80 90 00 00 02 a0 00 00
Oct  3 18:27:27 UNDEV kernel: I/O error, dev sda, sector 6193296 op 0x0:(READ) flags 0x0 phys_seg 84 prio class 0

 

If you have any suggestions on how I could make this work I would appreciate it, I know its a bit of a complex setup as I try to maximize hardware usage without having to spin up a dedicated hardware for unraid backup server.

The only other issues you can run in to is if you are using power management (Powertop auto-tune, ASPM etc).. I had my flash drive disappear using Powertop --auto-tune, then I had one of my SSDs just drop off the bus entirely.. I also tried turning on ASPM to L1 in the BIOS for various PCI buses, but again, I started running in to IO errors, so pretty much went back to a more basic power management setup, and whilst doing disk swapping/parity builds I've got no power tweaks running at all..

 

The only other difference I see between your setup and mine, is my enclosure uses a Realtek USB Hub setup for ASM Sata bridge and you have VIA, I have no idea if either are more/less reliable/compatible than each other.. 

 

Finally, what is the Hardware you are running Proxmox on? being a USB Gen 3.2 10gbps enclosure some earlier USB implementations were very flaky, I've really only reliably had 10gbps and 20gbps (3.2 Gen 2x2) devices working on quite modern Intel hardware.

Edited October 4, 20241 yr by Snubbers

16 hours ago, Snubbers said:

The only other issues you can run in to is if you are using power management (Powertop auto-tune, ASPM etc).. I had my flash drive disappear using Powertop --auto-tune, then I had one of my SSDs just drop off the bus entirely.. I also tried turning on ASPM to L1 in the BIOS for various PCI buses, but again, I started running in to IO errors, so pretty much went back to a more basic power management setup, and whilst doing disk swapping/parity builds I've got no power tweaks running at all..

 

The only other difference I see between your setup and mine, is my enclosure uses a Realtek USB Hub setup for ASM Sata bridge and you have VIA, I have no idea if either are more/less reliable/compatible than each other.. 

 

Finally, what is the Hardware you are running Proxmox on? being a USB Gen 3.2 10gbps enclosure some earlier USB implementations were very flaky, I've really only reliably had 10gbps and 20gbps (3.2 Gen 2x2) devices working on quite modern Intel hardware.

powertop is a great tip. I am actually running `powertop --auto-tune` at boot on the proxmox host. Let me disable this and see if this changes things.

 

Proxmox host is a Minisforum MS-01 mini pc. Intel 12600H with vpro 32gb memory

I wasn't able to fix this issue when nesting unraid with proxmox as the hypervisor.

I put this USB3 enclosure on an older HP 800 G6 mini pc and booted unraid there, the system has been stable for 3 days.