steve1977 Posted April 10, 2020 Share Posted April 10, 2020 I have a USB dockingstation (2 harddisks). I'd love to add these as unassigned device. Somehow does not seem to be possible? No disk shows up as unassigned device. I tried various disks (formatted NTFS and XFS), but nothing works. Curious whether this is even possible? If so, what do I need to do? Attaching diagnostic log. Thanks! Can drives be either XFS or NTFS? Can I plug in/out the disks or does it need to be connected when starting Unraid? tower-diagnostics-20200410-1335.zip Quote Link to comment
JorgeB Posted April 10, 2020 Share Posted April 10, 2020 Before thinking of that I would worry about disk13 read errors: Apr 10 01:12:29 Tower kernel: ata7.00: configured for UDMA/33 Apr 10 01:12:29 Tower kernel: ata7: EH complete Apr 10 01:12:29 Tower kernel: ata7.00: exception Emask 0x50 SAct 0x8000000 SErr 0x4890800 action 0xe frozen Apr 10 01:12:29 Tower kernel: ata7.00: irq_stat 0x0c400040, interface fatal error, connection status changed Apr 10 01:12:29 Tower kernel: ata7: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } Apr 10 01:12:29 Tower kernel: ata7.00: failed command: READ FPDMA QUEUED Apr 10 01:12:29 Tower kernel: ata7.00: cmd 60/00:d8:90:37:3a/01:00:00:00:00/40 tag 27 ncq dma 131072 in Apr 10 01:12:29 Tower kernel: res 40/00:00:90:37:3a/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Apr 10 01:12:29 Tower kernel: ata7.00: status: { DRDY } Apr 10 01:12:29 Tower kernel: ata7: hard resetting link Apr 10 01:12:34 Tower kernel: ata7: link is slow to respond, please be patient (ready=0) Apr 10 01:12:39 Tower kernel: ata7: COMRESET failed (errno=-16) Apr 10 01:12:39 Tower kernel: ata7: hard resetting link Apr 10 01:12:40 Tower kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 10 01:12:42 Tower kernel: ata7.00: configured for UDMA/33 Apr 10 01:12:42 Tower kernel: sd 7:0:0:0: [sdo] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Apr 10 01:12:42 Tower kernel: sd 7:0:0:0: [sdo] tag#27 Sense Key : 0x5 [current] Apr 10 01:12:42 Tower kernel: sd 7:0:0:0: [sdo] tag#27 ASC=0x21 ASCQ=0x4 Apr 10 01:12:42 Tower kernel: sd 7:0:0:0: [sdo] tag#27 CDB: opcode=0x88 88 00 00 00 00 00 00 3a 37 90 00 00 01 00 00 00 Apr 10 01:12:42 Tower kernel: print_req_error: I/O error, dev sdo, sector 3815312 Apr 10 01:12:42 Tower kernel: md: disk13 read error, sector=3815248 Apr 10 01:12:42 Tower kernel: md: disk13 read error, sector=3815256 Apr 10 01:12:42 Tower kernel: md: disk13 read error, sector=3815264 Apr 10 01:12:42 Tower kernel: md: disk13 read error, sector=3815272 Apr 10 01:12:42 Tower kernel: md: disk13 read error, sector=3815280 Apr 10 01:12:42 Tower kernel: md: disk13 read error, sector=3815288 Apr 10 01:12:42 Tower kernel: md: disk13 read error, sector=3815296 Looks like a connection problem. Quote Link to comment
steve1977 Posted April 10, 2020 Author Share Posted April 10, 2020 My connection issue is the reason why I am looking for USB. I'd like to test something by shifting disks to USB. This will allow me to understand what's really happening. I keep having connection issues for many years and never found a sustainable solution. Any thoughts why my USB disks are not showing up? Quote Link to comment
JorgeB Posted April 10, 2020 Share Posted April 10, 2020 Harder to find when the log is full with other issues, reboot and after array start connect the USB drive, then post new diags. Quote Link to comment
steve1977 Posted April 10, 2020 Author Share Posted April 10, 2020 Thanks. I removed disk 13 and rebuild the array (without parity). Now only 14 disks as I removed 2 for trouble-shooting. I plugged in the USB after starting the array (only one USB disk to keep things simple). I refreshed UD, but doesn't show up. Any thoughts? Thanks for your help! tower-diagnostics-20200410-1751.zip Quote Link to comment
JorgeB Posted April 10, 2020 Share Posted April 10, 2020 There's a problem detecting the USB device even after multiple tries: Apr 10 17:50:57 Tower kernel: usb 1-6: new high-speed USB device number 4 using xhci_hcd Apr 10 17:51:03 Tower kernel: usb 1-6: unable to get BOS descriptor set Apr 10 17:51:08 Tower kernel: usb 1-6: unable to read config index 0 descriptor/start: -110 Apr 10 17:51:08 Tower kernel: usb 1-6: can't read configurations, error -110 Apr 10 17:51:08 Tower kernel: usb 1-6: new high-speed USB device number 5 using xhci_hcd Apr 10 17:51:14 Tower kernel: usb 1-6: unable to get BOS descriptor set Apr 10 17:51:19 Tower kernel: usb 1-6: unable to read config index 0 descriptor/start: -110 Apr 10 17:51:19 Tower kernel: usb 1-6: can't read configurations, error -110 Apr 10 17:51:19 Tower kernel: usb usb1-port6: attempt power cycle Apr 10 17:51:20 Tower kernel: usb 1-6: new high-speed USB device number 6 using xhci_hcd Apr 10 17:51:25 Tower kernel: usb 1-6: unable to read config index 0 descriptor/all Apr 10 17:51:25 Tower kernel: usb 1-6: can't read configurations, error -110 Apr 10 17:51:25 Tower kernel: usb 1-6: new high-speed USB device number 7 using xhci_hcd Apr 10 17:51:31 Tower kernel: usb 1-6: unable to get BOS descriptor set Apr 10 17:51:36 Tower kernel: usb 1-6: unable to read config index 0 descriptor/start: -110 Apr 10 17:51:36 Tower kernel: usb 1-6: can't read configurations, error -110 Apr 10 17:51:36 Tower kernel: usb usb1-port6: unable to enumerate USB device Try a different port but it's likely some problem with the enclosure itself. Quote Link to comment
steve1977 Posted April 10, 2020 Author Share Posted April 10, 2020 Got it. It does work with my notebook, so the USB dock is per se not broken. It may not be compatible with Unraid / Linux though? Quote Link to comment
JorgeB Posted April 10, 2020 Share Posted April 10, 2020 48 minutes ago, steve1977 said: It may not be compatible with Unraid / Linux though? Possibly. Quote Link to comment
Recommended Posts
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.