SweetAndLow
Sweet'NASty
- Joined
- Nov 6, 2013
- Messages
- 6,421
i'm getting about 800 park counts per day(avg. over 8 days). My drives where purchased between nov. 23 2013 and dec. 24 2013. I should probably make a linux live cd
Fri Feb 21 08:07:43 PST 2014 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35676 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35402 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35619 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35744 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35563 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35713 Thu Feb 27 20:32:04 PST 2014 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35689 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35417 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35633 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35757 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35576 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35726
For those with some WD Reds, apparently not. I think it goes like this..
- WD Reds introduced to market in 2012. Everything is fine. (I'll call these drives group 1)
- WD Red drives manufactured around Sept-Dec 2013 changed to having an 8 second idle park(normally I'd call it intellipark, but I don't think that term is appropriate for WD Reds). wdidle3 works on these drives. (I'll call these drives group 2)
- At some point people complained, WD backtracked and changed it to 300 seconds(or disabled... not sure which). Likely Dec-2013/Jan-2014. (I'll call these drives group 3)
i purchased my first wd red around weeks ago. i've only been using it for less than 10 hours though. according to crystaldiskinfo i have a load unload cycle count raw values of 173.
i also noticed that compare to my external 3.5" green drive, the red drive when idle is very very quiet... BUT whenever i access it, it begins clicking so loud. i have a bad loud pc case fans and the clackety sound from the wd red when being accessed is even drowning the case fans sound.
is the loud clackety sound comes from the load / unload cyclec count...?
what made me concern is that, i dont even have to use the drive for heavy activity like gaming to hear the clackety loud sound. something as simple as renaming a file or creating a new folder then i'll have that clack clack clack sound.
crystaldiskinfo reported it good. what other tests i should do in order to be able to determine whether i should RMA or not...?
ps: i live in third world country so RMA is handled by local distributors and after sales service are very bad at best. if i want to rma i have to be able to give them "proof" that the drive is faulty first :(
The loud clackety is probably a bad drive? I would run smart tests and if it fails get it replaced.. With an 8 second timer you could also be hearing the drive spin down/up and buffer causing performance degradation..
Greg,I ran wdidle3.exe on recommendation from part of the thread, and it reported the load time of one of the new drives as 300 seconds, and the other as 8.0 seconds. I set it to "disabled" - but that doesn't seem to have had any effect. LCC is still counting up. I'll try setting it to 300 and see what happens.
Greg,
If it was actually set to disable and wdidle3.exe reports it is disabled then there are two possibilities that I can see for your LCC counting up... 1) You have FreeNAS parking the drives periodically. 2) You have a new type of drive which wdidle3.exe does not work on.
I think it's very important to evaluate this because if it's the latter well everyone is in for a surprise.
Yes, thank you for that information. I guess I have to check the Load Cycle Count on my drives now, too. And eventually use the wd5741x64 utility from a Live CD. Because I only used wdidle3.exe, thought "DISABLED - That's it." and didn't bother to actually verify the settings by checking the LCC values.When I ran wdidle3.exe against the drives, it reported 8.0s, 300s, and disabled for the various drives, and after setting the value to "disabled" for the 8.0s and 300.0s units, the reported back "disabled" after a cold boot when querying with wdidle3.exe. But -- the LCC continued to climb quickly.
I made a Ubuntu 12.04 LTS Desktop Live USB stick and downloaded the "WD Red Load/Unload" utility (wd5741x64) and after running that utility, it successfully reported that the first two drives were adjusted, and the older 4 drives didn't require adjustment. Since then, the LCC issue seems to be fixed.
So, conclusion, wdidle3.exe did set the load/unload duration to 'disabled' but it didn't actually fix the LCC issue, but the WD red load/unload utility DID fix it.
All six drives have the same firmware version - 80.00A80