This is an unusual post for this site, but I feel it is very important for as many Linux users too see as possible, to try and save them from HDD replacements and data loss.
I have recently discovered (a bit too late) that Western Digital Green hard drives have a serious issue when used in Linux as a main drive or as a NAS drive. The problem can also occur in certain situations in Windows too. The problem is due to a feature called IntelliPark. Which parks the heads on the drive after 8secs of drive inactivity.
Many Linux installations write to the file system a few times a minute in the background (eg. writing logs). As a result, there may be 100 or more load cycles per hour, and the load cycle rating may be exceeded in less than a year. This problem also makes the drives very unresponsive and makes your system feel slow as the heads need to be unparked when you try and load something.
My friend has killed two 1TB Green drives on his XBMC media box in four years. The 500GB drive in my partners machine is in deep trouble as the load_cycle count is at 1991353 after a power_on_hours of 29549hrs. Compare that to my WD Black 1TB which has a load_cycle count of 721 after 13579hrs.
Now Western Digital's specsheet says that the drives are good for 300,000 Load/unload cycles, so this is a pretty big deal.
http://www.wdc.com/wdproducts/library/SpecSheet/ENG/2879-771438.pdf
How to check/evaluate your WD Green Drive.
If you have a Western Digital Green drive, please check your SMART information before it’s too late. To do this you will need to install the package called smartmontools :
Now check like this changing sda to whatever your Green drive is. (Use lsblk in terminal or gparted or i-nex or something to work out which drive it is.):
If the Load cycle count exceeds a few thousand, you’re affected by the idle3 timer problem.
Here is how the output should look when this isn’t a problem:
This is how we solve the problem.
Ok so you have the problem and want to fix it. Western digital have made a DOS utility to fix it if you ask them for it. Or can find it. Its called wdidle3.exe
But we arn’t going to use that. Instead we are going to use a Linux unofficial alternative called idle3-tools. It is already packaged in most distributions like Manjaro/Ubuntu/Mint/Fedora so no need to compile it. but here is the source:
http://idle3-tools.sourceforge.net/
Install idle3-tools with whatever package manager you use. Or like this in the terminal:
Now check what your drives timer is currently set as. (Replace sda if needed with your own drive.):
It will likely say it’s set to 80 [8sec]
Now really we want to just disable the timer altogether like it is on a black drive, and just let our systems power management handle the drive. If you want to just increase the time, then goto http://idle3-tools.sourceforge.net/ and read the instructions.
To disable the timer (Replace sda if needed with your own drive):
Next step is to shutdown and power off your computer. Rebooting isn’t enough! You need to power off, so the drive will turn on with the new settings.
Now check again:
and it should say disabled.
Optional step.
Remove idle3-tools and smartmontools with your package manager or in a terminal:
That’s it! All done. You can now enjoy the reliability and speed from the WD Green drive that you expected to have when you bought it.
You can also find this post @ https://wiki.manjaro.org/index.php?title=Western_Digital_Green_-_Drive_Fix_-_Linuxve_Fix_-_Linux
Also on Forums here https://forum.manjaro.org/index.php?topic=17890.0
And finally here aswell https://orkultus.wordpress.com/
I have recently discovered (a bit too late) that Western Digital Green hard drives have a serious issue when used in Linux as a main drive or as a NAS drive. The problem can also occur in certain situations in Windows too. The problem is due to a feature called IntelliPark. Which parks the heads on the drive after 8secs of drive inactivity.
Many Linux installations write to the file system a few times a minute in the background (eg. writing logs). As a result, there may be 100 or more load cycles per hour, and the load cycle rating may be exceeded in less than a year. This problem also makes the drives very unresponsive and makes your system feel slow as the heads need to be unparked when you try and load something.
My friend has killed two 1TB Green drives on his XBMC media box in four years. The 500GB drive in my partners machine is in deep trouble as the load_cycle count is at 1991353 after a power_on_hours of 29549hrs. Compare that to my WD Black 1TB which has a load_cycle count of 721 after 13579hrs.
Now Western Digital's specsheet says that the drives are good for 300,000 Load/unload cycles, so this is a pretty big deal.
http://www.wdc.com/wdproducts/library/SpecSheet/ENG/2879-771438.pdf
How to check/evaluate your WD Green Drive.
If you have a Western Digital Green drive, please check your SMART information before it’s too late. To do this you will need to install the package called smartmontools :
sudo pacman -S smartmontools
(Arch / Manjaro)sudo apt-get install smartmontools
(Ubuntu / Mint)Now check like this changing sda to whatever your Green drive is. (Use lsblk in terminal or gparted or i-nex or something to work out which drive it is.):
sudo smartctl -A /dev/sda | grep "^193"
193 Load_Cycle_Count 0x0032 253 253
000 Old_age Always - 1991353
If the Load cycle count exceeds a few thousand, you’re affected by the idle3 timer problem.
Here is how the output should look when this isn’t a problem:
sudo smartctl -A /dev/sdb | grep "^193"
193 Load_Cycle_Count 0x0032 200 200
000 Old_age Always - 721
This is how we solve the problem.
Ok so you have the problem and want to fix it. Western digital have made a DOS utility to fix it if you ask them for it. Or can find it. Its called wdidle3.exe
But we arn’t going to use that. Instead we are going to use a Linux unofficial alternative called idle3-tools. It is already packaged in most distributions like Manjaro/Ubuntu/Mint/Fedora so no need to compile it. but here is the source:
http://idle3-tools.sourceforge.net/
Install idle3-tools with whatever package manager you use. Or like this in the terminal:
sudo pacman -S idle3-tools
(Arch / Manjaro)sudo apt-get install idle3-tools
(Ubuntu / Mint)Now check what your drives timer is currently set as. (Replace sda if needed with your own drive.):
sudo idle3ctl -g /dev/sda
It will likely say it’s set to 80 [8sec]
Now really we want to just disable the timer altogether like it is on a black drive, and just let our systems power management handle the drive. If you want to just increase the time, then goto http://idle3-tools.sourceforge.net/ and read the instructions.
To disable the timer (Replace sda if needed with your own drive):
sudo idle3ctl -d /dev/sda
Next step is to shutdown and power off your computer. Rebooting isn’t enough! You need to power off, so the drive will turn on with the new settings.
Now check again:
sudo idle3ctl -g /dev/sda
and it should say disabled.
Optional step.
Remove idle3-tools and smartmontools with your package manager or in a terminal:
sudo pacman -R idle3-tools smartmontools
(Arch / Manjaro)sudo apt-get purge idle3-tools smartmontools
(Ubuntu / Mint)That’s it! All done. You can now enjoy the reliability and speed from the WD Green drive that you expected to have when you bought it.
You can also find this post @ https://wiki.manjaro.org/index.php?title=Western_Digital_Green_-_Drive_Fix_-_Linuxve_Fix_-_Linux
Also on Forums here https://forum.manjaro.org/index.php?topic=17890.0
And finally here aswell https://orkultus.wordpress.com/
Some you may have missed, popular articles from the last month:
Load_Cycle_Count 4677971
Is this a problem?
BTW this is WD Elements Desktop WDBAAU0020HBK
The weird thing is that on my 2 others WD Black, the idle3 timer was already disabled.
Some setups have this Drive Series as main drive. See NAS Servers.
Some people, here in Germany jumps on the Save power train, because the power was not cheap here so the people use these kind of drives.
So i find the information from the Topic starter really important.
Why? I'm hardware/software technician and openSuSE supporter.
I have a green Drive from WD, but it was a USB Drive that's works now intern as Data drive. My primary drive was a ssd.
Thx to the Topic starter.
Best regards
Peter
- Stian
I have heard that other drives can be affected (eg. blue and some laptop drives), but since I cannot personally check and test, I only mentioned green.
The best idea I guess is to check even if it's not green.
I also have no idea if this fix would work for a non WD drive. I guess it might, but I haven't at all looked into it or tried it.
I tried the idle3ctl command on a non WD hard drive and got this: "The drive /dev/sda does not seem to be a Western Digital Drive but a M4-CT064M4SSD2".
193 Load_Cycle_Count 0x0032 074 074 000 Old_age Always - 52319
the WD Blue that have SteamOS(Debian) don`t have the problem.