Seems that when unraid wants to spin down a USB hard disk, the USB is disconnected.

afterward the USB  appears but as new diferent dev name, on this log you will notice it had name std and now sdd

Feb 15 01:55:20 segator-unraid kernel: usb 4-4: USB disconnect, device number 7
Feb 15 01:55:20 segator-unraid kernel: usb 4-4.1: USB disconnect, device number 8
Feb 15 01:55:20 segator-unraid kernel: sd 25:0:0:0: [sdt] Synchronizing SCSI cache
Feb 15 01:55:20 segator-unraid kernel: sd 25:0:0:0: [sdt] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Feb 15 01:55:21 segator-unraid kernel: usb 4-4: new SuperSpeed Gen 1 USB device number 9 using xhci_hcd
Feb 15 01:55:21 segator-unraid kernel: hub 4-4:1.0: USB hub found
Feb 15 01:55:21 segator-unraid kernel: hub 4-4:1.0: 3 ports detected
Feb 15 01:55:21 segator-unraid usb_manager: Info: rc.usb_manager usb_remove   /dev/bus/usb/004/008 004 008
Feb 15 01:55:21 segator-unraid usb_manager: Info: rc.usb_manager Device Match Seagate_Backup+_Hub_BK_NA9RLEDH vm:   004 008
Feb 15 01:55:21 segator-unraid usb_manager: Info: rc.usb_manager Removed Seagate_Backup+_Hub_BK_NA9RLEDH vm:  nostate 004 008
Feb 15 01:55:21 segator-unraid kernel: usb 4-4.1: new SuperSpeed Gen 1 USB device number 10 using xhci_hcd
Feb 15 01:55:21 segator-unraid kernel: usb-storage 4-4.1:1.0: USB Mass Storage device detected
Feb 15 01:55:21 segator-unraid kernel: scsi host3: usb-storage 4-4.1:1.0
Feb 15 01:55:22 segator-unraid usb_manager: Info: rc.usb_manager usb_remove  Seagate_Backup+_Hub_01CB1163B0XP /dev/bus/usb/004/007 004 007
Feb 15 01:55:22 segator-unraid usb_manager: Info: rc.usb_manager Device Match Seagate_Backup+_Hub_01CB1163B0XP vm:   004 007
Feb 15 01:55:22 segator-unraid usb_manager: Info: rc.usb_manager Removed Seagate_Backup+_Hub_01CB1163B0XP vm:  nostate 004 007
Feb 15 01:55:22 segator-unraid usb_manager: Info: rc.usb_manager usb_add Seagate_Backup+_Hub_01CB1163B0XP /dev/bus/usb/004/009 004 009
Feb 15 01:55:22 segator-unraid usb_manager: Info: rc.usb_manager Autoconnect No Mapping found Seagate_Backup+_Hub_01CB1163B0XP /dev/bus/usb/004/009 004 009 port 4-4
Feb 15 01:55:22 segator-unraid usb_manager: Info: rc.usb_manager usb_add Seagate_Backup+_Hub_BK_NA9RLEDH /dev/bus/usb/004/010 004 010
Feb 15 01:55:22 segator-unraid usb_manager: Info: rc.usb_manager Autoconnect No Mapping found Seagate_Backup+_Hub_BK_NA9RLEDH /dev/bus/usb/004/010 004 010 port 4-4.1
Feb 15 01:55:22 segator-unraid kernel: scsi 3:0:0:0: Direct-Access     Seagate  Backup+ Hub BK   D785 PQ: 0 ANSI: 6
Feb 15 01:55:22 segator-unraid kernel: sd 3:0:0:0: Attached scsi generic sg3 type 0
Feb 15 01:55:22 segator-unraid kernel: sd 3:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16).
Feb 15 01:55:22 segator-unraid kernel: sd 3:0:0:0: [sdd] 27344764927 512-byte logical blocks: (14.0 TB/12.7 TiB)
Feb 15 01:55:22 segator-unraid kernel: sd 3:0:0:0: [sdd] 4096-byte physical blocks
Feb 15 01:55:22 segator-unraid kernel: sd 3:0:0:0: [sdd] Write Protect is off
Feb 15 01:55:22 segator-unraid kernel: sd 3:0:0:0: [sdd] Mode Sense: 4f 00 00 00
Feb 15 01:55:22 segator-unraid kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 15 01:55:34 segator-unraid kernel: sdd: sdd1
Feb 15 01:55:34 segator-unraid kernel: sd 3:0:0:0: [sdd] Attached SCSI disk

 

Edited February 17, 20224 yr by segator

attach diagnostics to your NEXT post in this thread

1 hour ago, segator said:

 

afterward the USB  appears but as new diferent dev name, on this log you will notice it had name sdt and now sdd

It is quite normal form the device name to change if a drive disconnects and then reconnects as the sdX type names are assigned dynamically at the Linux level, so you can never assume they stay constant (this is one of the reasons Unraid identifies drives by their serial number and not the sdX type device Id).  This will cause problems if the USB drive is used in the array as the core Unraid system is not hot-plug compatible but if the disk is being used as a Unassigned Devices then the UD plugin should handle this OK.

segator-unraid-diagnostics-20220217-2035.zip

 

The affected disk is disk28

2 minutes ago, segator said:

segator-unraid-diagnostics-20220217-2035.zip 397.48 kB · 0 downloads

 

The affected disk is disk28

It is not normally recommended to have USB disks in the main array as if they disconnect for any reason and then reconnect with a different Id then Unraid will not handle this.    If this is only happening for you on a spindown/spinup sequence then you may get away with having it in the array if you disable spindown for that drive.

Ok I will try to disable spindown hdparm -S0 /dev/sdx it will be enough right?

30 minutes ago, segator said:

Ok I will try to disable spindown hdparm -S0 /dev/sdx it will be enough right?

I think itimpi meant click on the drive and set spin down to never for that drive from defau!t.

Got it I just disabled spindown on  unraid UI, I will let you know if the issue still happening.

Anyway I have other HDD via USB can be spinned down and no problems so far, also are plugged to the same USB controller.

Edited February 18, 20224 yr by segator

Just now, segator said:

Got it I just disabled spindown on  unraid UI, I will let you know if the issue still happening.

Anyway I have other HDD via USB can be spinned down and no problems so far, also are plugged to the same USB controller.

are they using same usb adapter? if not firmware may be different.

Your diagnostics show you don't have any parity disk. And in fact, I often recommend not bothering with parity when you have USB connected array disks, since disconnects will result in the array being out-of-sync with frequent rebuilds.

 

That is a lot of disks with no redundancy though. If you have a disk fail of course nothing you can do but copy from backup, but you would have to know what is on each disk.