For comparison my ‘good’ drive has around 6000 hours on time and averages about 3-4 LCCs per hour (total 21k lifetime LCCs).
My newer and higher Load Cycle Count My Book Home drives are doing several hundred per hour.
At this rate it will have caught up to my older drive in a matter of days.
It’s clearly acting as intended but introduces a delay and click sound everytime is has to move the head on and off the ramp (about 8 seconds after the drives last use.
Obviously moving the head about is what drives do all the time whats of concern is the ramp loading and unloading itself at this rate I will hit the MTBF rate of 300k per WD’s documentation.
I simply want a way to turn this feature down. I’ve timed it and the drive ramps the heads about 8 seconds after the last use. This is a rediculously short time… something like a few minutes would seem a reasonable way to match the MTBF of this feature with the overall expected lifespan of the drive.
I really wouldn’t bebothered if this was a 250-500GB drive but it’s a 2TB monster and this ‘feature’ seems like an achillies heal to me.
Not to mention the overall environmental footprint it’s supposed to save of managing a warranty return and all the other effort/energy use associated with a premature drive failure.
Thanks for the info… I agree I think the eSata/USD/FIrewire logic is masking these extended ATA/SATA commands from the drive. If I fancy risking it I’ld have to open the My Book and pull out the drive for direct WDIDLing but I don’t want to do that until I know whether the WDIDLE3 will work with this My Book’s model hdd: WD20EADS-00R6B0
Anyway I really hope this wdidle tool can be easily modified to work with an eSata connect My Book Home.
ps. I noticed using the HD Tune SMART info refresh causes an unload… if you let your drive idle for more than 10 seconds you’ll hear the drive park the heads… click fresh and you’ll hear the drive unload/unpark the head…