LCC issue "automatically solved" by DSM or ... ?

[maxxfi]

Try also a "hdparm -I /dev/sdX" command on both 00KA9 and 22KA9 disks, and see if it reports any difference in capabilities.

[Lex]

After another two days of testing I finally found a setting thats 100% working for me: with the WDIDLE-script I set the idle-timer to "248" (thats 60 minutes) and with the hdparm-script the AdvancedPowerManagement to "255" (that means OFF). Now the drives are running for about two days and the LCC (LoadCycleCount) finally did not increase at all any more! Now I am happy with it.

But I also have a warning for playing around with WDIDLE and unsupported WD-disks: today I temporarily bricked a WD3200BEKT: I use this drive in my PS3 and modified the wdidle-timer with WDIDLE3 to a different value (default was 8seconds - I set the timer to 60minutes). After this, the drive didn´t work in my PS3 any more! There was just three short "chirping" click-sounds and that´s it. The PS3 didn´t boot any more! I tried some different WDIDLE-values including shorter ones (e.g. 5minutes), but the drive remained "dead". The only way to get the drive back to life was to set the default value "8" (8seconds). After this, the drive worked again as though nothing had happened!
So be carefull and make a backup of your data before experimenting with unsupported drives!

Alex

[phils]

What this tells us is that it isn't disabling the LLC on drives in the expansion units.

OK so I just upgraded my DS1511+ (with DX510) from DSM 3.2 to 4.0-2228, and can confirm they appear to be have fixed this.

S99WDidle3Dis.sh now contains this:

Code: Select all

for d in `/usr/syno/bin/synodiskport -sata` `/usr/syno/bin/synodiskport -eunit`

and this command:

Code: Select all

/usr/syno/bin/synodiskport -eunit

returns the drives in the external DX510 unit.

I also popped a new drive in the DX510 and confirmed it has disabled correctly.

[koolyce]

Hello,

Yes you can !
There is a script that is called each time the system is shut down that changes the IDLE3 parameter to "Disabled" on all the WD drives. The script is part of the DSM and can be found at: /usr/syno/etc/rc.d/S99WDidle3Dis.sh

If you edit this script and change /usr/syno/bin/syno_disk_ctl --wd-idle -d to /usr/syno/bin/syno_disk_ctl --wd-idle -s300 it will set the timer value to 300 instead of disabling it.

Don't forget to shut-down your DSM after that before turning it back on to do the tests.

I did it on mine and it didn't change anything. I hope you'll have more success. I'd be interested to know if it works for you.

Also, if you want to check the value of the IDLE3 parameter directly from the Synology, you can do it from the terminal: /usr/syno/bin/syno_disk_ctl --wd-idle -g /dev/sda (and sdb and sdc etc...)

Hope this helps,

Pascal

I have 3x WD20EARS and 1x WD20EARX and with my EARS I didn't have the LCC problem but when I added my EARX, I started getting problem with LCC for this HD.

So I tried to disabled the LCC, but even if it was disabled, the LCC was horrible.

So next, I tried the hint from Pascal by modifying the script and I set the timer to 248 (-s248) and I shutdown my NAS. Restart, all my drives are with the timer to 248.

After 3 hours, of idle, the LCC raise only of 3, which means that I'm good for 300 000 hours, as the HD are designed for 300 000 LCC. This means about 34 years ;o)

[jaguar2010]

At least in DSM 1944 (and I think it's also in 1955) the command to disable WDidle is run at every shutdown (because the disk needs to be physically powered off to use the new setting). The script is located at /usr/syno/etc/rc.d/S99WDidle3Dis.sh
If you can access your NAS from ssh/telnet, you can check if the WDidle has been disabled running this command (please login as root):

Code: Select all

for d in `/usr/syno/bin/synodiskport -sata` ; do echo "*** /dev/$d ***"; /usr/syno/bin/syno_disk_ctl --wd-idle -g /dev/$d; done

This will poll each disk slot and returns the following (in results below /dev/sda, /dev/sdb, etc. are disk slot names so they change)

For each WD disk where it's able to read the timer (and [0] means that is successfully disabled)

Code: Select all

Get /dev/sda WD idle3 timer [0] successfully

For each *empty* disk slot

Code: Select all

Cannot open device /dev/sdb
fail iRet -1

For a slot that contains a non-WD disk

Code: Select all

fail iRet 1

For DS411 with latest DSM installed, i get

Code: Select all

Cannot open device /dev/sda
fail iRet -1
*** /dev/sdb ***
Cannot open device /dev/sdb
fail iRet -1
*** /dev/sdc ***
Cannot open device /dev/sdc
fail iRet -1
*** /dev/sdd ***
Cannot open device /dev/sdd
fail iRet -1

[maxxfi]

For DS411 with latest DSM installed, i get

Code: Select all

Cannot open device /dev/sda
fail iRet -1
*** /dev/sdb ***
Cannot open device /dev/sdb
fail iRet -1
*** /dev/sdc ***
Cannot open device /dev/sdc
fail iRet -1
*** /dev/sdd ***
Cannot open device /dev/sdd
fail iRet -1

Did you log in as 'root' ? If you log in as 'admin' or other user account the command doesn't have enough privileges to access the disk device.

[jaguar2010]

For DS411 with latest DSM installed, i get

Code: Select all

Cannot open device /dev/sda
fail iRet -1
*** /dev/sdb ***
Cannot open device /dev/sdb
fail iRet -1
*** /dev/sdc ***
Cannot open device /dev/sdc
fail iRet -1
*** /dev/sdd ***
Cannot open device /dev/sdd
fail iRet -1

Did you log in as 'root' ? If you log in as 'admin' or other user account the command doesn't have enough privileges to access the disk device.

Thanks for the tip. logged in as root and everything is fine.

Code: Select all

*** /dev/sda ***
Get /dev/sda WD idle3 timer [0] successfully
*** /dev/sdb ***
fail iRet 1
*** /dev/sdc ***
Get /dev/sdc WD idle3 timer [0] successfully
*** /dev/sdd ***
Cannot open device /dev/sdd
fail iRet -1

[giovenale]

Maybe this explains what I just found...
I'm mounting disks on my 414j
2ns disk is an old WD20EACS... immediately shows an enormous increase of LCC, while the EARX was ok.
Probably because I first mounted EARX, then I shut the machine down and wdidle3 set timer to disabled. Then I mounted the EACS and I found the LCC issue.
Finally I decided to go for wdidle3 with msdod... and I found the idle3 timer already disabled!
Probably it was disabled when I shut down the station to extract the disk!!!
Anyway I set the timer back to 300 s... I guess that now it's set that way, and it will be disabled at the next shutdown.
Only one think makes me worried: after 1 hour the LCC count did not increase a bit... fixed at the same value.
Is it normal or can I suppose WD hacked someway the EACS not to show the LCC after using wdidle3? (there are rumours about this on the net...) Is it possible to hack S.M.A.R.T. data?!?
Anyway, does the parking of the heads make some noise I can hear? (just to check...)

Thanks for your help

Emilio