I recently had cause to recover data from a Dell PC that used a hardware RAID controller and had two 250 GB SATA drives configured as RAID 0. RAID 0 is data striping. It works at the block level so, assuming your NTFS block size is set to 128KB and you have a file that is 256KB in size it will store one block on one physical drive and the other block on the other physical drive. Total capacity is 500GB.
Unfortunately, something which most non-technical consumers will not understand is that RAID 0 does not offer any data redundancy or protection whatsoever. What it does (presumably offer) is some speed advantage since any given amount of data can be written, for the most part to two physical drives at the same time and indeed read from two drives at the same time. In theory anyway, this is a great performance advantage, doubling or at least nearly doubling the speed at which data can be stored and read back.
The thing is, it also DOUBLES your chances of disastrous data loss. If either drive dies and cannot be accessed then the other one is also useless as it only contains half of your data. Think of it this way. Every hard drive you have is a lottery ticket. It has a certain probability of being bad or of being bad at some point in the future just like a lottery ticket has a given chance of winning. If you want to double your chances of winning the lottery, the only way to do it is to buy two tickets. If you buy two identical drives, each expected to fail within say 1 million operations (this is a hypothetical number for illustration) then by having two acting as one you now have 2 in a million chance of failure. 2 in a million is the same as 1 in 500,000 so you just halved the time before you can expect to lose your stuff! Twice as fast, maybe. Twice as likely for any failure to result in total failure, definitely.
RAID 1 on the other hand required two identical drives and transparently copies every operation from one drive to the other. When the 256KB file I mentioned above is saved, it is written entirely to disc1 and the hardware RAID controller then writes the same data to the second drive. Your PC operating system gets on with it’s stuff after the first write so this second one, if you are using a hardware RAID controller is “free” in terms of a performance hit. Hopefully you can see though that the maximum read and write rate you are going to get here is the one you get with a single drive. On the up side though, you have a real-time, bang up to date copy (save the power off scenario while a write to a specific file is going on) of all data. When one of the drives fail, as it surely will, you simply use the other one on its own and your data is safe while you get another drive and get setup again then copy all your data across. using the drive examples above you should again see that you now have two drives each with a 1 in a million failure chance. For the failure to be catastrophic you would require them to both fail at the same time or very close together. So you’re approximate chances of failure are now 1 in 2 million. That’s four times the reliability of the RAID0 configuration.
Anyway, I’m really writing this post so I don’t forget the tools I used to recover data from what turned out to be a RAID0 striped configuration with a damaged Master Boot Record on the first disc in the pair.
I used File Scavenger with RAID option from Quetek corporation. What a marvellous bit of software, reasonably priced and on the first night I was trying to sort this out I made use of their webchat technical support which was awesome.
Before I realised the drives had been RAIDed (the second one showed up as empty when I plugged it in as a slave on my own machine) I ran the restore and it found a million or so files which gave me hope that all was well. Moreso, as I restored some of the images it found, they appeared to work too. Long story short, it turned out that my initial tests were only of images smaller than the block size used on the drives and so images below 128KB (they were thumbnails) were looking good. It was only after I saw larger images with stripes missing or truncated that I contacted Quetek and they told me the drives were probably RAID0.
Armed with that knowledge I was able to take a guess at the raid settings within File Scavenger and after a couple of false starts I suddenly got lots of files with proper folder names (rather than “Unknown”) a wide variety of sizes and following a test restore where files of several megabytes were ok, I was confident that all was well.
The machine that I was doing the restore on only had enough power connectors for one extra SATA drive so restoring from both drives wasn’t an option. This is where File Scavenger came in useful again. It allowed me to make an image of each of the drives (fortunately I had 600GB+ free on my system drive) and then it allowed me to select those images to work with instead of physical drives. Thus, I was able to disconnect the drives for the duration of the restore and they only went back in the original system when I was certain that I had a good backup of each and had successfully got all the data back.
It did take a while, the restore went on for about 18 hours all-told but I was then able to copy all the “Documents and Settings” to an external drive, ignoring all the apps and windows files.
The next challenge was then setting up the failed system to use the drives (they had passed deep testing, I believe the changes to the partition records had been a software or unfortunate keystroke upon dell booting). I just could not get windows xp pro to recognise the drives. I’d told the Dell RAID bios to create them as a RAID1 pair but windows setup would just blue screen every time. I had an original windows XP pro disc and the XP serial that came with the machine so thought I was good to go.
The problem turned out to be the lack of SATA drivers on the XP disc. You know that point at bootup where windows says “press F6 to load additional storage drivers”? well, that’s the bit I needed but I did not have the drivers nor a floppy drive.
The answer turned out to be simple thanks to another bit of software that is free!. First, get the drivers from the dell website. I got these and extracted then to a folder. I then installed the wonderful nlite. This software lets you start with a standard windows disc (XP,vista) produce an ISO of it, add in extra drivers you wish microsoft had included, pre-fill the windows serial and answers to lots of other setup questions and finally, to burn the lot to a new disc that you can now use to boot into setup. It was a learning curve that lasted a few hours but once all these bits came together, the process was actually very easy.
Software used:
File scavenger from Quetek corp.
NLite