More on the WD20EARX load cycles

  • Thread starter Thread starter Tom Del Rosso
  • Start date Start date
T

Tom Del Rosso

With the same batch file and a delay of 1 hour, the load cycle count changes
as follows:

603
607
610
614
616

It should increment by 1 each time. So it loads and unloads by itself from
1 to 3 times per hour when it is not being accessed.
 
Tom Del Rosso said:
With the same batch file and a delay of 1 hour, the load cycle count changes
as follows:

It should increment by 1 each time. So it loads and unloads by itself from
1 to 3 times per hour when it is not being accessed.

I don't see that here. I have 300 load-cycles in the last 5 months on
my AADS (plausible for one per boot). Before I appliad the fix, it was
about 100'000 for 1 year. I caught it only at 200'000 cycles.

Maybe you have some other mechanism that messes with the disk?

Arno
 
Arno said:
I don't see that here. I have 300 load-cycles in the last 5 months on
my AADS (plausible for one per boot). Before I appliad the fix, it was
about 100'000 for 1 year. I caught it only at 200'000 cycles.

Maybe you have some other mechanism that messes with the disk?

No handles are open. I don't know what else can be accessing it.

I'll measure again after changing the timeout. What value do you use?


--

Reply in group, but if emailing add one more
zero, and remove the last word.

"There is no place as good to think as a bathtub." - Leo Szilard
 
With the same batch file and a delay of 1 hour, the load cycle count changes
as follows:

603
607
610
614
616

It should increment by 1 each time. So it loads and unloads by itself from
1 to 3 times per hour when it is not being accessed.

Do you have smartd running in the background? If so, you should configure
it to bypass disks that are in standby. The default check interval is 30
minutes.
 
Do you have smartd running in the background? If so, you should configure
it to bypass disks that are in standby. The default check interval is 30
minutes.

Good idea. Still, something else is odd here, as the disks
should not be able to unload (and load) more than once per hour
with an one-hour setting. Maybe the parameters are wrong.

As a pragmatic solution, I would advise to set the maximum spin-down
delay, measure the increment and decide whwther you can just live
with it.

Arno
 
Arno said:
Good idea. Still, something else is odd here, as the disks
should not be able to unload (and load) more than once per hour
with an one-hour setting. Maybe the parameters are wrong.

No to smartd. Maybe the USB adapter is at fault. I'll have to shut down
and connect the drive internally, test more under Windows, then change the
idle setting.

As a pragmatic solution, I would advise to set the maximum spin-down
delay, measure the increment and decide whwther you can just live
with it.

Living with it will be the only option anyway. :)
 
No to smartd. Maybe the USB adapter is at fault. I'll have to shut down
and connect the drive internally, test more under Windows, then change the
idle setting.

That is a possibility. Maybe it explicitely sends standby requests
for the disk.
Living with it will be the only option anyway. :)

Indeed ;-)

Arno
 
No to smartd. Maybe the USB adapter is at fault. I'll have to shut down
and connect the drive internally, test more under Windows, then change the
idle setting.

Agreed, many external USB cases that lack fans will spin down the drive as to
not generate heat.


I have a Nexstar CX that does just that.
 
GMAN said:
Agreed, many external USB cases that lack fans will spin down the
drive as to
not generate heat.


I have a Nexstar CX that does just that.

But I don't understand why the spin-down command would produce another load
cycle if it's already unloaded.
 
But I don't understand why the spin-down command would produce another load
cycle if it's already unloaded.
Cause it wakes it up just to spin it down again. I know, its retarded!
 
Back
Top