Intel ICHxR RAID Data Recovery 101

Just posting up some useful information for those who need to repair a broken raid on Intel chipsets.

Sometimes a drive can drop out of the raid set and get reset to "non-raid disk and when this happens it can be a nightmare and you can lose data if not handled properly.

Do not go into the CTRL-I raid utility to fix, this will destroy the data as it resets back to raid disk.

You need a few applications downloaded from the net from www.runtime.org.

You will need a PC that boots and has plenty of connectors for the raid drives you need to get data from.

Connect the drives and boot into windows with raid drives connected, do not enable raid for those drives, just connect and boot into windows.

Windows will go though its discovery and stuff, let it finish but dont go into the drive system manger panel in windows.

Download and run Raid Reconstructor and tell it what raid level you had and select what drives are from the raid set. If you had raid 5 it needs all but one drive to reconstruct the set or it can use all drives, it didnt seem to make a difference in speed. Once Raid Reconstructor runs it quick wizard to figure out stripe and block size it will then prompt you to start up Captain Nemo or Getmydataback NTFS. I used GMDB NTFS.

Raid Reconstructor then feeds its discovery map into GMDB and begins the rebuild process, it will scan the entire raid set for all data and display the directory structure. You can then copy the data from the damaged raid onto a hard disk or whatever you have to hold the data you want to recover.

When a disk drops from raid, the map information is lost and this is why you cannot just reset back to a raid disk. With the information from Raid Reconstructor it is possible to reset the drive back to raid when you pay for the $299 service. I am yet to go that route but I was successful in a raid 5 recovery of all data.

Sticky.

can confirm fugger's observations!

about 2 weeks ago, one of my disks died! this was no problem for the raid 1 volume on the disks, but the raid 0 volume where my xp installation sits was to be called lost.

as i expected the electronic module on the disk as the faulting part and i had nothing to loose anymore i decided to do some research and found Runtime Software on the net.

using the electonic module from another identical drive on the defective disk and "RAID Reconstructor" from runtime, i was able to recover all data of my raid 0 volume!

great product to recommend. also take a look at their imaging software DriveImage XML which is free to download. this software, like RAID Reconstructor can also be integrated in BartPE via Plugins allowing you to create a bootable cd with all the tools you need ...

Sounds like some very useful information. :)

Would this 'RAID reconstructor' also be necessary for RAID1 arrays?

I have heard stories where people could only recover failed RAID1 arrays (the spare disk that is still in good health) when it was attached to the original controller.

Since it is a plain mirror i am quite puzzled as to how this would be necessary.

Is this the case with Intel ICHxR controllers?

Quote:

---

Originally Posted by Da_maniaC

Would this 'RAID reconstructor' also be necessary for RAID1 arrays?

Is this the case with Intel ICHxR controllers?

---

no, you should not need it for a raid 1 array. its the idea of raid 1 to be able to access data after the failure of a single drive (assuming two drives in the array).

the system will boot and access data as if there is no problem, tough bios and matrix storage manager will notify you of the failed drive. at least this was the case in my situation working with an intel ich8r.

So this concerns mainly RAID 0?

There is another way to restore your RAID array if a disk dropped out. If you have a hardware failure on one of your disks, this way won't work, otherwise it should be fine. It worked for me three times. Note that this way also won't work if your windows install is on the raid array you're trying to recover, because then your pc won't boot.

*I am not responsible for any data loss blablabla, I'm just giving you a possible sollution; from my experience it tends to work*
1) Enter the Ctrl-I configuration utility. Write your raid level, array size, stripe size and everything else that can be configured on a piece of paper, you'll need this info later.
2) Delete the Raid-array. Yup, that's right, just throw it away.
3) Reboot and create a new array just like your old one. If you do not use the full disk for your array, make the array slightly (0.5GB or so) larger than the old one, so you're sure the old one fits on the new one.
4) Reboot. Don't enter the drive system manger panel in windows. Download and install testdisk. http://www.cgsecurity.org/wiki/TestDisk
5) Start testdisk. The program ask you whether or not it should create a log file. It doesn't matter for all I know, so choose whatever you like. Select your brand new raid array. Select 'Intel partition' if you have a regular
Windows partition. Next choose 'Analyse', then 'Quick search'. If your old array doesn't show up, try 'Deeper search'. Now your partition should show. Select the old partition and press Enter, then 'Write'. Testdisk now
writes the old partition table on your new array.
6) Close the program, reboot and everything should be fine.

