They did release a statement
about the load/unload issue, so they aren't denying it. They also suggested the obvious solution of fixing your OS and software settings to not poll the drive at a rate that causes it to constantly go in and out of power saving mode. They even go as far as providing a utility for their enterprise class drives to increase the timer, effectively disabling the feature.
I stand corrected on the fact that WD has now made the utility available to the public for enterprise class drives, but not sure what one is supposed to do if they have a consumer WD GP drive. For a long time before that they refused to release the utility, and usually claimed it did not exist (even though a few people on this forum have had for quite some time). I know about that because I spoke to WD tech support on multiple occasions, and exchanged at least 10 emails with them, and the whole time the denied any knowledge of the utility.
But let's review the current WD claims that the problem is with Linux. Here is their claim:
"Some utilities, operating systems, and applications, such as some implementations of Linux, for example, are not optimized for low power storage devices and can cause our drives to wake up at a higher rate than normal. This effectively negates the power-saving advantages of low-power drives, such as Western Digitalâ€™s RE2GP, and artificially increases the number of load-unload cycles"
1. The fact that WD has acquiesced and released the utility tacitly acknowledges that significantly exceeding the rated load/unload cycle rating for the drive (300,000) most likely is a problem that impacts the WD GP reliability. So all those who are questioning that on this forum are now in conflict with what WD is implying.
2. WD suggests that problem is that Linux is not optimized for power-saving because it causes the GP drives and artificially increases the number of load-unload cycles. This is backwards. Windows avoids the load/unload cycles by constantly writing to drive every few seconds, which means that the drive never (or rarely) unloads during normal use
. Linux (on the other hand) writes to drives less frequently (even when not used by an external application), which still causes the drive to unload, but the frequency is just outside the maximum WD unload setting so the drive is constantly going from load to unload and back to load again. Linux is no more inefficient in this regard than Windows, and the claim that it lacks power-saving features is bunk.
3. If Linux were fixed to â€œnot poll the drive at a rate that causes it to constantly go in and out of power saving modeâ€