I did this on my ReadyNAS Ultra 4. I installed the RootSSH Access addon to get shell access and got the idle3-tools download link from http://idle3-tools.sourceforge.net/# Install packages needed to compile idle3-toolsapt-get updateapt-get install libc6-dev gcc gdb libtag1-dev uuid-dev make automake# Do all work on /c (don't want to take any more space on the flash than we have to)cd /c# Download & Extract idle3-toolswget "http://downloads.sourceforge.net/project/idle3-tools/idle3-tools-0.9.1.tgz?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fidle3-tools%2F&ts=1324565985&use_mirror=superb-sea2"mv idle3-tools-0.9.1.tgz\?r\=http\:%2F%2Fsourceforge.net%2Fprojects%2Fidle3-tools%2F\&ts\=1324565985\&use_mirror\=superb-sea2 idle3-tools-0.9.1.tgztar -xzvf idle3-tools-0.9.1.tgz # Compile idle3-toolscd idle3-tools-0.9.1make# Disable the idle timer on each drive./idle3ctl -d /dev/sda./idle3ctl -d /dev/sdb./idle3ctl -d /dev/sdc./idle3ctl -d /dev/sddThe last step is to shutdown (NOT REBOOT) the ReadyNAS, unplug it, then plug it back in and boot. The IDLE timer should now be disabled.

Edalquist,you truly made my day :-]]]I just tried this on a Duo v2 and it simply worked like a charm. I got two WD20EARX disks inside the unit, running for four months now - and stumbled across the LCC issue just two weeks ago. I realized that one of the disks had already reached 100K, so I was desperately seeking for a way to get rid of this.I had no way of finding a current desktop machine that I could hook up the drives to, so this was my last hope.Thank you, thank you, THANK YOU!!!

Damn, i did this recently on my disk, had to do all the complicated stuff with my desktop. If only i had found this thread...

Thanks for this tip. I just tried this remotely on my DuoV2 and it seems to work great. I have 2 WD30EZRX in there and they were factory set to 80 (8 seconds). After almost a month set at 80 they are both over 54,000 on LCC. I set them both to 250 (25 seconds ¿or maybe 61 minutes?) and will see how it goes over the next few days. I scheduled the power timer to shut it off for an hour to see if that will let the new setting take effect. If not I'll power cycle it when I get home.EDIT: If what I read is correct, this will hopefully also make the drives less noisy since they won't be parking the heads so much.UPDATE: This seems to of fixed my LCC issue. In 4 days my LCC count has increased by only 3 on both disks. The disks are quieter since the heads aren't parking all the time. Also remotely setting the power timer settings to power off the nas for just an hour let the new idle3 setting take effect, so this could be done completely remotely.

Hi,I would be glad if someone gives me a hand here. I did as instructed (using drives WD30EZRX), however i could not decide on the correct parameter.Some people say that they changed it to 300sSome disable using the /d optionHowever, when looking at the description and the table below, I am totally lost. Should I use -s300, -s254 or what? How do I know which version of the wdidle?Regards.Meaning of the returned raw value depending on the wdidle3 versionThe value 0 is used when the timer is disabled.The values 1 to 128 are reported in .1s by all wdidle3.exe versions.The values 129 to 255 are in .1s for version 1.00, but in 30s for versions 1.03 and 1.05The difference only affects the output, the stored timer is identical between versions. Maybe different WD drives have different beheviour.wdidle3 v1.00 v1.03 v1.050 disabled disabled disabled1 100ms 100ms 100ms100 10s 10s 10s128 12.8s 12.8s 12.8s129 12.9s 30s 30s130 13s 60s 60s254 25.4s 3780s 3780s255 25.5s 3810s 3810s

I didn't want to disable it all together because parking the heads is suppose to increase power savings. That's one of the reasons I got a NAS and green drives in the 1st place.I am guessing to set 300 seconds (5min) you'd want to use "-s 138" on each drive.138-128=1010x30=300 secondsI set mine to 250 which I think is 61 minutes, but I hear my drives working all the time and the LCC does go up a digit every couple of days, so maybe it is really 25 seconds, in which case you'd want to use "-s 3000" but it looks like you can only use up to "-s 255" (25.5 seconds).If you can afford to do it twice, I'd try "-s 138" on each drive first for a few days and see if the LCC count stops growing so fast. If not try "-s 255".

