Jump to content
RESET Forums (homeservershow.com)

Fix For Wd**ea*s Green Drives Intellipark Found?


Recommended Posts

Mr_Smartepants

Source info: http://www.ngohq.com/news/19805-critical-design-flaw-found-in-wd-caviar-green-hdds.html

 

Western Digital posted a knowledge base article, where it claims that "The number of systems using such applications and utilities is limited", a statement which we believe is false and inaccurate. Sending an HDD to idle mode only after 8 seconds of activity is abnormal behavior, which much software doesn't like as they are constantly writing and reading data to/from the HDD.

 

According to Western Digital, the following models are affected: WD20EADS, WD20EARS, WD15EADS, WD15EARS, WD10EADS, WD10EARS, WD8000AARS, WD7500AADS, WD7500AARS, WD6400AADS, WD6400AARS, WD5000AADS, WD5000AARS, WD1000FYPS, WD7500AYPS and WD7501AYPS.

 

Western Digital has released a DOS-based utility to modify the behavior of the HDD to wait longer before invoking idle mode. However, since most of their latest HDDs still ship with the default setting of 8 seconds, we strongly recommend users with affected HDDs to use the utility immediately.

 

How to Adjust Intellipark's Timer

1. Download the WDIDLE3 ISO image and burn it to a CD/DVD.

2. Ensure that your SATA controller is set to IDE mode from the BIOS.

3. Boot from the CD/DVD, it should take you into DOS.

4. In DOS prompt, type: "wdidle3 /S300" to change the default timer from 8 seconds to 300 seconds (5 minutes).

5. In DOS prompt, type: "wdidle3 /R" to verify the results.

 

Read more: http://www.ngohq.com/news/19805-critical-design-flaw-found-in-wd-caviar-green-hdds.html#ixzz1K8IbfjiD

 

I've noticed elevated numbers in the SMART data for all 4 of my WD 1TB EARS drives. Poor latency and performance times also. I'll try this utility on one of the drives and report back.

I'm looking at the SMART "Load Cycle Count" data and I'm seeing numbers as high as 417053. I'm not sure if that's an actual count or a "virtual" number.

Does anyone else have a different fix?

Link to post
Share on other sites
  • Replies 25
  • Created
  • Last Reply

Top Posters In This Topic

  • Mr_Smartepants

    11

  • pcdoc

    4

  • Captain Reynolds

    3

  • timekills

    2

Source info: http://www.ngohq.com/news/19805-critical-design-flaw-found-in-wd-caviar-green-hdds.html

 

Western Digital posted a knowledge base article, where it claims that "The number of systems using such applications and utilities is limited", a statement which we believe is false and inaccurate. Sending an HDD to idle mode only after 8 seconds of activity is abnormal behavior, which much software doesn't like as they are constantly writing and reading data to/from the HDD.

 

According to Western Digital, the following models are affected: WD20EADS, WD20EARS, WD15EADS, WD15EARS, WD10EADS, WD10EARS, WD8000AARS, WD7500AADS, WD7500AARS, WD6400AADS, WD6400AARS, WD5000AADS, WD5000AARS, WD1000FYPS, WD7500AYPS and WD7501AYPS.

 

Western Digital has released a DOS-based utility to modify the behavior of the HDD to wait longer before invoking idle mode. However, since most of their latest HDDs still ship with the default setting of 8 seconds, we strongly recommend users with affected HDDs to use the utility immediately.

 

How to Adjust Intellipark's Timer

1. Download the WDIDLE3 ISO image and burn it to a CD/DVD.

2. Ensure that your SATA controller is set to IDE mode from the BIOS.

3. Boot from the CD/DVD, it should take you into DOS.

4. In DOS prompt, type: "wdidle3 /S300" to change the default timer from 8 seconds to 300 seconds (5 minutes).

5. In DOS prompt, type: "wdidle3 /R" to verify the results.

 

Read more: http://www.ngohq.com/news/19805-critical-design-flaw-found-in-wd-caviar-green-hdds.html#ixzz1K8IbfjiD

 