This is how I always do it, might be worth a try.

basically what is ICHxR?
or what's the diferences between ICH9R?

The X can stand for any number. ICH6R, 7, 8, 9, 10, etc...

book marking this since i am just venturing into matrix raid!

Hello all,

After i defaulted the bios of my P5e3 premium my raid0 array would not boot anymore.

I think the problem is that i saved (and exited) the defaulted bios, before changing the raidcontroller setting from ide to raid. So in other words. I booted my mobo with the incorrect raid controller setting (IDE). With the incorrect setting i did not try to boot my Vista 64bit, I just booted into bios again to change it from ide to raid. But after i set it to the correct setting and tried to boot into vista 64bit it did not work. It says i have to insert bootable media and press a key.

They array seems to be fine and the array is still listed in bios as a bootable device, but the system isnt able to boot from it anymore.

Can anyone confirm that booting the mobo with incorrect raid controller settings will messup the Raid0 bootdevice (partition)?
Is this a common issue? and is here a work arround?


Kazi

sounds like the MBR is broken. Run the repair utility on the Vista install disk. Also does the raid Rom see your configuration IE Raid 0,1,5 as the same as it was before?

Quote:

---

Originally Posted by Kazi

Hello all,

After i defaulted the bios of my P5e3 premium my raid0 array would not boot anymore.

I think the problem is that i saved (and exited) the defaulted bios, before changing the raidcontroller setting from ide to raid. So in other words. I booted my mobo with the incorrect raid controller setting (IDE). With the incorrect setting i did not try to boot my Vista 64bit, I just booted into bios again to change it from ide to raid. But after i set it to the correct setting and tried to boot into vista 64bit it did not work. It says i have to insert bootable media and press a key.

They array seems to be fine and the array is still listed in bios as a bootable device, but the system isnt able to boot from it anymore.

Can anyone confirm that booting the mobo with incorrect raid controller settings will messup the Raid0 bootdevice (partition)?
Is this a common issue? and is here a work arround?


Kazi

---

You just have to go back into bios and enable all your sata drives again. Happens everytime you go to defaults in bios.

Quote:

---

Originally Posted by FUGGER

Just posting up some useful information for those who need to repair a broken raid on Intel chipsets.

Sometimes a drive can drop out of the raid set and get reset to "non-raid disk and when this happens it can be a nightmare and you can lose data if not handled properly.

Do not go into the CTRL-I raid utility to fix, this will destroy the data as it resets back to raid disk.

You need a few applications downloaded from the net from www.runtime.org.

You will need a PC that boots and has plenty of connectors for the raid drives you need to get data from.

Connect the drives and boot into windows with raid drives connected, do not enable raid for those drives, just connect and boot into windows.

Windows will go though its discovery and stuff, let it finish but dont go into the drive system manger panel in windows.

Download and run Raid Reconstructor and tell it what raid level you had and select what drives are from the raid set. If you had raid 5 it needs all but one drive to reconstruct the set or it can use all drives, it didnt seem to make a difference in speed. Once Raid Reconstructor runs it quick wizard to figure out stripe and block size it will then prompt you to start up Captain Nemo or Getmydataback NTFS. I used GMDB NTFS.

Raid Reconstructor then feeds its discovery map into GMDB and begins the rebuild process, it will scan the entire raid set for all data and display the directory structure. You can then copy the data from the damaged raid onto a hard disk or whatever you have to hold the data you want to recover.

When a disk drops from raid, the map information is lost and this is why you cannot just reset back to a raid disk. With the information from Raid Reconstructor it is possible to reset the drive back to raid when you pay for the $299 service. I am yet to go that route but I was successful in a raid 5 recovery of all data.

