I'll go one better. Here is the Western Digital support article on the subject: http://wdc.custhelp.com/cgi-bin/wdc.cfg ... 1232125802
They acknowledge the problem and provide a utility to disable the offending feature.
That link does not support the idea that high load/unload count leads to decreased reliability, just that if HDD is waken from "idle 3" (unloaded idle) state every 20 the power savings from unloading are practically lost anyway (even if you don't disable unload feature).
Equally worthless links for proving increased failure rate associated with high load/unload count.
To quote: "that the current behavior poses a significant risk to the longevity of hard drives used in a wide range of laptop models".
I say: no it does not.
Then I can quote: "no it does not."
Now that obviously proves a LOT because I quoted it. Alternatively I could quote
Penn Jillette wrote:
Well the manufacturers publish the maximum number of load/unload cycles the drive is designed to survive over it's lifetime.
Read them again and you should notice that they promis at least
N load/unload cycles. At least means minimum
number of load/unload cycles the drive should be able to take. Practice has shown that HDD manufacturers have been very conservative in these published minimum sustained cycle count specs. Greenpowers exceeding 10 times rated cycles, laptop HDDs reaching 10 million cycles, etc.
It is probably fine. I'm 95% sure. Why risk it though?
Seagate firmware is probably fine (by now). I'm 90% sure. Why risk it though?
The other solution is to use software that "does not wake up the drives unnecessarily every 10 to 30 seconds or so, thereby gaining substantial power savings and eliminating superfluous activity." That's the real solution, the firmware update is just a workaround.
It's funny how Linux users have so much difficulty admitting that their OS isn't perfect and that their OS does something totally useless every 20 seconds that negatively affects power saving, increases unload count and makes extra clicks that annoys the silencers. Obviously Ubuntu is not to be blamed.
Think of it this way: it would cost WD nothing to tweak their firmware to reduce or eliminate the head park behavior - - - The fact that they have released several generations of new drives with about the same head parking behavior despite knowing about the "issue" leads me to believe that they have not observed any significant reliability problems.
Indeed. WD has not "fixed" the firmware so it's reasonable to think there is nothing worthy of fixing. To not fix something that is a known issue with a known cause (since it's intentional behaviour) for several drive generations can only be concluded that the behaviour doesn't cause increase in warranty returns (which is something WD would like to keep as low as possible).
Seagate bricking firmware on the other hand was assessed with firmware updates, and as the cause for bricking wasn't completely clear for manufacturer, the fix didn't quite solve all bricking issues. Fixed or not fixed, they took it seriously and attempted to fix it. WD has not done any changes to the unload timer, only offering optional tool for those who like to reconfigure their drives.