BIOS-based RAID is little more than a poorer version of software RAID, from everything I've read and encountered. Plus if your mobo is fried, you usually have to replace it with a similar mobo, due to the way that BIOS will format the disks to track the volumes. This is a DEFINITE consideration for recovery of data, as you can't just slap a mirrored disk into another system and pull data off it if the system can't see the volumes. There are also issues I've encountered where something will zap the config information from the BIOS and after a reboot it can't find the volumes anymore!
Software RAID on Windows tends to have a reputation for working well enough for redundancy, but not working well performance-wise, but from my research it looks like it is usually RAID 5 in software with Windows that you really take a hit. Linux-based software RAID is regarded as mature and very usable; often on-par with hardware schemes.
Hardware-wise, I've used a few kinds of Hardware RAID (3Ware and PERC) and I've had one disaster with it and a couple save-your-arse situations. Hardware RAID usually also allows for things like physical notifications (blippy lights and labels on ports) so you don't need to figure out which drive is failed and they tend to keep the underlying mechanisms hidden from the OS, so it's less of a pain in the a__ to configure and maintain. Some cards like 3Ware actually have some nice features; the hardware cards additionally tend to offer the best performance. It's also nice if they support hot-swap of drives, depending on your server usage scenario.
I think in your situation it depends on what this server is going to be used for. Even a relatively slow RAID with light use isn't a handicap. If it's something getting hammered...database server, for example, or busy mail server...go hardware. If it's light to medium use, use Windows software RAID, especially if you're not comfortable with the hardware version.
But generally speaking...avoid the BIOS RAID like the plague for a server or critical system.
Either way, make sure you have a recovery plan (backup) that allows full metal recovery...RAID is not a backup :-)
If your array is md0 then echo "idle" > /sys/block/md0/md/sync_action
'idle' will stop an active
resync/recovery etc. There is no
guarantee that another resync/recovery
may not be automatically started
again, though some event will be
needed to trigger this.
http://www.mjmwired.net/kernel/Documentation/md.txt#477
Best Answer
I don't know what will happen if you try to remove the array, but Microsoft says:
https://technet.microsoft.com/en-ca/library/cc787944(v=ws.10).aspx
Besides, if you leave the disks in an inconsistent state, one disk will be different than the other (corrupt). Best to wait until they are synchronized before you do anything.
You are supposed to wait until the disks are consistent and then select Break Mirrored Volume to create two separate disks/volumes that are identical (because the disks are consistent!).