---

Awesome stuff.

Thank you very much for this....it worked like a charm! :)

Dont know where else to ask this,

but is it possible to transfer a raid from a ICH7 (975x board) to a newer board with ICH10?

Tjelaw, yes Intel RAID has been forward upgradeable for many revs now but going from 7 to 10 I never tried. It might work but you would need newest .inf already on the drive when you boot or you will BSOD on boot.

I ahve done this, and as Fugger suggest, install newest chipset driver before migration.

Ok :up: thanks for the info, much appriciated

Good info on careful management of dropped RAIDs.

I defend the no nonsense way: a RAId 0 of fast and small drives,like a pair of velociraptors (better yet on a hardware implementation like ASUS easy RAID feature to AVOID OS hassles with ACIH-IDE modes) and and external drive with routine dayly drive image backup:
A-Not all the dropped RAID 0s can be recovered by softwares, and the solution proposed demands another working machine for the data recovery
B-failed BIOS setups or failed OSs installs can ruin a RAID, but with a backup drive image RAID recosntruction is direct and much faster than any software solution
C-A burned electronic circuit in a HD does not mean permanent data loss, like was demonstrated above, but you will still need another HDs circuit board for the repair- just save costs and add and external drive dedicated for image backup: the 300GB velociraptors can be recovered for $80 with Maxtor OneTouch external HD.
The product information couldnt be more oriented towards the RAID0 velociraptors situation: "Back up your files with a push of a button or set up the software to perform convenient automatic backups.
Simplifies drive management and backup scheduling":rofl:

When I lost my raid0 array on my ich8r I just put the disks to IDE in bios, started windows from another HD and recovered the data with raidreconstructor and getdataback. No need for another comp if you have a spare HD.

Thanks a million for this info Fugger!
It worked like a charm using RaidReconstructor and GetDataBack to recover the data from my two Raptors that I had used in RAID-0! :up:

And now I'll try to do at least weekly backups of the array! ;) :yepp:

Thanks for posting this, good info. http://seoagora.com/img/308/s08e1024rvou/champagne.gifhttp://seoagora.com/img/317/s08b1024uzjw/content.gifhttp://seoagora.com/img/459/k08q1024glza/ecstatic.gifhttp://seoagora.com/img/460/c08n1024twxu/eeek.gifhttp://seoagora.com/img/464/c08o1024tpai/puzzle.gif

Quote:

---

Originally Posted by BulldogPO

So this concerns mainly RAID 0?

---

RAID 0 is most susceptible, but RAID 1 can have an issue, too. When the first disk of the pair drops, it leaves a perfect copy but that copy may not be bootable. Windows instructs you to test both alone to be sure they boot, apparently because the 'Make Array' function often fails so that you cannot boot directly to the second drive. The MS Knowledge Base doesn't say how to fix it. You have to edit BOOT.INI to correct the entry for the second drive.

Here is the thread from when I had to deal with the problem.

Btw, I never did figure out why the first drive wouldn't boot when re-installed, but if you can boot from the second you can always rebuild it.

Some more valuable information for using Raid Reconstructor.

As mentioned in Fugger's post, you must disable RAID in the BIOS. But you also must disable AHCI. If you don't, the Intel BIOS can recognize the first disk in the RAID array as the complete RAID drive, which for a 2 disk array is 2x the size of the physical disk.

I was asked to fix a Intel ICHR stripe where one drives dropped out of set and no longer appeared as a "member disk".

I set it up with the above utilities and one of the drives was physically damaged and it could not complete the image process enough to restore data.

What I did

I hooked both drives up and enabled Intel raid and entered the Raid Utility with CTRL - I
I deleted the one remaining drive from the raid set and then remade the raid with default settings
After it rebooted, windows loaded and I was able to copy off critical stuff

I got lucky with this method.

Quote:

---

Originally Posted by Deodatus

There is another way to restore your RAID array if a disk dropped out. If you have a hardware failure on one of your disks, this way won't work, otherwise it should be fine. It worked for me three times. Note that this way also won't work if your windows install is on the raid array you're trying to recover, because then your pc won't boot.

