Intel RAID Volume Inaccessible and Failed – RAID1 using WD VelociRaptor

This is story about HDD – WD (Western Digital) VelociRaptor 600 GB SATA Hard Drives (WD6000HLHX) connected in RAID1 (mirror) on EVGA motherboard using Intel ICH10R wRAID5. The RAID1 and / or HDD failed, died, and then (I do not have a real explanation), revived again after reformat and RAID rebuilding.

It all begun with random reboots and Intel Matrix Storage Console reported that one of the drives is in failed state. After marking drive as normal, RAID rebuilt itself, and everything worked for a couple of days. Then, same reboots, same rebuilds, and feeling that something from hardware is dying.

After one of the reboots, computer didn’t start up. It hang on BIOS screen saying, that there are no bootable drives, and that RAID1 has failed. This time it failed showing that all RAID failed instead of just one drive.

Failed RAID Volume Detected

Intel(R) Matrix Storage Manager option ROM v8.0.0.1038 ICH10R wRAID5. Copyright(C) 2003-08 Intel Corporation. All Rights Reserved.
Failed RAID volume detected. Recover volume? (Y/N):

Answering Yes to this recover question, it started the rebuild process. But rebuild never finished, it hang in the middle with the following errors:

Volume Inaccessible

Volume Inaccessible
The data in a volume is no longer accessible because of failed hard drives. Click here to identify the failed drives.

Of course you cannot click on this balloon error, because system HDD / RAID have failed, and it is impossible to start / read Intel program from that drive.

Intel RAID Failed Port 0

After this, Volume Inaccessible error, it is impossible to continue anything because Windows does not recognize HDD / RAID volume any more. Something similar happens when you hot-unplug HDD.

Then we downloaded WD Data Lifeguard Diagnostic for Windows, to test for HDD errors. Tool can be downloaded here.

It is impossible to test HDD while it is in the RAID mode, so we removed drives from the RAID. Now Lifeguard Diagnostic showed errors for the one of the disks, on the port 0.

DLGDIAG Status Code 07, Failure Checkpoint 97

Western Digital Data LifeGuard Diagnostics - DLGDIAG for Windows
[DLGDIAG for Windows]
Quick Test on drive 1 did not complete!
Status code = 07 (Failed read test element), Failure Checkpoint = 97
(Unknown Test)
SMART self-test did not complete on drive 1!

After digging some WD PDF manuals, these codes means that HDD is unrecoverable, and need to be sent to WD for replacement. So I decided to format failed drive (privacy concerns) and send it to WD. However, to my surprise, formatting went without any problems, even more, running WD Data Lifeguard Diagnostic again showed that error is gone. But after more extensive testing showed warning that, it ‘Failed to update disk property’. Didn’t find any reference to this warning in the web, but I suspect that is caused by fact, that HDD is not formatted.

Failed to update disk property!

Western Digital Data LifeGuard Diagnostics - DLGDIAG for Windows
[DLGDIAG for Windows]
Failed to update disk property!

Now it runs for a couple days or more without any problems. Failed HDD is now on Port 3 instead of Port 0.

Here is Photo of the drives before going into one of our Antec Twelve Hundred Case. Sorry for low quality image.

Two WD VelociRaptor SATA HDD 600GB

WD VelociRaptor Enterprise Hard Drives (600 GB, SATA 6 Gb/s, 32 MB Cache, 10,000 RPM).

Some reviews: WD VelociRaptor 600 GB review 1, WD VelociRaptor 600 GB review 2.

I have posted some Photos instead of screen-shots, because at some point I was unable to take screen-shots, for example, in the BIOS.

Update Nov 24, 2010.

Issue appeared again on Nov 5, 2010. Now changed motherboard to another model – EVGA X58 CLASSIFIED3 motherboard. It is now 11 days using the same HDD’s without any problems (fingers crossed). Migrating RAID mirror was easy task.

5 thoughts on “Intel RAID Volume Inaccessible and Failed – RAID1 using WD VelociRaptor”

  1. I have the same problem with ICHR10 and raid 10 4 Wd 500gb Blue .

    Drive randomly go Failed in Intel Raid , no smart fail on Drive and they test ok

  2. John, updated this post – see Update Nov 24, 2010. Also, could you share your motherboard / config data with us?

  3. I’ve got a similar issue on an ASROCK P67 Xtreme4 using 4 Samsung SpinPoint F3 1TB.
    Looks like this is an controller related issue.

  4. Just experienced the same with my Asus P8P67 motherboard. I guess these drives won’t exactly go over in history as the most reliable drives? I remember the 1.6GB drive series…about as good as the IBM Deskstars…*sigh*

  5. Check the firmware on your velociraptor, for drives manufactured before September 2009, you can experience a dropout on a good drive. I had this problem for a while until I made sure the firmware had 02 at the end instead of 01. Ask Western Digital what they can do since they are probably under warranty.

Leave a Reply

Your email address will not be published.