You are not logged in.
Well, necrobumping isn't ok, but a follow up on statistics in this case, might be. The concern is WD disks over time and life span.
Unfortunately my other big disk, a green Samsung, doesn't show post 193 Load cycle count. So no comparison can be made there. But I think my next disks will be Samsung, but as you said, with some research first.
I think you are reading to much into it I have the 2tb caviare green after 1 year says 167 restarts, Load_Cycle_Count 657, I have not played with anything, it runs 18hrs a day in my AMD Nvidia desktop it is also whisper quiet my Seagate 1tb and 500gb barracuda, same age have sector errors and are about to be replaced in the next month or so.
I'm dyslexic Please do not complain about puntuation or spelling and remember most dyslexic people have above average iq.
Offline
https://bbs.archlinux.org/viewtopic.php … 5#p1048835
Fortunately my LCC has calmed down since then. Currently 196547 (+506).
Last edited by Earnestly (2012-04-14 01:40:59)
Offline
Anyone tried the idle3-tools? Aur: https://aur.archlinux.org/packages.php?ID=50806
More info here: http://forum.synology.com/enu/viewtopic … 24&t=37967
http://community.wdc.com/t5/My-Book-Liv … d-p/151544
Offline
Anyone tried the idle3-tools?
I have tried - it does work for WD10EARS-00Y5B1 and WD10EADS-00M2B0.
"I exist" is the best myth I know..
Offline
Here too! WD10EARS-003BB1
sudo idle3ctl -g103 /dev/sda
Idle3 timer set to 510.0s (0x91)
I will now note my hours up/LCC ratio and see if it's getting better. Ratio today; 101,54 (475947 load cycle counts / 4687 power on hours )
Offline
I am over the moon. I spent a day of a pain booting freeDOS to use WD's wdidle3.exe only to find that disabling 'intellipark' caused my LCC to sky-rocket. The best option at the time was to settle for 300 seconds (maximum).
However, after using idle3ctl (idle3-tools from AUR) with the -d flag, my LCC has effectively stopped.
Device: WDC_WD5000AADS
Offline
idle3-ttols: First Submitted: Mon, 18 Jul 2011 10:08:34 +0000
A pity it wasn't noticed here.
Offline