Running RAID Reconstructor
Reconstructing a RAID is not a trivial task. There are many things that can cause the software to not produce the correct settings to ensure a properly constructed array. There are a few steps you will need to follow.
HINT: If you want to recover a broken NAS RAID, you might be interested in our new, much easier to use NAS Data Recovery software.
HINT: If you want to recover a broken Windows RAID, you might be interested in our new, much easier to use RAID Recovery for Windows software.
1. You will need to attach all the drives to a non-RAID controller so that the operating system can see all the drives as single drives inside of Windows.
2. You will need to start the software and choose your type of array at the top of the screen with the number of drives included in the array. If you have a RAID with more than 11 drives, you will need to use our RaidProbe service. You can find more information about this service at http://www.runtime.org/raidprobe.htm. If you have a 2 drive RAID-0, be sure to watch our tutorial about this type of recovery at http://www.youtube.com/watch?v=DWNq5rAhZ9Y.
3. You will then need to enter all these drives into RAID Reconstructor by right clicking on the white space next to the drive number and selecting the drives that belong in the array. If your RAID is a RAID-5 with one drive missing, leave one field empty. Once this is done, open the drives by clicking the open button at the bottom of the drive list on the right hand side.
4. You will now need to analyze the drives in the step 2 box at the top right hand side of the software. When this finishes, you must look at the bottom of the analysis screen to see if you received a RECOMENDED ENTRY. If you received a RECOMMENDED ENTRY, then click finish and go to step 5 of this article. If it says RESULT NOT SIGNIFICANT, then the software did not properly put the array together because it does not have all the information needed. If you are unable to produce a RECOMMENDED ENTRY, do not make an image of this RAID because it will just produce non-working files. You should then consider letting us do a RaidProbe which will allow us to put the array together by hand. Once it is completed, we will send you all the parameters and detailed instructions on how to rebuild the array. You can find more information about the RaidProbe at http://www.runtime.org/raidprobe.htm.
5. Once you have your settings, in step 3 of the software, you have the choice to make a virtual image, an image or write the data back to a drive directly. You would usually choose the virtual image. (If you are using a file system other than FAT, NTFS or XFS, contact us at this point for additional options.) If you choose to write the data directly to a drive, this will only work if the reason for the RAID failure was a controller failure. Otherwise there is something wrong with the file system or partition table that has caused the array failure in the first place and you will need to run GetDataBack to recover the data at that point.
6. Once you created the virtual image or the image, there are two options to recover your data.
Option 1: Mount the image with Captain Nemo You should use Captain Nemo if there is little or no file system damage. The advantage of Captain Nemo over GetDataBack is that Captain Nemo gives you immediate access to your files while GetDataBack will need to scan your image first. Download Captain Nemo (http://www.runtime.org/nemopro.zip) and mount the image you just created. You can now copy the files to another location.
Option 2: Scan the image with GetDataBack If there is significant file system damage or Captain Nemo does not bring the results you expect, you will need to download GetDataBack for NTFS (http://www.runtime.org/gdbnt.zip) to process the image you just created. We have also created a tutorial on how to do this at http://www.youtube.com/watch?v=XQBprGyy_Ko. If you run into problems with any of these steps, let us know right away so we can help you.