There's a lot of FUD floating around regarding the WD GPs, as have been covered in many threads here on SPCR. As far as I know there's no apparent connection between a high load/unload count and drive failures. If someone has data regarding this I would be very happy if that person could share that with us all.
Linux does not wake up every drive every 10 to 30 seconds. That might happen to the drive the OS resides on, but certainly not all drives connected to the system. This problem is also not limited to Linux. I have little personal experience with this issue since I've never used a WD GP as an OS disk (well once, but then in a situation when the disk was constantly accessed so it never got time to park its heads).
The "green" part regards to the low power consumption, which is not nit. The high failure rates of the larger capacity drives (1.5TB and above) has little to do with the head park feature and is not limited to WD drives either. Again, if someone more informed can shed some light on this I would be grateful.
I've owned a total of seven WD10EACS, all which have worked perfectly. I've also owned a WD20EADS which broke down after a while. The failure was probably not due to the head park feature since I never used the drive in a way that it used that feature very often. Of course I realize that this is anecdotal.
Regarding the 'wdidle3' utility, WD provide a firmware update for those who want to change the behavior of the drive to wait longer before positioning the heads in their park position. That's one solution. 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.http://wdc.custhelp.com/cgi-bin/wdc.cfg ... 1232125802