hello,

trying to do an external backup from my unraid server , i noticed one of the 6 external drives dissapeared.

after checking logs i see these events nonstop , no matter which external drive ,every time is a different "port":

TLDR its a 6 disk enclosure but only 5 works

Mar 5 20:56:30 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 35 using xhci_hcd

Mar 5 20:56:30 NOSTROMO kernel: usb 1-4.3.4: Device not responding to setup address.

Mar 5 20:56:30 NOSTROMO kernel: usb 1-4.3.4: Device not responding to setup address.

Mar 5 20:56:30 NOSTROMO kernel: usb 1-4.3.4: device not accepting address 35, error -71

Mar 5 20:56:35 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 37 using xhci_hcd

Mar 5 20:56:39 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 38 using xhci_hcd

Mar 5 20:56:43 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 39 using xhci_hcd

Mar 5 20:56:43 NOSTROMO kernel: usb 1-4.3.4: Device not responding to setup address.

Mar 5 20:56:44 NOSTROMO kernel: usb 1-4.3.4: Device not responding to setup address.

Mar 5 20:56:44 NOSTROMO kernel: usb 1-4.3.4: device not accepting address 39, error -71

Mar 5 20:56:48 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 41 using xhci_hcd

Mar 5 20:56:52 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 42 using xhci_hcd

Mar 5 20:56:57 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 43 using xhci_hcd

Mar 5 20:57:01 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 44 using xhci_hcd

Mar 5 20:57:06 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 45 using xhci_hcd

Mar 5 20:57:10 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 46 using xhci_hcd

Mar 5 20:57:15 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 47 using xhci_hcd

Mar 5 20:57:19 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 48 using xhci_hcd

Mar 5 20:57:23 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 49 using xhci_hcd

Mar 5 20:57:28 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 50 using xhci_hcd

Mar 5 20:57:32 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 51 using xhci_hcd

Mar 5 20:57:37 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 52 using xhci_hcd

Mar 5 20:57:41 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 53 using xhci_hcd

Mar 5 20:57:45 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 54 using xhci_hcd

Mar 5 20:57:45 NOSTROMO kernel: usb 1-4.3.4: Device not responding to setup address.

Mar 5 20:57:46 NOSTROMO kernel: usb 1-4.3.4: Device not responding to setup address.

Mar 5 20:57:46 NOSTROMO kernel: usb 1-4.3.4: device not accepting address 54, error -71

Mar 5 20:57:50 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 56 using xhci_hcd

Mar 5 20:57:54 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 57 using xhci_hcd

Mar 5 20:57:59 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 58 using xhci_hcd

Mar 5 20:57:59 NOSTROMO kernel: usb 1-4.3.4: Device not responding to setup address.

Mar 5 20:57:59 NOSTROMO kernel: usb 1-4.3.4: Device not responding to setup address.

Mar 5 20:57:59 NOSTROMO kernel: usb 1-4.3.4: device not accepting address 58, error -71

Mar 5 20:58:03 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 60 using xhci_hcd

Mar 5 20:58:08 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 61 using xhci_hcd

Mar 5 20:58:12 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 62 using xhci_hcd

Mar 5 20:58:16 NOSTROMO kernel: usb 1-4.3.4: new high-speed USB device number 63 using xhci_hcd

the fun part is that this setup worked 3 years without a single issue in truenas :S ,so i dont think is a cable/DaS/Disk problem. It seems more like a bug or issue with unraid.

can anyone help me ?

i tested the enclosure with several systems ,even in my steamdeck and every time it shows the 6 drives ,thasts why i ruled out a problem in the setup....

with unraid it works for a few mins if i pull all disks and attach one by one, but after a few minutes the error pop and a random drive dissapear again.

The DaS is a TerraMaster D6-320 using USB-C

nostromo-diagnostics-20260305-2102.zip

if it helps ,it worked before with unraid , seeing my own post (stupid me) i pasted a screenshoot of the machine doing a backup to the DaS here https://forums.unraid.net/topic/191977-help-with-diagnostic/#comment-1567708