*I am not responsible for any data loss blablabla, I'm just giving you a possible sollution; from my experience it tends to work*
1) Enter the Ctrl-I configuration utility. Write your raid level, array size, stripe size and everything else that can be configured on a piece of paper, you'll need this info later.
2) Delete the Raid-array. Yup, that's right, just throw it away.
3) Reboot and create a new array just like your old one. If you do not use the full disk for your array, make the array slightly (0.5GB or so) larger than the old one, so you're sure the old one fits on the new one.
4) Reboot. Don't enter the drive system manger panel in windows. Download and install testdisk. http://www.cgsecurity.org/wiki/TestDisk
5) Start testdisk. The program ask you whether or not it should create a log file. It doesn't matter for all I know, so choose whatever you like. Select your brand new raid array. Select 'Intel partition' if you have a regular
Windows partition. Next choose 'Analyse', then 'Quick search'. If your old array doesn't show up, try 'Deeper search'. Now your partition should show. Select the old partition and press Enter, then 'Write'. Testdisk now
writes the old partition table on your new array.
6) Close the program, reboot and everything should be fine.

This is how I always do it, might be worth a try.

---

So i just updated my bios and for some reason that made the Intel Raid think my second member drive had the serial number D.... instead of WD....

I tried this method but after rebooting the drive still isn't recognized by Windows which suggests i should load the correct filesystem driver for it.

I don't know if this error was there the first time, but when i get to the drive and it lists the current partition it writes:
"Error: size boot_sector 3518814208 > partition 4294967295"

I can access the partition just fine, but unfortunately i have no drive to put the data on, so that doesn't do much good, any thoughts on what to do from here?

Edit: Managed to save it could get myself some spare harddrives for the backup.

Thank you for posting this Fugger, it proved useful for me over the last 24 hours.

I start with drive1 and drive2 in AID0. This works fine for many years, I decide during an upgrade to add drive3 and migrate to RAID5 since the 1st 2 disks are quite old.

When I powered it on with the new drive I had not fully seated the power connector for drive1, so it saw drive2 and a non raid drive and marked the array as failed. After this no combination of drives would get the array back online and there's sod all interface to fix it. Srsly Intel, WTF!

RAID Reconstructor and GetDataBack for NTFS did the trick in the end though, had to go out and rush buy a 1TB external drive to have enough storage to do the recovery.

So thank you Fugger, and screw you Intel, My day job is developing storage controllers, ours would never get in a tangle like this. Even a redundant RAID level would be balked by this problem.

I'd like to add info on recovering a RAID 0 (and at least some other RAID types too) painlessly. To be able to accomplish the painless part, one needs to be proactive when it comes the various RAID disasters that may occur--just as one ought to be fearful about losing data that are not backed up. I hope my thoughts are closely enough related to the sticky to be useful to others. They seem to fit pretty well in the context of the things already discussed above. I don't mean to be pedantic on the proactive part. But, being prepared for a RAID disaster makes recovery much more palatable.

I've used Acronis True Image for years for disaster recovery. My RAID 0 has been pushed almost to extinction several times, but my True Image disk images always have saved me from hours of reinstallation, etc. Here, I am not concerned about data recovery since I back my data up regularly sans True Image. Still, what I am talking about can prevent the loss of data in a RAID disaster--except for unbacked up data.

My current True Image disk image came in very handy two times recently after building the setup in my sig. First, my image was made from the RAID 0 installation on a different, but still capable, computer. Anyway, the current version of True Image claims to be able to do a good job of recovery even from dissimilar computers--with RAID or not. I decided to give it a try. And, it worked. That is, having set my SATA drives to RAID, in my ASUS BIOS, I was able to recover my installation perfectly to the new rig using my (true) image. The "perfectly" part took a tad of fussing around with Device Manager, but, whoa, what a break. I didn't have to reinstall 7 and all my apps.

