WD40EFRX - LoadCycleCount issue is back?!

[-DDD-]

"This utility modifies the behavior of the drive to wait longer before positioning the heads in their park position and turning off unnecessary electronics."

[johnripper]

For you this reads very helpful and should be able to go into more details, aren't you?

[-DDD-]

My English isn't good enough to describe that, but when you google "load cycle wd", there are many posts and Discriptions of this Issue.

[johnripper]

Please stop spamming this thread. Thank you.

If anybody can provide further detailed Information about this "tool" please let me know.

[effetredici]

WD seems to have realized/accepted their blunder and posted a utility for this on their site.

http://support.wd.com/product/download. ... 01&lang=en

Someone can help use the linux version from nas?

[simonesch]

Does someone have experiences with WD40EFRX modified with the tool from WD?
http://support.wd.com/product/download. ... 01&lang=en?
Does this solve the problem?

[kys]

TS-870 Pro, 4.0.3 with six WD40EFRX-68WT0N0 drives (fw 80.00A80)

I used this tool on all six drives with no errors. Confirmed: http://support.wd.com/product/download. ... 1&lang=en? solved the LCC issue for me.

Code: Select all

09:46 E:\
$ wd5741 -d?
WD5741 Version 1
Update Drive
Copyright (C) 2013 Western Digital Corporation


-Dn   Model String           Serial Number     Firmware
-D2   WDC WD40EFRX-68WT0N0   WD-BLAHBLAH   80.00A80

09:46 E:\
$ wd5741 -d2
WD5741 Version 1
Update Drive
Copyright (C) 2013 Western Digital Corporation


WDC WD40EFRX-68WT0N0   80.00A80   Drive updated successfully

[-DDD-]

mid january '14
i bought 8 wd red 4tb for my 870.
all arrived with the idle set to 300.
i will not change it for a while and look how the llc will grow.

mid february 14
1 wd red, idle set to 300 with wdidle3 on http://www.ultimatebootcd.com/

[itsmarcos]

Does anyone know whether the utility provided by WD will work on a WD Red disk connected via an eSata cradle/dock to my laptop?

[itsmarcos]

Does anyone know whether the utility provided by WD will work on a WD Red disk connected via an eSata cradle/dock to my laptop?

Answering myself. Managed to update the firmware of my new WDEFRX with my laptop (Win7) using an eSata cradle.
Scanning the disk for bad blocks now

[Mark68]

Hello everyone,

dan2507 Wrote :

I'd also be interested what the advantages/disadvantages are for 300 sec compared
to disabled. As the Red 2 + 3TB drives has this timer disabled it sounds logical
to keep this, I hope I'm correct.


I am curious too.


dan2507 wrote :

For the RED series the max LCC count is 600.000, for the Green 300.00o
if I remember correct.


My 3 year old green had a LCC of 650.000 - 700.000 still worked fine but
I was afraid of losing data and replaced them for WD Red 3 TB.
I had the idea the Greens were getting a bit more slower that is it took a bit more time to actually
stream data to my streamer.
The Reds have a power on time of only 950 hours and an avarage LCC of 950 now.

Are these normal values?

I am using a QNAp TS 410 nas with firmware 3.6.1.


Another question does the hardware powersetting effect the LCC of the drives?
I have set them on power - on - all the time so they don't go into sleepmode
after for instance 30 minutes ( or more ).

Thanks

Mark

[ChoppedBroccoli]

major props to spindoctor and mnuesser for their posts here earlier in the thread:
http://forum.qnap.com/viewtopic.php?f=1 ... 75#p389501
and
http://forum.qnap.com/viewtopic.php?f=1 ... 75#p390108

I have no desktop machine to connect my WD Red drives to and my old SATA enclosure isn't compatible with the larger 3TB drives so that didn't work either. My only option was to be able to run the utility directly on my QNAP TS-451. Seems to have worked flawlessly.

To add a bit more context on what I did on my QNAP TS-451:

------------------------
Move the program to the NAS and make it executable:

macbook_computer$ scp idle3ctl xxx@x.x.x.x:/root
xxx@xxxx's password:
idle3ctl 100% 14KB 14.2KB/s 00:00

[~] # chmod +x idle3ctl

[~] # ./idle3ctl -V
idle3ctl v0.9.1

----------
Find your drives locations:

[~] # fdisk -l /dev/sd?

Disk /dev/sda: 3000.5 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 267350 2147483647+ ee EFI GPT

Disk /dev/sdb: 3000.5 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 267350 2147483647+ ee EFI GPT
...

------
Check the current values:

[~] # ./idle3ctl -g105 /dev/sda
[~] # ./idle3ctl -g105 /dev/sdb
(both said 300 seconds)

-------
disable both (can do just one to test first):

[~] # ./idle3ctl -d /dev/sda
[~] # ./idle3ctl -d /dev/sda

--------
reboot (I rebooted from the web UI) and check again:

[~] # ./idle3ctl -g105 /dev/sda
Idle3 timer is disabled
[~] # ./idle3ctl -g105 /dev/sdb
Idle3 timer is disabled

--------

Even though my drives came set to 300 seconds, here were my stats for each drive after 3 months:
~6000 LCC over 1451 hours ~= a load cycle every 900 seconds
These drives are supposed to be rated for 300,000 LCC, so 300,000/6000 * 1451 hours = 8 years
8 years ain't too bad, (I'd probably replace the drives in that time) but it really doesn't provide much buffer. I reasoned that I am still happily using a 1TB drive from 2009 (6 years ago) and expect to for another couple years. So in the end I decided to just disable it for now.

[Toxic17]

just use the smart drive utility like so:

http://forum.qnap.com/viewtopic.php?f=1 ... 44#p451147

[ChoppedBroccoli]

just use the smart drive utility like so:

http://forum.qnap.com/viewtopic.php?f=1 ... 44#p451147

Ah didn't know about that, though their smart drive utility would probably indicate I don't need the update since it was already set to 300 on ver A82. So unless the smart drive utility can be used to override this and set it anyway, I probably needed the idle3ctl

[schumaku]

I probably needed the idle3ctl

No luck, unless your NAS is Intel based ... as per your profile, it's a TS-212 which has an ARM CPU.