Breaking a RAID 1 Mirror
December 13, 2005
I recently needed to upgrade a machine that had a mirrored pair of 150Gb Serial ATA (SATA) drives. This was a small form factor (SFF) machine, a Shuttle SB51G XPC, with the drives mirrored via the on-board SATA RAID controller that’s part of the Intel 865G chipset.
What I wanted to do was remove the mirror, leave one of the drives (with its content intact) as the boot drive, and add a 300Gb SATA drive as a (non-mirrored) second drive. In the end, this turned out to be fairly simple to do, but it took me a while to figure it all out.
If you just go into the SATA controller dialog (by pressing Ctrl-I during the boot process), it gives you the option of removing the mirrored volume. Unfortunately, this is accompanied by all sorts of warnings that you are going to lose all of the data on the volume.
Attempting to go into the BIOS settings and set the SATA controller to IDE mode instead of RAID left the operating system (Windows XP Media Center Eddition (MCE)) unbootable. Interestingly, an older XP Pro install on the same machine (via dual boot) would boot fine in this mode, but the MCE install was unable to find a boot device; I’m guessing it’s a difference between driver versions on the two installs.
Breaking the mirror by simply removing one of the drives worked fine (as one would hope it would, that being the point of mirrored drives), and MCE booted up with a warning that the mirror was degraded.
Adding the 300Gb at this point worked, and I was able to see the drive in Disk Manager and format it. Unfortunately, attempting to boot the system afterwords resulted in a “Missing Operating System Error” if the 300 was plugged in. It made no difference which of the two SATA channels each drive was plugged into.
Booting the system again with only the 150 attached, I hot-plugged the 300 (kids, don’t try this at home) and it was visible again, but this obviously wasn’t a workable solution.
The Intel RAID utility told me it could rebuild the volume using the 300, so (for lack of a better idea) I let it do so, mostly because I was curious as to whether the remaining 150 gig would be available to build a partition on (it wasn’t).
At this point, I had three copies of the system — the two original 150s (the one I removed, and the one I left in), plus the 300. I figured that since I could always plug in the other 150, I had nothing to lose by breaking the RAID using the boot-up utility, even if it did lose all of the data on the volume.
I then proceeded to break the RAID, and “surprise” — both drives appeared as seperate drives, with an intact version of the 150 gig system. Despite the warning, no bad things happened.
This left me with a final problem, in that (apparently since I’d left the 300 on the first channel) the 150Gb partition on the 300 was set as drive C, and Disk Manager will not let you change the drive letter of a boot drive. There’s a good reason for this (you can paint yourself into a corner very fast), but if it would have just let me swap drive C to the other drive, it would have been fine.
I know that Partition Magic and a couple of similar programs can fix this, but I didn’t have any of them handy, and at this point I was tired of messing with it and had spent far longer on the problem than I cared to, so I reformatted the 150, and added a second partition on the 300, which left me with the additional space I wanted, albeit on two volumes instead of one.
The only reason I’m bothering to post this is that I found very little information online regarding just what really happens when you break a RAID mirror on a system like this, and maybe I can save somebody else a few hours of grief.
Your mileage may vary, I’d strongly advise backing up first, and I won’t be responsible if you lose all of your data, but that being said, breaking a RAID 1 mirror (at least on a system configured like this one) may not be as fatal as it appears.