Recovering from a broken RAID 0

The first thing to know about RAID 0 is that it is not a replacement for a RAID 5. This seems to be the biggest misunderstanding about RAID 0′s. People have a drive physically die and then think, “Well next time I will build a RAID 0 and not have this happen ever again.”, then they call us asking why it failed.

RAID 0 arrays will suffer the same issues as a single drive, if the drive physically dies, the only thing you can do is send it to a hardware recovery company. You will have the same issues with creating a RAID 0 that has more then two drives, if one dies, then the entire array will go down. This would be like having an airplanes with six engines and if one of them fails, the plane crashes. If you have more than two drives, make a RAID 5.

This is where RAID Reconstructor comes in. If your array is broken because of controller issues or you do not have the orignal computer you created the array in, RAID Reconstructor can help you. It will allow you to take a two drive RAID 0 and de-stripe it into a single image or back to a drive. If you make the image, then you can scan that image in GetDataBack for NTFS. If you write the data back to a single drive, the file system and partition table of the array must be intact, otherwise you will end up with an empty drive that you will need to also run GetDataBack for NTFS on to recover the data.

If you run RAID Reconstructor with the default settings on a RAID 0, you will not get the recommended entry as most RAID 0 arrays do not start at sector zero. Watch our video tutorial to see exactly what must be done to get a recommended entry.

Watch the tutorial

Leave a Reply

You must be logged in to post a comment.