NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
pashalifi
Sep 14, 2020Aspirant
Externsl USB HDD not recognised by ReadyNAS RN102
I'm trying to connect an external HDD to the top back USB port on a ReadyNAS RN102, to copy files to and from the ReadyNAS to the HDD (a Western Digital 14TB Elements). The HDD is powered on and ...
- Sep 14, 2020
dmesg output below - not sure about the 'spinning up ... not responding ... timing out ... hardware error...' The device is brand new and working fine mounted to my Ubuntu Dell XPS for read and write, also working fine mounted to my Dune HD media player. So I think you may be right, the 14TB volume is too much.
Never mind, thanks for your help - I'll just copy to / from over the network instead.
Cheers, Stephen
[8437870.744004] usb 3-1: new SuperSpeed USB device number 2 using xhci_hcd [8437870.764542] usb 3-1: New USB device found, idVendor=1058, idProduct=25a3 [8437870.764561] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [8437870.764572] usb 3-1: Product: Elements 25A3 [8437870.764581] usb 3-1: Manufacturer: Western Digital [8437870.764591] usb 3-1: SerialNumber: 39524B575239574C [8437870.766214] usb-storage 3-1:1.0: USB Mass Storage device detected [8437870.766866] scsi host3: usb-storage 3-1:1.0 [8437871.765073] scsi 3:0:0:0: Direct-Access WD Elements 25A3 1030 PQ: 0 ANSI: 6 [8437871.769953] sd 3:0:0:0: Attached scsi generic sg2 type 0 [8437871.771099] sd 3:0:0:0: [sdc] Spinning up disk... [8437872.773731] ...not responding... [8438054.804657] sd 3:0:0:0: timing out command, waited 180s [8438234.824536] sd 3:0:0:0: timing out command, waited 180s [8438414.834014] sd 3:0:0:0: timing out command, waited 180s [8438414.834094] sd 3:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [8438414.834112] sd 3:0:0:0: [sdc] Sense Key : Hardware Error [current] [8438414.834152] sd 3:0:0:0: [sdc] ASC=0x44 <<vendor>>ASCQ=0x81 [8438594.854770] sd 3:0:0:0: timing out command, waited 180s [8438594.854851] sd 3:0:0:0: [sdc] Test WP failed, assume Write Enabled [8438774.874714] sd 3:0:0:0: timing out command, waited 180s [8438774.874794] sd 3:0:0:0: [sdc] Asking for cache data failed [8438774.874808] sd 3:0:0:0: [sdc] Assuming drive cache: write through [8438774.879952] sd 3:0:0:0: [sdc] Unit Not Ready [8438774.879979] sd 3:0:0:0: [sdc] Sense Key : Hardware Error [current] [8438774.880017] sd 3:0:0:0: [sdc] ASC=0x44 <<vendor>>ASCQ=0x81 [8438954.884145] sd 3:0:0:0: timing out command, waited 180s [8439134.904441] sd 3:0:0:0: timing out command, waited 180s [8439314.914554] sd 3:0:0:0: timing out command, waited 180s [8439314.914649] sd 3:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [8439314.914666] sd 3:0:0:0: [sdc] Sense Key : Hardware Error [current] [8439314.914706] sd 3:0:0:0: [sdc] ASC=0x44 <<vendor>>ASCQ=0x81 [8439314.915202] sd 3:0:0:0: timing out command, waited 30s [8439494.934127] sd 3:0:0:0: timing out command, waited 180s [8439674.944036] sd 3:0:0:0: timing out command, waited 180s [8439674.944126] sd 3:0:0:0: [sdc] Attached SCSI disk
pashalifi
Sep 14, 2020Aspirant
Thanks I'll take a look at that - I didn't consider the size of the drive was a factor but sounds likely! Cheers
pashalifi
Sep 14, 2020Aspirant
dmesg output below - not sure about the 'spinning up ... not responding ... timing out ... hardware error...' The device is brand new and working fine mounted to my Ubuntu Dell XPS for read and write, also working fine mounted to my Dune HD media player. So I think you may be right, the 14TB volume is too much.
Never mind, thanks for your help - I'll just copy to / from over the network instead.
Cheers, Stephen
[8437870.744004] usb 3-1: new SuperSpeed USB device number 2 using xhci_hcd [8437870.764542] usb 3-1: New USB device found, idVendor=1058, idProduct=25a3 [8437870.764561] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [8437870.764572] usb 3-1: Product: Elements 25A3 [8437870.764581] usb 3-1: Manufacturer: Western Digital [8437870.764591] usb 3-1: SerialNumber: 39524B575239574C [8437870.766214] usb-storage 3-1:1.0: USB Mass Storage device detected [8437870.766866] scsi host3: usb-storage 3-1:1.0 [8437871.765073] scsi 3:0:0:0: Direct-Access WD Elements 25A3 1030 PQ: 0 ANSI: 6 [8437871.769953] sd 3:0:0:0: Attached scsi generic sg2 type 0 [8437871.771099] sd 3:0:0:0: [sdc] Spinning up disk... [8437872.773731] ...not responding... [8438054.804657] sd 3:0:0:0: timing out command, waited 180s [8438234.824536] sd 3:0:0:0: timing out command, waited 180s [8438414.834014] sd 3:0:0:0: timing out command, waited 180s [8438414.834094] sd 3:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [8438414.834112] sd 3:0:0:0: [sdc] Sense Key : Hardware Error [current] [8438414.834152] sd 3:0:0:0: [sdc] ASC=0x44 <<vendor>>ASCQ=0x81 [8438594.854770] sd 3:0:0:0: timing out command, waited 180s [8438594.854851] sd 3:0:0:0: [sdc] Test WP failed, assume Write Enabled [8438774.874714] sd 3:0:0:0: timing out command, waited 180s [8438774.874794] sd 3:0:0:0: [sdc] Asking for cache data failed [8438774.874808] sd 3:0:0:0: [sdc] Assuming drive cache: write through [8438774.879952] sd 3:0:0:0: [sdc] Unit Not Ready [8438774.879979] sd 3:0:0:0: [sdc] Sense Key : Hardware Error [current] [8438774.880017] sd 3:0:0:0: [sdc] ASC=0x44 <<vendor>>ASCQ=0x81 [8438954.884145] sd 3:0:0:0: timing out command, waited 180s [8439134.904441] sd 3:0:0:0: timing out command, waited 180s [8439314.914554] sd 3:0:0:0: timing out command, waited 180s [8439314.914649] sd 3:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [8439314.914666] sd 3:0:0:0: [sdc] Sense Key : Hardware Error [current] [8439314.914706] sd 3:0:0:0: [sdc] ASC=0x44 <<vendor>>ASCQ=0x81 [8439314.915202] sd 3:0:0:0: timing out command, waited 30s [8439494.934127] sd 3:0:0:0: timing out command, waited 180s [8439674.944036] sd 3:0:0:0: timing out command, waited 180s [8439674.944126] sd 3:0:0:0: [sdc] Attached SCSI disk
- schumakuSep 14, 2020Guru - Experienced User
The sense key is coming from the HDD (or it's enclosure) and not from the ReadyNAS host. Hard to say what is causing it, low probability there is an interop issue.
[Edit] Coming back to this:
[8439314.914649] sd 3:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [8439314.914666] sd 3:0:0:0: [sdc] Sense Key : Hardware Error [current] [8439314.914706] sd 3:0:0:0: [sdc] ASC=0x44 <<vendor>>ASCQ=0x81
This indicates an interop issue - well possible the USB controller on the ReadyNAS would require a low level firmware/microcode update to handle large capacity drives.
- StephenBSep 14, 2020Guru - Experienced User
schumaku wrote:
This indicates an interop issue - well possible the USB controller on the ReadyNAS would require a low level firmware/microcode update to handle large capacity drives.
What firmware are you running?
- schumakuSep 14, 2020Guru - Experienced User
Worth checking the WD Elements firmware for upgrades using the WD Drive Utilities (I fear it's Windows only...)
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!