I've noticed elevated numbers in the SMART data for all 4 of my WD 1TB EARS drives. Poor latency and performance times also. I'll try this utility on one of the drives and report back.

I'm looking at the SMART "Load Cycle Count" data and I'm seeing numbers as high as 417053. I'm not sure if that's an actual count or a "virtual" number.

Does anyone else have a different fix?

 

 

Please do let us know. I have bee reading about this for awhile now and I am not convinced there is a problem, especially with all the models that are listed here. I am very curious to see what results you get. Also, Raid controllers as well as windows handle things differently than other OS's. Let us know what you find.

Link to post
Share on other sites
Mr_Smartepants

OK, here's what I did.

1) Select drive that is only 2% full (minimize loss in case of failure).

2) Shut down EX490 and external bay

3) Remove selected drive from external bay.

4) Shut down Primary PC

5) Disconnect all HDD from PC except WD10EARS server drive

6) Boot into BIOS, Deselect AHCI mode and switch all SATA ports to IDE mode per instructions

7) Save settings, reboot

8) Boot to CD made from above .ISO

9) Run WDIDLE3.EXE utility using /S300 switch

10) Utility completes, reports 300 second cycle (5 min)

11) Shut down, disconnect HDD, replace in server external bay.

12) Boot server and external bay. All drives power up, light show, all seem happy.

13) Reconnect PC drives, boot to BIOS, reconfigure BIOS for previous AHCI settings, reboot to Win7

14) Login to PC

15) Console immediately reports SMART warnings.

16) Launch console, go to StableBit Scanner. Pictures say it all.

30u7hfl.png

30a6dr7.png

Now I'm going to wait a few days to see if these warnings go away after a full scan or I'll try moving the drive from the external case to a spare slot in the EX490 to see if that makes any difference.

I'm fairly positive this SMART warning is due to the change to the settings, and not indicative of an actual pending failure. The drives are only a few months old.

Link to post
Share on other sites
timekills

The current pending sector count is interesting. I wonder if the frequent head parking bumps that number up. If they come back as readable over time (i.e. after additional checks the hard drive does) that number will drop. If that happens I'd be interested in hearing about it. That would be some damning evidence.

 

FWIW, current pending sector count reflects the sectors that had a read error, but have not been rechecked and confirmed as bad. Frequently you'll get these and upon re-read the dat is okay so the sector is left as okay. Usually that's due to movement of the head from physical movement of the drive...or perhaps trying to be parked while a RAID or OS was trying to read something...

Link to post
Share on other sites

Tim Daleo did a quick YouTube video on running the WDidle prgram. Maybe he can comment

 

I would recommend running wdidle3 on all applicable WD drives before installation.

Link to post
Share on other sites
Mr_Smartepants

I would recommend running wdidle3 on all applicable WD drives before installation.

I do plan on migrating my EX490 over to WHS2011 eventually. Once I get enough drives cleared off and copy my data over I can do a clean wipe of all the other drives and setup 2011 clean. I'll run wdidle3 on the EARS drives at that time once my testing is complete and no further errors crop up. I've got some brand new Hitachi 2TB drives standing by that I picked up for $69 from the recent Amazon sale, so I'm not that worried if this drive gets hosed.

 

I have the drive completely removed from the storage pool and StableBit Scanner is running a full surface scan now. It's been running all night and is only about 60% done.

I'll report back when I get back from work on the status and if that error goes away.

Edited by Mr_Smartepants
Link to post
Share on other sites

Are the EARs jumpered? Changing the intellipark is not going to make this disk healthy. You have another issue here as this looks like an advanced format issue.

Link to post
Share on other sites
Mr_Smartepants

Yes, all my EARS drives are jumpered. The full surface scan didn't fix it. I RDP'd into the server and through the system disk management MMC snap-in I deleted the partition, and it's doing a complete format (not quick). Once that's done, I'll rescan it.

Otherwise, I'll pull it from the server and connect it to my PC and run the WD diagnostic tools on it to see if it's an actual hard fault.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...