so maybe its a kernel or update issue , its been a long time since i tried to do a full backup , my bad

USB problems:

Mar 5 21:01:57 NOSTROMO kernel: usb 1-4: USB disconnect, device number 4

Mar 5 21:01:57 NOSTROMO kernel: usb 1-4.1: USB disconnect, device number 6

Mar 5 21:01:57 NOSTROMO kernel: sd 33:0:0:0: [sdg] Synchronizing SCSI cache

Mar 5 21:01:57 NOSTROMO kernel: sd 33:0:0:0: [sdg] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK

Mar 5 21:01:57 NOSTROMO kernel: usb 1-4.3: USB disconnect, device number 5

Mar 5 21:01:57 NOSTROMO kernel: usb 1-4.3.1: USB disconnect, device number 8

Mar 5 21:01:57 NOSTROMO kernel: sd 36:0:0:0: [sdj] Synchronizing SCSI cache

Mar 5 21:01:57 NOSTROMO kernel: sd 36:0:0:0: [sdj] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK

Mar 5 21:01:57 NOSTROMO kernel: usb 1-4.3.2: USB disconnect, device number 9

Mar 5 21:01:57 NOSTROMO kernel: sd 37:0:0:0: [sdk] Synchronizing SCSI cache

Mar 5 21:01:57 NOSTROMO kernel: sd 37:0:0:0: [sdk] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK

Mar 5 21:01:57 NOSTROMO kernel: usb 1-4.3.3: USB disconnect, device number 10

Mar 5 21:01:57 NOSTROMO kernel: sd 34:0:0:0: [sdh] Synchronizing SCSI cache

Mar 5 21:01:57 NOSTROMO kernel: sd 34:0:0:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK

Mar 5 21:01:57 NOSTROMO kernel: usb 1-4.4: USB disconnect, device number 7

Mar 5 21:01:57 NOSTROMO kernel: sd 35:0:0:0: [sdi] Synchronizing SCSI cache

Mar 5 21:01:58 NOSTROMO kernel: sd 35:0:0:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK

Please note that USB is not recommended for array or pool devices; one of the reasons is that they have a tendency to drop for no reason. You can try a different USB port or cable.

On 3/6/2026 at 8:40 AM, JorgeB said:

USB problems:

Mar 5 21:01:57 NOSTROMO kernel: usb 1-4: USB disconnect, device number 4

Mar 5 21:01:57 NOSTROMO kernel: usb 1-4.1: USB disconnect, device number 6

Mar 5 21:01:57 NOSTROMO kernel: sd 33:0:0:0: [sdg] Synchronizing SCSI cache

Mar 5 21:01:57 NOSTROMO kernel: sd 33:0:0:0: [sdg] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK

Mar 5 21:01:57 NOSTROMO kernel: usb 1-4.3: USB disconnect, device number 5

Mar 5 21:01:57 NOSTROMO kernel: usb 1-4.3.1: USB disconnect, device number 8

Mar 5 21:01:57 NOSTROMO kernel: sd 36:0:0:0: [sdj] Synchronizing SCSI cache

Mar 5 21:01:57 NOSTROMO kernel: sd 36:0:0:0: [sdj] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK

Mar 5 21:01:57 NOSTROMO kernel: usb 1-4.3.2: USB disconnect, device number 9

Mar 5 21:01:57 NOSTROMO kernel: sd 37:0:0:0: [sdk] Synchronizing SCSI cache

Mar 5 21:01:57 NOSTROMO kernel: sd 37:0:0:0: [sdk] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK

Mar 5 21:01:57 NOSTROMO kernel: usb 1-4.3.3: USB disconnect, device number 10

Mar 5 21:01:57 NOSTROMO kernel: sd 34:0:0:0: [sdh] Synchronizing SCSI cache

Mar 5 21:01:57 NOSTROMO kernel: sd 34:0:0:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK

Mar 5 21:01:57 NOSTROMO kernel: usb 1-4.4: USB disconnect, device number 7

Mar 5 21:01:57 NOSTROMO kernel: sd 35:0:0:0: [sdi] Synchronizing SCSI cache

Mar 5 21:01:58 NOSTROMO kernel: sd 35:0:0:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK

Please note that USB is not recommended for array or pool devices; one of the reasons is that they have a tendency to drop for no reason. You can try a different USB port or cable.

this is caused when i power off the enclosure ,it always pop in truenas also .

note that drives are powered down when this happens ,so i never had a data corrruption problem

Thing is the enclosure works in several devices ,but not unraid ,and it worked in the past. Do you know if there is a usb bug or something related that can point me in the right direction?

ive tried 3 cables but each one have the same problem after a few seconds

the usb array is for offline backup ,not for daily operation :)

Edited March 7Mar 7 by ARMITAGEIII

You can try disabling the UASP driver, to see if it works better with the old usb-storage one, post new diags after a reboot when all devices are online.

On 3/8/2026 at 10:14 AM, JorgeB said:

You can try disabling the UASP driver, to see if it works better with the old usb-storage one, post new diags after a reboot when all devices are online.

how do i disable USAP in unraid?

On 3/8/2026 at 9:14 AM, JorgeB said:

post new diags after a reboot when all devices are online.

so i just need to reboot the unit with external array on ? thats how you disable uasp driver?

I need to see the diags with the unit connected and working.

well .it fixed itself ,i really did nothing xD

here are the logs and a screenshoot from the backup im currently running:

nostromo-diagnostics-20260312-0125.zip

seems like the ol "reboot to see if it works" really did hahahaha

If it happens again and you want to try with the USB storage drive, add this to syslinux.cfg:

usb_storage.quirks=0480:a006:u

Note that sometimes changing the driver can make the device IDs also change, so it would require a new config, but it should not happen in this case since they are already using the actual disk IDs.

will do ,it happened again and im not sure what causes it.

ill let you know if this fix works

10 hours ago, JorgeB said:

If it happens again and you want to try with the USB storage drive, add this to syslinux.cfg:

usb_storage.quirks=0480:a006:u

Note that sometimes changing the driver can make the device IDs also change, so it would require a new config, but it should not happen in this case since they are already using the actual disk IDs.

sigh

added the line ,still happening ,the funny thing is that never is the same drive ,nor the same slot. also if i use the DaS in other devices works flawless.

could it be some bios setting? im quite lost here.

