Hi guys,I bought two WD20EZRX - 00D8PB0 2TB "Green" drives to fit in my NV+ (v1, I guess - the PCB still says "Infrant"). The WD Green 20EARX model is on the compatibility list, and the EZRX should be equivalent according to the scheme on http://www.wdc.com/wdproducts/library/o ... 001028.pdf(To head off some obvious questions, these are brand-new OEM component drives from a reputable supplier, not discount disks farmed from retail portable HDs. I've also used WD Green in video streaming applications with no problems. )I did the usual backup of the existing volume, then power down, removed my existing HDs, did a Factory Reset on the NAS (my original firmware used 4k blocksize, so the original volume did too), and inserted one of the disks.After a long initialisation, I got a "Bad disk" error, so I tried the other instead, only to get the same thing.Unfortunately, not only do these disks now not work, but after their trip through the ReadyNAS, they won't even register on my desktop PC's SATA controller. Attempting to use them in a Dell PC results in a spurious "Password Required" message from the BIOS (the EZRX doesn't have a password feature).Mounting the disk in a USB enclosure looks better at first, but it is impossible to partition the disk - the partitioning operation times out. I'm in the process of RMAing the disks, but I'm concerned that all I'll get is another pair of sacrificial WD20EZRX.So, any idea what's going on here, and any ideas on how I can get my disks back if the RMA is rejected?

What firmware are you running in the NAS?

Apologies, I should have included this:Hostname: nasModel: ReadyNAS NV+ [X-RAID]Serial: 000da20190b1Firmware: RAIDiator 4.1.14 [1.00a043] Memory: 256 MB [2.5-3-3-7]

My guess is that the disks got locked somehow. You can google on ways to unlock (or perhaps mdgm will reach out to you).

The problem is that both disks worked before they were put into the ReadyNAS. I cannot now mount them anywhere to be able to unlock them: my desktop PC refuses to boot up if either disk is on the SATA bus at power-up. (I believe the Dell BIOS "password" prompt is spurious - the EZRX doesn't offer password protection as far as I can discover)

See this old thread: viewtopic.php?f=24&t=7600&p=42812I believe your drives ended up locked.

ReadyNAS NV+ ate my WD20EZRX (2TB Green)?

19 Replies

Replies have been turned off for this discussion

KrisW
Aspirant
Mar 27, 2015
The other disk is worse, with many, many bad sectors. I'm surprised - it's a long time since I've come across a defective HDD.

My initial test of the drives was a short format and random-read/write which didn't find enough bad sectors to tip the disk into failure status. But, after the ReadyNAS did its full write-readback test over the entire drive, and exposed all of the defective sectors, the SMART controller decided that the disk was indeed defective.

... And because the SMART status said "Failed", the ReadyNAS would no longer use the drive.

Mystery solved. Now I've got to get replacements....

Thanks for your help guys.
KrisW
Aspirant
Mar 26, 2015
Okay, the clouds are clearing a little.

Once connected to the WD diagnostics (via a USB enclosure), the disk I have with me reports a "Failed" SMART status - too many bad sectors. It appears that this disk is damaged, and the ReadyNAS is correct in showing "Bad Disk".

The disks passed a quick check before I put them into the ReadyNAS, but it seems the ReadyNAS does a read/write check over the whole disk, which would have caused the controller to log the bad sectors and place the drive into a Failed SMART status.

I will check the other disk, the one that claims to be locked, tomorrow. (this other disk is back with the reseller I bought it from)
KrisW
Aspirant
Mar 25, 2015
thanks, I'll try that..
StephenB
Guru - Experienced User
Mar 25, 2015
If you have a usb enclosure you should also be able to run the generic disk tests.
KrisW
Aspirant
Mar 25, 2015
Factory reset was performed with the WD disk alone in the unit.

My PC bootloader dies if I try to boot with the locked WD drive installed, so using any Windows SATA tool is problematic for me.

Luminary

Mar 25, 2015

KrisW wrote:
Factory reset resulted in the unit hanging at "Booting...", so I performed a USB Restore of the Raidiator4.1.8 firmware onto the NAS instead.

Now, on reboot, with the WD disk in bay 3, I get an "ERR: No Disks" on the LCD display. RAIDar tells me the same thing. "Setup" isn't available

The four LED indicators blink in this sequence: ".*..", "....","****","...." (Bay 2 lit, all off, all on, all off).

I repeated the test with the WD disk in Bay 1, and got the same result.

KrisW wrote:
Factory reset resulted in the unit hanging at "Booting...", so I performed a USB Restore of the Raidiator4.1.8 firmware onto the NAS instead. Now, on reboot, with the WD disk in bay 3, I get an "ERR: No Disks" on the LCD display. RAIDar tells me the same thing. "Setup" isn't available The four LED indicators blink in this sequence: "...", "....","***","...." (Bay 2 lit, all off, all on, all off). I repeated the test with the WD disk in Bay 1, and got the same result.

Just to isolate the problem further, is it possible that you factory reset your NAS using a spare disk other than your existing WD drives in order to check whether if there is a fault on the NAS chassis or with your existing WD drives...?

You may also run an Extended test to each of your existing WD drives using the WD Data Lifeguard Diagnostics for Windows: http://support.wdc.com/product/download ... =612&sid=3

KrisW
Aspirant
Mar 25, 2015
Okay...

Factory reset resulted in the unit hanging at "Booting...", so I performed a USB Restore of the Raidiator4.1.8 firmware onto the NAS instead.

Now, on reboot, with the WD disk in bay 3, I get an "ERR: No Disks" on the LCD display. RAIDar tells me the same thing. "Setup" isn't available

The four LED indicators blink in this sequence: ".*..", "....","****","...." (Bay 2 lit, all off, all on, all off).

I repeated the test with the WD disk in Bay 1, and got the same result.
mdgm-ntgr
NETGEAR Employee Retired
Mar 24, 2015
With the disks that aren't working if you are fine with wiping them can you try a factory reset using Flex-RAID?

1. Leave all locked drives in NV+
2. Perform factory default reset
3. From RAIDar, select flex RAID instead of XRAID
KrisW
Aspirant
Mar 24, 2015
Okay, assuming that the locking password for a drive locked by v1 is the following 32 bytes:

BE EF BE F0 BE F1 BE F2 BE F3 BE F4 BE F5 BE F6 BE F7 BE F8 BE F9 BE FA BE FB BE FC BE FD BE FE

(that's the resulting byte sequence of the code posted in the v1 link, for a big-endian CPU)

Here's my result (/dev/sdb is the device on Linux)

# hdparm --security-unlock $(echo -e '\xBE\xEF\xBE\xF0\xBE\xF1\xBE\xF2\xBE\xF3\xBE\xF4\xBE\xF5\xBE\xF6\xBE\xF7\xBE\xF8\xBE\xF9\xBE\xFA\xBE\xFB\xBE\xFC\xBE\xFD\xBE\xFE') /dev/sdb

security_password="��"

Issuing SECURITY_UNLOCK command, password="��", user=user
SECURITY_UNLOCK: Input/output error

The other failed disk is in my ReadyNAS. But for as long as it remains inserted in the NAS, the NAS becomes unresponsive to SSH or HTTP connection requests. This cannot be normal, expected behaviour. Any suggestions?
mdgm-ntgr
NETGEAR Employee Retired
Mar 24, 2015
The unlocking method you tried is for disks locked by a v2, not by the v1.

The link StephenB gave is for the v1

The link vandermerwe gave is for the v2.