NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WD10EARS-00MVWB0
This drive is apparently supported, however I have 1 installed and it's showing 12 ATA errors. Does this mean that actually this will start increasing and eventually fail?
Model: WDC WD10EARS-00MVWB0
Serial: WD-WCAZA7512688
Firmware: 51.0AB51
SMART Attribute
Raw Read Error Rate 0
Spin Up Time 1191
Start Stop Count 10
Reallocated Sector Count 0
Seek Error Rate 0
Power On Hours 1
Spin Retry Count 0
Calibration Retry Count 0
Power Cycle Count 8
Power-Off Retract Count 7
Load Cycle Count 39
Temperature Celsius 36
Reallocated Event Count 0
Current Pending Sector 0
Offline Uncorrectable 0
UDMA CRC Error Count 0
Multi Zone Error Rate 0
ATA Error Count 12
Extended Attribute
Hot-add events 0
Hot-remove events 0
Lp stat events 1
Power glitches 0
Hard disk resets 0
Retries 0
Repaired sectors 0
5 Replies
- Ok so reading around it looks like I need to use the WDUtil to increase the park/idle timeout from 8 seconds to 300 seconds, this should dramatically reduce the number of parks the drive does thus saving the drive mechanism from premature wear. I can then use the Duo's spin down timer + the drive built in spin down timers to save power.
I've installed the 2nd drive and it's showing 0 ATA errors, I'm guessing the 1st drive just had a fart when it was first powered on the ATA error count for that drive is still 12 and doesn't look to be increasing.
Now I'm just re-discovering how pants wifi networks are for copying Gigs of data :roll: :lol: my router only has a 10/100mbit switch built in but I'm sure I have a desktop switch somewhere that is Gigabit. - What version of RAIDiator came on your ReadyNAS?
mdgm wrote: What version of RAIDiator came on your ReadyNAS?
It was 4.1.6, but it immediately wanted to do a firmware update so I updated it to 4.1.7.- The ATA errors would be due to an issue that was addressed by 4.1.7.
On a separate issue. If you haven't already done so since updating to 4.1.7 I would suggest doing a backup and a factory reset to get 4k sector alignment. - Ahh I see so probably when it initialised for the first time on 4.1.6 it produced the errors and of course updating to 4.1.7 has prevented any further errors.
I did read somewhere that to get the 4k alignment you had to do a factory rest which I did, is there anyway to tell if was successful?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
