Repair incorrectly reported broken/failed Intel RAID0

Since I purchased a new motherboard I have started using Intel RAID0 for 2xSamsung 840 Pro 256GB and 2xHitachi 1TB 2.5″ disks. Performance is great and everything worked well, until I had to reset my BIOS a few times because of overclocking. For some reason my second RAID0 array (On the Hitachi HDD’s) would always come up failed. 


This was strange to me (I have a background in Storage) as there was no reason why the RAID would have failed. So I started investigating and I found a way to repair the situation without data loss.

After reading up on this problem (and finding a few helpfull blogs, but mostly a lot of other people having the same problem) I was able to puzzle together a way to actually repair the failed RAID0 stipe and get it back again as it was before it “failed”.

After doing some testing it turns out that when my BIOS resets itself it puts the controller back in AHCI mode. When you then go through the normal POST and it tries to run an operating system, for some reason it screws up one of the RAID0 sets. But in reality, nothing is wrong with it.

I will highlight how to fix it in a series of screenshots below. Step wise we are going to do the following:

– Reset disks to non-member
– Re-create RAID disks with exact previous settings
– Search drive for lost partition
– Recover partition information and reboot

This guide only works if the RAID that has failed is NOT your primary boot volume. Some steps in Windows will be required. If it is your boot volume, some alternative steps for the Windows portion will need to be found.

Steps in Screenshots

Rebooting after setting the controller back from AHCI to RAID results in the following situation, Enter the Configuration Utility using CTRL-I
 
The following screen appears where you can clearly see on of the disks is now a “Non-RAID Disk”, incorrectly in our situation
 
Select “Reset Disks to Non-RAID”
 
Select the other disk of the ‘failed’ RAID-group
 
When selected, Hit Y and then hit Enter
 
Now we have the disks both as “Non-RAID” Disks and we can start reconstructing the RAID configuration, this will NOT overwrite any data on disks except for the RAID configuration area (which was empty before already)
 
Select “Create RAID Volume”
 
Select the intended Disks
 
This is a bit of a tricky part, you need to select the EXACT same details as where selected before. You cannot deviate in RAID Level, Stripe Size or Capacity
 
For me, I always create RAID volumes slightly smaller then the actual capacity of the current disks. If you ever need to rebuild and use a disk from a different generation or manufacturer, sometimes they can be slightly smaller then the on you had. If you do not leave some free space you will be out of options, so as a tip, do not use it to full capacity! In my case I use 1800GB

 

After filling in the correct values, create the RAID

 

The RAID will be healthy and we can boot into Windows (Not yet from the recovered volume!)

 

Exit the Configuration Utility
 

Recovering the Windows Partition

Now that we have restored the RAID configuration we will need to recover the partition in Windows. Sadly Windows itself does not have a tool for this so we will be using a little program called “TestDisk”. Cudos for creating this easy to use tool!
 
First thing, let’s open ‘Disk Management’ to check the status of our disks. Whatever you do, CANCEL the following pop-up!
 
Do NOT Initialize the disk! Hit Cancel
 
 
Here we see our restored RAID volume, but windows believes it to be empty, no partition information found

 

Download the “TestDisk” tool

 

Unzip it to a directory and run it

 

When it’s started you will be presented with the following interface, click “Create”

 

Select the correct volume to recover your information from, in our case the 1800GiB volume (Exactly the same size as in the Intel Configuration Utility)

 

Select the type of partition that you had created on your volume. Basically the following guide lines can be used ‘Intel is common for less then 2TB’. Anything above 2TB is usally a ‘EFI GPT’ volume.

 

Have it analyze your disk for a lost partition

 

Click “Quick Search”

 

Because no data was really overwritten it will find our partition in only a few seconds! Select it and hit “Enter”

 

When this screen appears, click  “Write” to write the found partition information back to disk

 

Are we sure? Yes we are! 😀

 

Hit Ok
And exit the application and then reboot

 

 

After rebooting we are presented with both drives I had before, the label of the disks is the same as before losing it

 

And voila, all files visible, and it should all be intact! Mission successful
 
And that is it. Your drive and volume and most importantly data is back, intact, without corruption. As said above, for me this happens when the BIOS gets reset and the default AHCI is selected. But luckily this easy way to recover it exists!
 
Questions or comments are very welcome below!
Please follow and like us:

