Morning dupre:
No, on my motherboard setup (Microstar) you can start with an existing install (probably that way on others, just have experience with this one)...it DOES require that you load the RAID drivers while you're on a regular IDE connect
...then you move it to the RAID controller/connector and build the array. And yes, when you tell it to build the mirror it goes away awhile and buids a mirrored set of the 1st one. OR you CAN start with fresh drives. There's a good explanation of how to do it on the MSI site...and several how-to's.
As for the reversibility (back to a single drive) I have no direct experience, but doubt that it would be all that big a deal. (that assumption sometimes costs me, tho)
LOL Seems it would just be a matter of going back into the RAID array setup at boot and taking the second drive out...and making the remaining one a single drive array...set as striped (lying to the OS).
I'm about to take that plunge into RAID on my own MSI-6380 setup. (there've been several false starts...1st motherboard IDE controller went south...got that RMA'ed and back and when I put it back together the CPU went...waiting on a new one) Have another WD1000JB to put in it.
There may be truth to what folx say about it not being better...but I'll find out for myself.
Also am planning a RAID setup for another client who has a small network in an accounting business. His concern is (of course) the backup feature of RAID, rather than speed, so I don't think it'll be anything exotic...but may go $C$I.
And for sure deeper than 2 discs.
I would say that I set up a KT3 Ultra ARU that was sweet...for a friend. He opted out of raid, so I just used the RAID controller connections for his 2 IDE drives and that left the DVD/CD and CDRW on their own channels. Increased his boot time, but he likes it fine. He currently uses DI for backup...and when we got it smoothed out and purring we burnt a bootable CD for safekeeping.
His array setup is configured each as a single drive array, both masters, striped. (in name only, again lying to the OS)