NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
stivo
Feb 01, 2011Follower
WD20EARS-00MVWB0 - works with NV+ or not?
Could it be clarified if WD20EARS-00MVWB0 Western Digital hard drive is officially compatible with NV+?
This is the latest model which retailers stock at the moment. I doubt the approved one can actually be found, at least not here in Australia.
Cheers,
Steve
This is the latest model which retailers stock at the moment. I doubt the approved one can actually be found, at least not here in Australia.
Cheers,
Steve
21 Replies
Replies have been turned off for this discussion
- zestAspirantgblades,
are you saying you have a 4 bay NV+ with WD20EARS-00MVWB0 (fully populated, eg 4 drives) and it all worked at rel 4.1.6?
I belive it is not supposed to work unless you get firmware up to 4.1.7.
I got mine upgraded to 4.1.7 using an older Seagate 400GB (HCL approved drive).
I then inserted another HCL approved drive HCL 2TB WD20EARS 00S8B1 - all synced well and as expected I got fully redundant 384GB across the two drives (equivalent to the smaller drive)
All well up to this point.
Last night while powered down I removed the 400GB Seagate and replaced it with 2TB WD20EARS-00MVWB0 -
so I had two bays with 2TB in each (WD20EARS-00MVWB0 + WD20EARS 00S8B1)
after a long re-sync process all seems fine BUT I only got 384GB volume across the two 2TB drives!
How do I extend it to full 2TB?
zest - mdgm-ntgrNETGEAR Employee RetiredYou're supposed to factory default after upgrading to 4.1.7 or you may have poor write performance using the WD20EARS. 4k sector alignment requires a factory default after updating to 4.1.7.
There's also the adding support for drives that don't support TLER in 4.1.7.
As for expanding your volume have you tried a reboot? - gbladesAspirantI only had 2 drives when it worked in 4.1.6.
The quickest way I found to upgrade to 4.1.7 with these drives is as follows and this is what I did after seeing that it was working in 4.1.6. I did this because of the fact it should have a factory reset after the 4.1.7 update
1) Put in 1 drive only and perform a factory reset.
2) As there is 1 drive after it boots there is no rebuild going on in the background so you can go straight ahead and install the update.
3) Let it reboot into 4.1.7 to make sure it has loaded ok.
4) Shutdown and fit the additional drives.
5) Perform a factory reset. - zestAspirantI need to report that after reboot my X-RAID picked up and expanded the second and third disk
so my current config is:
bay1: WD20EARS-00MVWB0
bay2: WD20EARS 00S8B1
bay3: WD20EARS-00MVWB0
bay4: WD20EARS-00MVWB0
634 GB (17%) of 3692 GB used
Ch 1 : WDC WD20EARS-00MVWB0 [1862 GB] 1859 GB allocated
Ch 2 : WDC WD20EARS-00S8B1 [1862 GB] 1859 GB allocated
Ch 3 : WDC WD20EARS-00MVWB0 [1862 GB] 1859 GB allocated
My latest problem is the error I'm getting when adding the fourth disk:
-------------
The disk attached to channel 4 could not be initialized. The most common reasons are RAID resync in progress, faulty drives, and disks that are too small to be added to the array.
[Mon Feb 14 19:46:59 EST 2011]
--------------
I have tried reboot a few times, I have also tried to init/format disk under XP - no problems. Still will not work under NV+ with the error as above.
Also I am not sure if I need to do anything about LCC
DISK1
Raw Read Error Rate 0
Spin Up Time 1000
Start Stop Count 16
Reallocated Sector Count 0
Seek Error Rate 0
Power On Hours 109
Spin Retry Count 0
Calibration Retry Count 0
Power Cycle Count 14
Power-Off Retract Count 13
Load Cycle Count 3051
Temperature Celsius 31
Reallocated Event Count 0
Current Pending Sector 0
Offline Uncorrectable 0
UDMA CRC Error Count 0
Multi Zone Error Rate 0
ATA Error Count 0
DISK2
Raw Read Error Rate 0
Spin Up Time 9308
Start Stop Count 43
Reallocated Sector Count 0
Seek Error Rate 0
Power On Hours 126
Spin Retry Count 0
Calibration Retry Count 0
Power Cycle Count 42
Power-Off Retract Count 41
Load Cycle Count 3667
Temperature Celsius 35
Reallocated Event Count 0
Current Pending Sector 0
Offline Uncorrectable 0
UDMA CRC Error Count 0
Multi Zone Error Rate 0
ATA Error Count 114
DISK1
Raw Read Error Rate 0
Spin Up Time 966
Start Stop Count 15
Reallocated Sector Count 0
Seek Error Rate 0
Power On Hours 94
Spin Retry Count 0
Calibration Retry Count 0
Power Cycle Count 13
Power-Off Retract Count 12
Load Cycle Count 2628
Temperature Celsius 33
Reallocated Event Count 0
Current Pending Sector 0
Offline Uncorrectable 0
UDMA CRC Error Count 0
Multi Zone Error Rate 0
ATA Error Count 0
Please advise ...
zest - TechZ1AspirantAfter reading quite a few threads and not wanting to start another one, there's just 1 query someone needs to answer:
WD20EARS-00MVWB0 drives, NV+ NAS, 4.1.7 firmware...should end-users do ANYTHING on the TLER issue or not? - mdgm-ntgrNETGEAR Employee RetiredShouldn't be a need to do anything regarding TLER if you're running 4.1.7 (or later once newer firmware is released) on a NV+.
See http://www.readynas.com/RAIDiator_4_1_7_Notesyoh-dah wrote:
New features and enhancements
8. Added support for WD drives that don’t support TLER.
The factory default on 4.1.7 is still needed to get the 4k sector alignment though. - TechZ1Aspirant
mdgm wrote: Shouldn't be a need to do anything regarding TLER if you're running 4.1.7 (or later once newer firmware is released) on a NV+.
See http://www.readynas.com/RAIDiator_4_1_7_Notesyoh-dah wrote:
New features and enhancements
8. Added support for WD drives that don’t support TLER.
The factory default on 4.1.7 is still needed to get the 4k sector alignment though.
Thanks mdgm, you're always one to help out here :)
The point #8 really didn't make much sense to me (and I'm sure others), it says it adds support for WD drives that DON'T support TLER...my English must be failing me since to me it means that it now supports those WD drives that don't have TLER? - PapaBear1ApprenticeWD has discontinued support for TLER on recent firmware revisions of some of their drives.
- TechZ1AspirantA very good thread that clarifies some points is here (Netgear, you really need to update your FAQ about WD EARS/EADS drives and their revisions!)
The LCC issue is somewhat alarming, especially given the stock values that WD ships its drives with.I read somewhere that the WD20EARS is designed for around 1,000,000 LCC and at the rate of around 3000 per day thats 1000000/3000=333.3' Days for design life failure..
A guesstimation forcast of less than a year before harddrive failures.
Not at all something an end-user wants to hear! - TechZ1Aspirant
TechZ wrote: A very good thread that clarifies some points is here (Netgear, you really need to update your FAQ about WD EARS/EADS drives and their revisions!)
The LCC issue is somewhat alarming, especially given the stock values that WD ships its drives with.I read somewhere that the WD20EARS is designed for around 1,000,000 LCC and at the rate of around 3000 per day thats 1000000/3000=333.3' Days for design life failure..
A guesstimation forcast of less than a year before harddrive failures.
Not at all something an end-user wants to hear!
A friend of mine just setup an identical NAS: WD20EARS-00MVWB0 x4 + an NV+, the LCC is at 9858 after 254 hours of operation.
Related Content
- Sep 05, 2011Retired_Member
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!