motherboard is an erying 12500h with 32gb ram ,a nvme to sata adapter and i tried 3 usb c cables with the exact same result :(

It needs to be in the same line as append, after /bzroot, leave just a space

Like this i hope¡¡ will try tonight doing a full backup with rsync , hope it works.If not i will attach the DaS to my main computer which also has 10gbps optical fiber and do the backup the old way ,copy and paste using windows (EWWWWWW)

19 minutes ago, ARMITAGEIII said:

Like this i hope¡¡ will try tonight doing a full backup with rsync , hope it works.If not i will attach the DaS to my main computer which also has 10gbps optical fiber and do the backup the old way ,copy and paste using windows (EWWWWWW)

Mar 12 23:47:42 NOSTROMO kernel: usb 1-4.3.2: new high-speed USB device number 42 using xhci_hcd

Mar 12 23:47:42 NOSTROMO kernel: usb 1-4.3.2: Device not responding to setup address.

Mar 12 23:47:43 NOSTROMO kernel: usb 1-4.3.2: Device not responding to setup address.

Mar 12 23:47:43 NOSTROMO sysDrivers: SysDrivers Build Complete

Mar 12 23:47:43 NOSTROMO kernel: usb 1-4.3.2: device not accepting address 42, error -71

Mar 12 23:47:47 NOSTROMO kernel: usb 1-4.3.2: new high-speed USB device number 44 using xhci_hcd

Mar 12 23:47:51 NOSTROMO kernel: usb 1-4.3.2: new high-speed USB device number 45 using xhci_hcd

Mar 12 23:47:56 NOSTROMO kernel: usb 1-4.3.2: new high-speed USB device number 46 using xhci_hcd

Mar 12 23:48:00 NOSTROMO kernel: usb 1-4.3.2: new high-speed USB device number 47 using xhci_hcd

Mar 12 23:48:00 NOSTROMO kernel: usb 1-4.3.2: Device not responding to setup address.

Mar 12 23:48:00 NOSTROMO kernel: usb 1-4.3.2: Device not responding to setup address.

Mar 12 23:48:00 NOSTROMO kernel: usb 1-4.3.2: device not accepting address 47, error -71

Mar 12 23:48:05 NOSTROMO kernel: usb 1-4.3.2: new high-speed USB device number 49 using xhci_hcd

Mar 12 23:48:09 NOSTROMO kernel: usb 1-4.3.2: new high-speed USB device number 50 using xhci_hcd

Mar 12 23:48:13 NOSTROMO kernel: usb 1-4.3.2: new high-speed USB device number 51 using xhci_hcd

Mar 12 23:48:13 NOSTROMO kernel: usb 1-4.3.2: Device not responding to setup address.

Mar 12 23:48:14 NOSTROMO kernel: usb 1-4.3.2: Device not responding to setup address.

Mar 12 23:48:14 NOSTROMO kernel: usb 1-4.3.2: device not accepting address 51, error -71

Mar 12 23:48:18 NOSTROMO kernel: usb 1-4.3.2: new high-speed USB device number 53 using xhci_hcd

Mar 12 23:48:27 NOSTROMO kernel: usb 1-4.3.2: new high-speed USB device number 55 using xhci_hcd

maybe its time to find a new DaS or use a NaS to backup my main NaS ,which sounds stupid :/

11 minutes ago, ARMITAGEIII said:

use a NaS to backup my main NaS

My backup NAS is made of parts I had after various upgrades to my main NAS, including the drives.

1 hour ago, trurl said:

My backup NAS is made of parts I had after various upgrades to my main NAS, including the drives.

i have a spare motherboard with i7 6700k with 8 sata ports so... ,its tinkering time :P. also i have another unraid license ,the older ones :)

well... it was the usb C cable

4 cables failed and 1 cable chinese brand and cheap ,works flawless...

one of the cables the original one is 60 euros 2 meters 40 gbps 240W and 8k usb c

so... chinese no brand wins ¬¬

if it happens one more time ill build another server with unraid to backup my main server, DaS sucks tbh. and optical fiber cabins are too expensive for my use

thank you everyone for the tips :3

On 3/15/2026 at 12:20 AM, ARMITAGEIII said:

well... it was the usb C cable

4 cables failed and 1 cable chinese brand and cheap ,works flawless...

one of the cables the original one is 60 euros 2 meters 40 gbps 240W and 8k usb c

so... chinese no brand wins ¬¬

if it happens one more time ill build another server with unraid to backup my main server, DaS sucks tbh. and optical fiber cabins are too expensive for my use

thank you everyone for the tips :3

finally found the problem ,seems that something failed internally and only detect disk in "low speed mode" . so ill build a nas ,to backup my main nas :(

On 3/16/2026 at 10:29 AM, ARMITAGEIII said:

finally found the problem ,seems that something failed internally and only detect disk in "low speed mode" . so ill build a nas ,to backup my main nas :(

well, finally i located and fixed the issue :

It was dirt in the internal conectors in the DaS enclosure , cleaned it with 99% isopropyl alcohol and its working 4 hours ongoing

hope it helps someone in the future¡¡

as you can see in the attached image ,all six drives are detected and working ,and not a single error in syslog

nostromo-diagnostics-20260321-2200.zip

here is a sample picture with the exact zone where the dirt was ,as an advice ,clean every single slot with alcohol, included sata ports/usb C and the board in both sides

Edited March 21Mar 21 by ARMITAGEIII
grammar and example image