The second time True Image saved me recently has to do with the ASUS optimized BIOS defaults. I have RMA'd a number things related to my new system. And, several times I have had to rebuild from the mobo up--which implies the existence of a new BIOS with optimized defaults. Not thinking about the fact that these defaults do not include SATA RAID as a default on my board, I lost my RAID 0 the first time I rebuilt. True image to the rescue again. I got to the BIOS, set my RAID 0 array up freshly and, then, recovered my (true) image to the RAID setup. While it takes 30 or so minutes to recover in this fashion, my wait was a small price to pay for not having to reinstall everything or to deal with lost data.

I learned pretty quickly not to plug in my SATA array drives too soon during a rebuild. That is, now, I don't plug them in until after getting into the BIOS and choosing the SATA RAID option if using a mobo with BIOS defaults similar to mine.

Obviously, the uses of True Image RAID disk images (or those from a similar program) can be applied to many cases of RAID failure/disaster. But, the proactive part of the equation needs to be satisfied in order to recover relatively painlessly.

Quote:

---

Originally Posted by Deodatus

There is another way to restore your RAID array if a disk dropped out. If you have a hardware failure on one of your disks, this way won't work, otherwise it should be fine. It worked for me three times. Note that this way also won't work if your windows install is on the raid array you're trying to recover, because then your pc won't boot.

*I am not responsible for any data loss blablabla, I'm just giving you a possible sollution; from my experience it tends to work*
1) Enter the Ctrl-I configuration utility. Write your raid level, array size, stripe size and everything else that can be configured on a piece of paper, you'll need this info later.
2) Delete the Raid-array. Yup, that's right, just throw it away.
3) Reboot and create a new array just like your old one. If you do not use the full disk for your array, make the array slightly (0.5GB or so) larger than the old one, so you're sure the old one fits on the new one.
4) Reboot. Don't enter the drive system manger panel in windows. Download and install testdisk. http://www.cgsecurity.org/wiki/TestDisk
5) Start testdisk. The program ask you whether or not it should create a log file. It doesn't matter for all I know, so choose whatever you like. Select your brand new raid array. Select 'Intel partition' if you have a regular
Windows partition. Next choose 'Analyse', then 'Quick search'. If your old array doesn't show up, try 'Deeper search'. Now your partition should show. Select the old partition and press Enter, then 'Write'. Testdisk now
writes the old partition table on your new array.
6) Close the program, reboot and everything should be fine.

This is how I always do it, might be worth a try.

---

There is an error in these steps.
For Step 2. You do NOT delete the array. You reset each disk individually to non-raid members. This clears the raid metadata, without harming the partition table or data on the disks.

This method also requires that your disks be plugged into the ORIGINAL ports that you BUILT the array on. So say you had your array originally plugged into ports 3,4, and 5, but then later moved them to ports 0,1, and 2. You MUST disconnect your drives and plug them in so that they are in the EXACT sockets that they were plugged into during the building of the array.

If you attempt this method without doing the above, your partition will be partially readable, or appear corrupt. If this happens... ALL IS NOT LOST. Repeat steps 1-3 but plug your drives in correctly. If you don't know what ports you were plugged into... TRY EVERY COMBINATION and repeat until you can fully read your partition.

Everything else here is exactly right. I've used this method several times to recover both raid0 and raid5 arrays.

I read the Intel RAID 101 but not sure how to fix my issue.

Intel has apparently a pretty crappy RAID implementation on even good MB's.

I have a Gigabyte GA-X58A-UDR3R.

I have a RAID 1 for a boot drive on the Gigabyte RAID controller for the OS. It works fine booting W7.

I have a RAID 5 array on the Intel Controller comprised of 6 2TB discs. I have a degraded array a few months ago, that reverted to a failed array when I replaced the drive. It has set that way since then. Mainly because I discovered how bad the RAID MB controllers are and was shopping for a dedicated RAID controller. I have one now and want to try and get some of the data off the failed RAID 5, move to another computer across the network, put in the new controller and build a new array.

The array is still configured in the Intel controller. How is the best way to get the data back off it. It shows failed, and the replacement disc is listed as a non-member with no way to fix the array apparently.

This helped another lurker I was helping at TH, so I thought I would chime in and say thanks for him.