Hi all, Im having some issues with setting up my new unraid server. Some background, When i first set it up with fresh drives and my DAS everything was working fine. I was able to get the two drivers Pre-cleared with no issues, then assigned and array was started and parity was created. I took the array down and restarted my machine, and then i ran into a lot of issues.

My system would no longer boot up and had a bunch of USB issues, so i saw in another post to try to use the usb_storage.quirks=174c:55aa:u in my syslinux config. Which allowed it to boot up and start rebuilding my parity. I ran a short SMART test on both of my drives and found no issues. I feel like every time i try to build the parity or try something new i get new errors every time.

However maybe 8min in to the rebuild i get a TON of disk read errors. Not sure if those are due to the HD or if they are due to the USB. Any ways... im trying to figure out if its just one component or everything that is having issues. That way i know if my drives are bad i can RMA them.

I have tried multiple USB cables, and one of the only ones that seemed to maybe work was a cheap phone charging one but my speeds were super slow.

anyways im not sure what kind of other information i need to include for troubleshooting. I know a DAS is not ideal, and now i know why... but it was just what was in my budget.

here are various diagnostics and syslogs from various errors and times ive tried.

centoria-syslog-20250530-0606.zipcentoria-diagnostics-20250530-0149.zipcentoria-diagnostics-20250529-1636.zip

Post the output from 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/4p, 480M

ID 0bda:5420 Realtek Semiconductor Corp.

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

ID 0bda:5420 Realtek Semiconductor Corp.

/: Bus 002.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 0bda:0420 Realtek Semiconductor Corp.

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

ID 0bda:0420 Realtek Semiconductor Corp.

|__ Port 001: Dev 006, If 0, Class=Mass Storage, Driver=usb-storage, 10000M

ID 174c:235c ASMedia Technology Inc.

|__ Port 002: Dev 005, If 0, Class=Mass Storage, Driver=usb-storage, 10000M

ID 174c:235c ASMedia Technology Inc.

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

ID 0781:cfcb SanDisk Corp.

When the drivers was the UAS, I had other issues with the parity not even starting.

I was still seeing UAS related errors logged, I assume this was before the change?

May 29 16:16:51 Centoria kernel: sd 1:0:0:0: [sdb] tag#24 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD

May 29 16:16:51 Centoria kernel: sd 1:0:0:0: [sdb] tag#24 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e0 00

May 29 16:16:51 Centoria kernel: scsi host1: uas_eh_device_reset_handler start

May 29 16:16:51 Centoria kernel: usb 2-4.3.1: reset SuperSpeed Plus Gen 2x1 USB device number 5 using xhci_hcd

Yea i believe that one was before the change. the 2 from 5/30 are the most recent ones with the change

OK, the other ones show what looks like a typical USB disconnect issue:

May 30 01:44:23 Centoria kernel: usb 2-1.3-port4: config error

May 30 01:44:24 Centoria kernel: usb 2-1.3-port1: config error

May 30 01:44:24 Centoria kernel: usb 2-1.3.1: USB disconnect, device number 5

May 30 01:44:24 Centoria kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache

May 30 01:44:24 Centoria kernel: sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK

May 30 01:44:25 Centoria kernel: usb 2-1.3-port4: config error

Try a different USB port, if you have already tried different cables, not much else you can do, this is one of the reasons USB devices are not recommended, they are prone to issues like these.