NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS NV+ ate my WD20EZRX (2TB Green)?
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?
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?
19 Replies
Replies have been turned off for this discussion
- What firmware are you running in the NAS?
- Apologies, I should have included this:
Hostname: nas
Model: ReadyNAS NV+ [X-RAID]
Serial: 000da20190b1
Firmware: 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) - ....and this one:
viewtopic.php?p=380555#p380555
Symptoms are not typical as locked drives are normally not reported as bad by the readynas.
I agree with that, but I think they need to be unlocked in order to run the diags.vandermerwe wrote: ....and this one:
viewtopic.php?p=380555#p380555
Symptoms are not typical as locked drives are normally not reported as bad by the readynas.
KrisW - Vandermerwe's link tells you how to unlock the drives from a linux system. There is a windows version of hdparm here: http://disablehddapm.blogspot.com I've never tried it!- Once I find a system that will accept the disks, I'll try boot into Linux and try to remove the lock.
As for the cause, the drives were not locked by me. Nor were they unreadable when I put them into the ReadyNAS. The disks were new, in sealed packaging from WD. The locked/unreadable status resulted only after they failed in the ReadyNAS. Whatever is preventing their use now was done by the ReadyNAS.
It's possible that whatever is causing the "Bad Disk" error is taking the firmware down a code path where it does not unlock the drive afterwards. - Okay:
$ sudo -i
# hdparm --security-unlock NETGEAR
/dev/sdb security_password="NETGEAR"
/dev/sdb:
Issuing SECURITY_UNLOCK command, password="NETGEAR", user=user
SECURITY_UNLOCK: Input/output error
here's the dump of the disk info
# hdparm -I /dev/sdb
/dev/sdb:
ATA device, with non-removable media
Model Number: WDC WD20EZRX-00D8PB0
Serial Number: WD-WCC4M3RSE322
Firmware Revision: 80.00A80
Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
Supported: 9 8 7 6 5
Likely used: 9
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 3907029168
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
device size with M = 1024*1024: 1907729 MBytes
device size with M = 1000*1000: 2000398 MBytes (2000 GB)
cache/buffer size = unknown
Nominal Media Rotation Rate: 5400
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
* Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
SET_MAX security extension
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* 64-bit World wide name
* WRITE_UNCORRECTABLE_EXT command
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Gen3 signaling speed (6.0Gb/s)
* Native Command Queueing (NCQ)
* Host-initiated interface power management
* Phy event counters
* NCQ priority information
* unknown 76[15]
DMA Setup Auto-Activate optimization
Device-initiated interface power management
Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT LBA Segment Access (AC2)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
unknown 206[12] (vendor specific)
unknown 206[13] (vendor specific)
unknown 206[14] (vendor specific)
Security:
Master password revision code = 1
supported
enabled
locked
not frozen
expired: security count
supported: enhanced erase
Security level high
282min for SECURITY ERASE UNIT. 282min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50014ee20b408fd5
NAA : 5
IEEE OUI : 0014ee
Unique ID : 20b408fd5
Checksum: correct
I tried attaching the other disk back into the ReadyNAS. It acknowledges the insertion event, but then goes into CPU starvation: ssh won't respond, and the web UI won't load fully. - 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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