HOWTO: Disable WD IDLE3 via ReadyNAS

25 Replies

Replies have been turned off for this discussion

Peekay
Aspirant
Sep 16, 2012
mdgm wrote:
There is a DOS utility that will run on Windows: http://support.wdc.com/product/download.asp?groupid=609&sid=113

You should use that.

Cheers, I'll get onto it now, the drives are still effectively new so no dramas there.

Should I be worried about any damage I've done to my NAS by going as far as I did in trying to build the idle3 tools?
mdgm-ntgr
NETGEAR Employee Retired
Sep 16, 2012
Did you force apt-get to install the packages even though they have unmet dependencies. If not you should be fine.

However if you want to restore full software support you should backup your data and do a factory reset.

The new WD Red disks already have the appropriate WDIDLE3 setting. Unfortunately only the WD10EFRX is on the compatibility list for your NV+ (v1) at this time.

mdgm wrote:
There is a DOS utility that will run on Windows: http://support.wdc.com/product/download.asp?groupid=609&sid=113 You should use that.

Peekay

Aspirant

Sep 16, 2012

mdgm wrote:
Did you force apt-get to install the packages even though they have unmet dependencies. If not you should be fine.

However if you want to restore full software support you should backup your data and do a factory reset.

The new WD Red disks already have the appropriate WDIDLE3 setting. Unfortunately only the WD10EFRX is on the compatibility list for your NV+ (v1) at this time.

mdgm wrote:
Did you force apt-get to install the packages even though they have unmet dependencies. If not you should be fine. However if you want to restore full software support you should backup your data and do a factory reset. The new WD Red disks already have the appropriate WDIDLE3 setting. Unfortunately only the WD10EFRX is on the compatibility list for your NV+ (v1) at this time.

Sorry to sound stupid but I'm basically a Linux/command line newb.
By force are you referring to it's suggestion to APT GET -f install? If so - no I didn't do that suggestion.

mdgm-ntgr
NETGEAR Employee Retired
Sep 16, 2012
Ah, good. You should be fine then, I think.
mdgm-ntgr
NETGEAR Employee Retired
Nov 06, 2012
Just used this on a Duo v2. Thanks edalquist.
otivax
Aspirant
Nov 14, 2012
Thanks from Spain.
Works fine for me and my ReadyNAS Duo v2 (arm). My WD20EARX-00PASB0 stops to increase LCC :D
Sorry for my english.
Ney
Aspirant
Nov 22, 2012
I just wanted to say thank you for this guide. My LCC count had gotten over 20k in less than 3 months =O So set it to 254 on all disks and hope it helps :)
Do you people know wether enable HDD spindown in the power menu is adviced with WD green disks or should i disable it and let the Greens do their thing?
mgbenson
Aspirant
Jan 13, 2013
Is anyone able to confirm if this method work/should be tried on an NV+v2?

I've got 2 x WD20EARX drives installed (both '-008FB0' with LCC ~235,000), and have just added a third ('-00PASB0' which is claiming it failed during restriping) before I stumbled across this thread and the advice to not use the WD green.... :(
mdgm-ntgr
NETGEAR Employee Retired
Jan 14, 2013
It worked for me on the Duo v2 so it should also work on the NV+ v2 (charcoal chassis, runs RAIDiator 5.3.x)
mgbenson
Aspirant
Jan 14, 2013
Thanks, although I've now got a bigger problem as drive 3 failed / not being recognised after and expansion and drive 1 has now failed too....

http://www.readynas.com/forum/viewtopic.php?f=66&t=68981 :-( (Netgear Case #20343149)

Forum Discussion

HOWTO: Disable WD IDLE3 via ReadyNAS

25 Replies

Related Content

Disabling WPS

CM1150V Howto Do Port Forwarding

Disable external Access

Should I disable Mesh

RAXE500 - Disable BPDU?

NETGEAR Academy

ProSupport for Business