8 TB WD MyBook Duo configured as a RAID 1 (Mirrored) 4 TB drive: mounts to USB 2.0 port, but not 3.0

[Thomas Bihn]

I posted here a little over a year ago with my WD 4 TB MyBook USB 3.0 drive connected to the USB 3.0 port. Everything has been working fine with it, but I wanted to get some piece of mind with data and bought a WD 8 TB MyBook Duo USB 3.0 drive that can be configured on a Windows PC to act as a RAID 1 array (Mirrored) 4TB drive.

When I attempt to mount it to the USB 3.0 port, the system log is as follows:

Apr 25 22:39:37 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Apr 25 22:39:37 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Apr 25 22:39:37 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Apr 25 22:39:37 kernel: usb 1-1: ep 0x81 - rounding interval to 128 microframes
Apr 25 22:39:37 kernel: xhci_hcd 0000:00:0c.0: WARN no SS endpoint bMaxBurst
Apr 25 22:39:37 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Apr 25 22:39:37 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Apr 25 22:39:37 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Apr 25 22:39:37 kernel: hub 1-1:1.0: config failed, can't read hub descriptor (err -22)​

It won't mount.

If I remove it from the USB 3.0 port and connect it to the USB 2.0 port, it mounts:

Apr 25 22:40:26 kernel: scsi 1:0:0:0: Direct-Access WD My Book Duo 0A10 1030 PQ: 0 ANSI: 6
Apr 25 22:40:26 kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
Apr 25 22:40:26 kernel: scsi 1:0:0:1: Enclosure WD SES Device 1030 PQ: 0 ANSI: 6
Apr 25 22:40:26 kernel: scsi 1:0:0:1: Attached scsi generic sg1 type 13
Apr 25 22:40:26 kernel: sd 1:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
Apr 25 22:40:26 kernel: sd 1:0:0:0: [sda] 7813974016 512-byte logical blocks: (4.00 TB/3.63 TiB)
Apr 25 22:40:26 kernel: sd 1:0:0:0: [sda] 4096-byte physical blocks
Apr 25 22:40:26 kernel: sd 1:0:0:0: [sda] Write Protect is off
Apr 25 22:40:26 kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Apr 25 22:40:26 kernel: sd 1:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
Apr 25 22:40:26 kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Apr 25 22:40:26 kernel: sd 1:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
Apr 25 22:40:26 kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Apr 25 22:40:26 kernel: sd 1:0:0:0: [sda] Attached SCSI disk
Apr 25 22:40:26 usb: USB /dev/sda1(unknown) failed to mount At the first try!
Apr 25 22:40:26 usb: USB /dev/sda2(ntfs) failed to mount At the first try!
Apr 25 22:40:30 usb: USB ntfs fs at /dev/sda2 mounted on /tmp/mnt/My_Book.
Apr 25 22:40:30 rc_service: hotplug 1552:notify_rc restart_nasapps
Apr 25 22:40:30 iTunes: daemon is stopped
Apr 25 22:40:30 FTP Server: daemon is stopped
Apr 25 22:40:32 Samba Server: smb daemon is stopped
Apr 25 22:40:32 kernel: gro disabled
Apr 25 22:40:33 Timemachine: daemon is stopped
Apr 25 22:40:33 miniupnpd[1325]: shutting down MiniUPnPd
Apr 25 22:40:33 kernel: gro enabled with interval 2
Apr 25 22:40:34 Samba Server: daemon is started
Apr 25 22:40:34 statd[1630]: Version 1.1.6 Starting
Apr 25 22:40:34 statd[1630]: statd running as root. chown /var/lib/nfs/sm to choose different user
Apr 25 22:40:34 kernel: svc: failed to register lockdv1 RPC service (errno 97).
Apr 25 22:40:36 miniupnpd[1643]: HTTP listening on port 34908
Apr 25 22:40:36 miniupnpd[1643]: Listening for NAT-PMP/PCP traffic on port 5351
Apr 25 23:06:11 disk_monitor: Got SIGALRM...
​

The drives seem to be configured by the WD utility as NTFS. Is there anything I can do to get this working on the USB 3.0 port? It's mounted, but looking at the log, it looks like it may be having issues there as well.

Do you have any recommendations for how I could possibly get this particular drive working with the Router or am I looking at needing to only attach this to a PC?

Thanks,
Tom

 

[hggomes]

Try this:

Wireless => Professional => Band (2.4GHZ) => Reducing USB 3.0 Interference => Disable

 

[Thomas Bihn]

Thanks for the quick response @hggomes. I saw that suggestion in another thread and tried it with the same results.

 

[hggomes]

Try a powercycle after.

 

[Thomas Bihn]

Thanks for the tips. It didn't work. I ended up calling New Egg and issuing an RMA. They were great. When I submitted the return online, it wanted to charge a $15 and $48 restocking fee so I backed out of that. I called them and they were able to issue an RMA giving me full return credit for the device as long as I took New Egg credit instead of refund to my card. I think that was fair of them. I'm going to go ahead and purchase an actual NAS device instead of trying to apply a USB NAS on the system.

 

[hggomes]

You are welcome.

 

[Thomas Bihn]

You are welcome.

I just re-read my post. I hope you didn't take it as upset, sarcastic, or snarky. The log for the failure on the USB 3.0 mount seemed to indicate the USB hub built into the drive was getting in the way. Thanks again!

 

[hggomes]

Surely not, why should I?

In case you didn't noticed I have "Like" your post, for your purpose a NAS probably makes more sense.

 

[sfx2000]

I just re-read my post. I hope you didn't take it as upset, sarcastic, or snarky. The log for the failure on the USB 3.0 mount seemed to indicate the USB hub built into the drive was getting in the way. Thanks again!

USB3 hubs have been fairly problematic across many linux distros... which explains the logs, and also why it does work with USB2...