NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WD My Book Essential 3TB USB 3.0 and NV+ v2
I naively bought a WD My Book Essential 3TB USB 3.0 (USB 2.0 compatible) for use as a backup drive for my NV+ v2 (with 3 x 3TB WD drives inside), having used a number of different USB 2.0 drives in the past successfully (2 x Samsung 1.5TB Story Stations, Buffalo 2.0 TB Just Store Desktop). Unfortunately the NV+ refuses to recognise the WD drive, either in the USB 3.0 ports or the front USB 2.0 port. The WD is formatted as NTFS, as were the other drives I have used.
I am currently using the WD drive as a backup via my iMac (connected using Gigabit Ethernet to the NAS), but it would be more convenient to use it directly with the NAS.
Has anyone successfully used this mainstream drive with an NV+ v2? Has anyone got any suggestions?
I am currently using the WD drive as a backup via my iMac (connected using Gigabit Ethernet to the NAS), but it would be more convenient to use it directly with the NAS.
Has anyone successfully used this mainstream drive with an NV+ v2? Has anyone got any suggestions?
31 Replies
Replies have been turned off for this discussion
- Netgear support has been poor so far.
Not happy at all.
very surprised this hasn't been sorted yet, especially since Chewbacca said in september its being looked at. - I have a 2TB version that works with my Pro 6. My vague recollection is that it didn't work with the USB 3.0 cable that came with the WD. You have to use a USB 2.0 cable. I'll look tonight though as I've got some seagates too and I might be confusing the cable issue with the different units. Meanwhile try a USB 2.0 cable. Also, I find the NAS to be be a little inconsistent with discovery when a device is attached, but if I reboot the NAS it always finds them. I'm using a USB hub but that should only make it less likely to work, not more :-).
steve - I take it back my Wd my book essential is just working fine with the USB 3.0 cable. It was the seagates that need the 2.0 cable to work. I don't remember doing anything special to get it to work. I think I did use the Wd tools to change the sleep timeout from a pc.
Steve - System can detect new WD My Book Esential USB 3.0 3TB, but can not mount automatically because can not find USB disk filesystem, please see below log, it is OK that mount manually via SSH.
eb 21 19:34:47 ted kernel: usb 3-2: new SuperSpeed USB device number 6 using xhci_hcd
Feb 21 19:34:47 ted kernel: xhci_hcd 0000:01:01.0: WARN: short transfer on control ep
Feb 21 19:34:47 ted last message repeated 5 times
Feb 21 19:34:47 ted kernel: scsi4 : usb-storage 3-2:1.0
Feb 21 19:34:48 ted kernel: scsi 4:0:0:0: Direct-Access WD My Book 1140 1012 PQ: 0 ANSI: 6
Feb 21 19:34:48 ted kernel: scsi 4:0:0:1: Enclosure WD SES Device 1012 PQ: 0 ANSI: 6
Feb 21 19:34:48 ted kernel: sd 4:0:0:0: [sdb] 732558336 4096-byte logical blocks: (3.00 TB/2.72 TiB)
Feb 21 19:34:48 ted kernel: xhci_hcd 0000:01:01.0: WARN: Stalled endpoint
Feb 21 19:34:48 ted kernel: sd 4:0:0:0: [sdb] Write Protect is off
Feb 21 19:34:48 ted kernel: sd 4:0:0:0: [sdb] Mode Sense: 47 00 10 08
Feb 21 19:34:48 ted kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Feb 21 19:34:48 ted kernel: sd 4:0:0:0: [sdb] 732558336 4096-byte logical blocks: (3.00 TB/2.72 TiB)
Feb 21 19:34:48 ted kernel: xhci_hcd 0000:01:01.0: WARN: Stalled endpoint
Feb 21 19:34:48 ted kernel: sd 4:0:0:0: Attached scsi generic sg1 type 0
Feb 21 19:34:48 ted kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Feb 21 19:34:48 ted kernel: sdb:
Feb 21 19:34:48 ted kernel: scsi 4:0:0:1: Attached scsi generic sg2 type 13
Feb 21 19:34:56 ted kernel: xhci_hcd 0000:01:01.0: WARN: Stalled endpoint
Feb 21 19:35:00 ted last message repeated 5 times
Feb 21 19:35:01 ted kernel: sdb1
Feb 21 19:35:01 ted kernel: sd 4:0:0:0: [sdb] 732558336 4096-byte logical blocks: (3.00 TB/2.72 TiB)
Feb 21 19:35:01 ted kernel: xhci_hcd 0000:01:01.0: WARN: Stalled endpoint
Feb 21 19:35:01 ted kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Feb 21 19:35:01 ted kernel: sd 4:0:0:0: [sdb] Attached SCSI disk
Feb 21 19:35:05 ted RAIDiator: Could not find a known filesystem on USB_HDD_1!
Then I format the USB deriver again on PC, system detect and mount successfully.root@ted:/var/log# mount
/dev/md0 on / type ext3 (rw,noatime)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw)
tmpfs on /ramfs type ramfs (rw)
tmpfs on /USB type tmpfs (rw,size=16k)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/c/c on /c type ext4 (rw,noatime,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0)
/dev/sdb1 on /USB/USB_HDD_2 type tntfs (rw,noatime,iostreaming)
/USB/USB_HDD_2 on /home/ftp/USB_HDD_2 type none (rw,bind) root@ted:/var/log# - So I need to reformat the drive ?
- Yes it appears the filesystem on the 3TB is not readable by the readynas. Not sure why. Maybe these are the Apple versions of the MyBook? Regardless if you put something it understands on there it should show up then. If you have ssh access you could format it from the readynas. I'd use "mkfs.ext4 -m 0 /dev/sd<whatever>". There is a problem with timestamps backing up to ext3 USB drives from your main /c storage but it works great if you use ext4. NTFS formatted from windows will work but ntfs uses more cpu on the nas from what I've seen.
dsm1212 wrote: Yes it appears the filesystem on the 3TB is not readable by the readynas. Not sure why. Maybe these are the Apple versions of the MyBook? Regardless if you put something it understands on there it should show up then. If you have ssh access you could format it from the readynas. I'd use "mkfs.ext4 -m 0 /dev/sd<whatever>". There is a problem with timestamps backing up to ext3 USB drives from your main /c storage but it works great if you use ext4. NTFS formatted from windows will work but ntfs uses more cpu on the nas from what I've seen.
This doesn't work, at least for me, I can see the drive and all the data when I access it using my pc, but I can't read or write to it, DLNA doesn't work on it either.
Seem's stupid to me, why don't the drives work, really am disappointed with netgear at the moment, So many issue's, no fix's- Hmm. Maybe this is a kernel bug. Looks like there is a usb3.0 patch for 2.6.39 that might be relevant. See https://bugs.launchpad.net/ubuntu/+sour ... bug/647973. Reading this it sounds like there are really two symptoms: 1) won't mount OR 2) if you do get it mounted performance could be very poor. Good luck getting it out of Netgear :-(. Probably easier to return the WD and buy a different model if you still can.
steve dsm1212 wrote: Hmm. Maybe this is a kernel bug. Looks like there is a usb3.0 patch for 2.6.39 that might be relevant. See https://bugs.launchpad.net/ubuntu/+sour ... bug/647973. Reading this it sounds like there are really two symptoms: 1) won't mount OR 2) if you do get it mounted performance could be very poor. Good luck getting it out of Netgear :-(. Probably easier to return the WD and buy a different model if you still can.
steve
Hmm, I was thinking of buying a 3TB WD RED/Green and a USB 3 Enclosure, surely that should work?- Total guessing, but I don't think it's the drive here. It's the USB support in the WD enclosure being somehow incompatible with USB support in the NV+ v2. I have 3 seagate USB encl and 1 WD MyBook. They all work fine with my Pro 6 (which only supports USB 2.0).
steve
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