36 thoughts on “Repair incorrectly reported broken/failed Intel RAID0”

  1. Great guide. I've pieced this info before but this is nice step by step – very handy. Just fixed a 4 drive 10.3 TB RAID zero after a mobo drive controller failure and moving failed raid to another brand of board – worked great.

  2. Found this page after searching for lost raid after being in ACHI mode, I had 4tb of important data that looked lost for ever, thank you so much I now have it all back! You are a god send, thank you!!!

  3. Muchísimas gracias. He podido recuperar un RAID 0 de 4TB con informacion muy importante. Antes de hacer el write use la letra P para ver el listado y hacer la copia de seguridad de todo. Muchas muchas gracias. THANKS THANKS THANKS
    Saludos desde España.

  4. Thanks, you saved the day. I got frequent Intel RAID5 degradation. Like every 3 months. Windows 8.1 has really nice feature that it will freeze itself. Windows 7 are able to work and just make data unavailable but Windows 8.1 stucks themselves in infinite loop. I have 3x WD RED 6TB.

  5. My computer decided to lock up, and after I rebooted it, my Intel RAID 0 array was in "Failed" status for no good reason. These instructions worked perfectly! Thank you for posting this!

  6. OMG! I tried all options and failed. Yours was the last option I took. The only one that I could find with step by step instructions which works for a novice like me! Just wanna say thank you!

  7. This just saved me SO HARD. I almost lost 2 TB of photos and files. You need a donate button on this site, because I can’t even explain the panic attack I was having until I found this site.

    1. No problem, glad my tips helped you!

      I might consider a donation button in the future. 🙂

  8. Thanks a lot, you saved the day, was having mobo post problems that I fixed by moving some header one pin north on a rampage v extreme to help cold boot’s, amidst this, I pulled the bios battery as a last resort when I didn’t need to, so i lost all my raid 0 SSD data. This is brilliant. Thanks.

  9. Just want to leave a personal note of thank you for this guide. Clearly written and a life saver. I’ve been having trouble with stability on my motherboard and ran a bios update. It had wiped my settings and corrupted my RAID. All the data has now been recovered.

    1. I use Raid-0 for my steam, origin and Uplay games collections and although I do have it all backed up on the cloud it would take sometime to rebuild the library.

      I agree that no one should ever have unrecoverable data stored on Raid-0, but having this guide has saved me a lot of hassle restoring my data.

  10. Hit enter too fast?.
    Without having a backup.
    Why not use 2 seperate discs, with on each one a volume, or purchase an extra disk for RAID-1.
    (+ use a backup…)
    Speed is not an issue these days for home-used-discs. (Maybe Quindorian is the exception with his in-house serverroom, haha?.

    Ps. Forget charging your car, your IT consumes all 33kW ??
    Very Nice new house, but -also for our house-, what will the next owner do with it, haha.

    Good luck, when do you officialy receive your key?

    1. Yeah, I run RAID-0, but also have a home server which mirrors most of my data as a backup AND run crashplan on all my PC’s. And if you only have two disks and want speed AND safety, you could always get really inventive and use 50% for RAID-0 and 50% for RAID-1, best of both worlds and disks a huge now a days!

      My severs run off SSD’s now a days and my file server uses SSD caching, so performance isn’t really a problem anymore. 😉

  11. Hello, does this guide work also with two Samsung 950 Pro M.2 NVme SSDs in RAID 0?
    I was running a RAID0 array with two Samsung 950 Pro NVMe M.2 SSDs. I decided to update the BIOS for my Asus Z170 Deluxe Board from firmware 1702 to version 2202. I entered the BIOS, but after the Reboot the INTEL(R) Rapid Storage Technology under “advanced” now reports the array as failed, and the one drive is not marked as being part of an array.

    here are some screenshots.

    Any help would be great!

    https://imgur.com/a/O7Eo0

  12. You wrote that “This guide only works if the RAID that has failed is NOT your primary boot volume. Some steps in Windows will be required. If it is your boot volume, some alternative steps for the Windows portion will need to be found.”
    My RAID 0 is also my boot volume. I have no other HDD or SSD in my PC. Just this two Samsung SSDs in RAID 0. So, could you please explain also which alternative steps for the windows partition will need to be found?

    your help would be appreciated.

    1. The steps are the same. Recreate the RAID, make a bootable media I. E. usb key with test disk. After running test disk you need to boot windows recovery and fix the MBR. There’s a good thread on overclock detailing the steps.

    2. From what I can see my method should work for you but you are stuck with it being your boot drive thus you can’t follow the steps. But, if you could get your system to boot from a different media, you should still be able to do them.

      So if you have a spare old SSD or HDD lying around. Use a different computer (or the one you are currently using but disconnect the SSD’s temporarily) and install windows on it with the drivers and tools needed. Once that is done, reconnect everything, re-create the RAID in the BIOS as in the steps, boot from the new temporary install and follow the steps. That should, in theory, fix your problem!

  13. Hey – Just wanted to say a big thank you! Saved my bacon after resetting my BIOS. I had the same issue on an old computer and lost all my data – just wish I had this guide then. Really good guide, easy to follow. Thanks again.

  14. I had to replace a SuperMicro X9DAE motherboard. Of course it came with ACHI enabled, and I didn’t know enough to change it to RAID before attaching my RAID-0 disks. I thought I had lost my data until I encountered your incredibly clear, concise and helpful instructions! Thanks to you, my data is intact! (I did have a backup, but it wasn’t current – that’ll be the last time my backing up is not my HIGHEST priority!!!) Your website is now permanently loaded on my computer!

  15. I woke up this morning to find all my BIOS setting reset to default. When I reset it to RAID mode, my RAID volume had failed.

    You saved it man! Thank you thank you thank you!

  16. I’ve gone through the instructions, but one of my Intel SSD’s seemed to never properly “detach” from the RAID in the Intel menu.

    I experienced a loooong wait (maybe 15-20 sec) on doing any type of action in the Intel Boot-RAID menu at POST. My guess is that one of the disks are partially defective.

    HOWEVER: I was able to recover all the data making a .VHD image using “Free RAID 0 Recovery” like this:

    (0. My RAID 0 disks was not on the OS btw)
    1. Set both disks in the RAID 0 to non-members in the Intel boot-menu. Delete the RAID array if needed too.
    2. Start up Windows OS. You will now find the disks as single disks, of course. Do not initialize any of them if prompted.
    3. Download the software on http://www.freeraidrecovery.com. Install it.
    4. Select both RAID 0 disks, now showing as single disks in the Device Manager and inside the Free Raid Recovery program.
    5. The program will try to find the pattern by reading both disks, and eventually come up with options to how to save the data.
    6. Choose the type of image you want to save the disk in. I was using a network disk through \\server\share which was convenient.

    Now you can attach the VHD or VHDX in Disk Management in Windows, through right clicking “Disk Management” and “Attach VHD”.

    Voialla!

  17. Repairing a failed RAID0 laptop single disk…

    My situation was slightly different, so I add this comment.

    I had a RAID0 crash on an ACER Aspire R7 371T computer. On this computer the RAID bios is only accessible when it fails, it was Failed and indicating :
    1 ID LITEON IT L8T-25 … 238.4GB Non-RAID Disk
    3 ID LITEON IT L8T-25 … 238.4GB Member Disk (0)
    There is no other disk in this laptop and got all the time the message “no bootable device” :

    1) The first step of the above solution was easy, as indicated I cleared and reconstructed the RAID volume

    2) I now had to reconstruct my partitions with Testdisk… The solution I found was a live Ubuntu session, and for that to construct a bootable USB Ubuntu drive.
    On another working computer, you need a USB key, an ISO Ubuntu image and the Rufus software that will make the key. Do not use a Fedora iso image, I first try but the live session was not stable.
    A first precaution is to consider the BIOS boot mode : this has to be confirmed but my experience is : if you want to use the BIOS UEFI boot mode, in Rufus options, you need to format your key in “GTP for UEFI mode”. If you format in “MBR for UEFI”, your key will only boot in BIOS legacy mode. Don’t ask me why…

    3) The second precaution when booting Utuntun is to choose” try Ubuntu”, which initiate a session constructed in the computer RAM, not touching your HDD.
    Testdisk is included in the Ubuntu package. To find it, you need :
    – to connect to the internet by wifi or other
    – open the Xterm console (first icon, search, enter X, the Xterm icon appear)
    – to type :
    sudo add-apt-repository universe
    sudo apt-get update
    sudo apt-get install -y testdisk && sudo testdisk
    Now in Testdisk, by precaution, I first try to save 2 disks images. I am not sure if it’s possible and/or useful ? But, I didn’t succeed, destination of the image is only a dir of the active drive = the RAM = not enough space…
    So without any other choice, I jumped in the unknown ! I followed the indicated steps above : third precaution, choose the right disk ! The good one is the big one, here the 476,8 gb. I didn’t touch the members drives.
    Testdisk found 2 missing partitions and I rewrote them.

    4) Now comes the very good news ! After rebooting Ubuntu, my ACER drive was there! Still not booting but intact, I mounted another external USB drive and copy my data…

    5) At the end, I did not succeed on reconstructing the boot record, the drive was write protected for Windows ??? Anyway, the fight was over, to get a clean situation I reformat everything…

    Thank you, thank you, thank you…

  18. Hi, just wanted to say thank you for posting such a great guide. Lost a nested Intel Raid1+0 config when I pulled a gpu out of the case. Your instructions work perfectly to recover a raid 1 and raid 0 accross two drives. Thanks for sharing.

Leave a Reply

Your email address will not be published. Required fields are marked *