I have a new LGA2011 motherboard with an LSI Megaraid set.
I had RAID 0+1 (or 1+0, can't remember) on the old motherboard with 4 250G drives. It's totally shot.
If I *carefully* move the drives over to the new motherboard, maintaining the drive order, will the Megaraid controller recognize the drive set?
I have 2 2TB backup drives I could clone them to as a VHD, if that would help but then I'd need to do software RAID (which is fine just for a backup).
I'm a little hesitant to just plug the drives in. If you mess up the disks (wrong order), do you think the LSI MegaRaid would be able to tell in the setup?
Will putting the drives in wrong result in the RAID configuration getting wiped out in any way?
I have a backup, but it's not totally current, and the "backup catalog" from a previously successful Windows backup is now saying it's corrupt, so if I can't get the drives back, I lose a lot of stuff. (the backup was good, but then making a 3rd backup started saying "backup catalog is corrupt". I thought it meant for the most recent backup, but apparently the first backup was bad - and it's got my older files).
Can Ghost or Clonezilla backup the physical partition in a regular SATA mode so I at least have 4 backup disks?
If I understand you correctly, you had a RAID 10 setup on your old LGA775 motherboard on the embedded software SATA controller.
Then you bought a MegaRAID and a new motherboard.
You might be able to recover the RAID set if you can correctly pair the "1" sets of the RAID 10 array to the LSI card. When you boot the new setup, you should receive a "Foreign configuration" message. If you select "Import Foreign Configuration" the LSI card will read the metadata from the old HDDs that tell it what kind of array they were in and try to import it in to a new array (it will build the array automagically). BUT, it's very risky. If you fail to place the drives in the proper order, the array is toast. Permanently.
You may actually have better luck putting the four drives in an array on the new motherboard's SATA controller (assuming it supports RAID 10). You must still have the drives in the correct order.
You are really between a rock and a hard place.
Another thing to consider, you should be able to break the RAID 10 into a RAID 0 by simply not installing one drive of each RAID 1 set (it's a mirror). In this case, you would not select "import foreign config" but rather simply create a RAID 0 set and then attach a single drive from each RAID 1 pair and do not initialize. If it recognizes it, great, if it doesn't, not so great.
As for remembering whether it was RAID 10 or RAID 01, just look at the motherboard specs. I have never seen a motherboard natively support 0+1 (RAID 01). RAID 01 is generally implemented by creating 2 RAID 1 arrays and then striping them (RAID 0) via the OS.
In any case, putting the drives in the wrong order wil not only not work, it will most likely destroy the data that is on them (the import will be attempted and the build will fail) and then you'll be SOL with zero chance of any recovery.
There's a lesson to be learned here (actually several).
1. Always backup externally.
2. Don't use the motherboard's built-in SATA RAID controller. (for reasons that should be obvious in hindsight)
3. The vast majority of people have no business using RAID. At all.
4. And most importantly, see #1.
The RAID controller will have the configuration stored in NVRAM. Normally a RAID controller writes signatures to the disk and should be able to detect the configuration of the RAID Array. As long as you do not save the configuration to either NVRAM or to disk, you should be able to power off and try several configurations if for some reason you need to. If you get the array online, the first thing I would do is image the volume as a backup.
The RAID signatures on disk, are those industry standard? I assume they go in a separate configuration partition.
Ideally, you could pull the physical partitions off as VHD's and connect them in software RAID, but that's a really long shot. I assume these configuration parameters are pretty controller specific (not even brand).
Hard to get firm data on this stuff.
I hope to fiddle with things this weekend, will let everyone know what happened. I imagine other people go through this from time to time.
Well the signature I believe is normally written as by the controller at a lower level than the partition level. You won't see it as a separate partition. This is pretty standard on enterprise controllers (SCSI/SAS) from LSI. I have not worked with their MegaRAID controllers before, but I have a lot of experience with LSI's enterprise SAS controllers. The signatures will definitely be controller specific. Just make sure you do not write anything out until it is working. In a worst case scenario, if you can't get it to work, connect the drives via a non_RAID controller, get a lot of external storage and you can reconstruct the stripe set using a number of software utilities out there. R-Studio is probably may favorite, its affordable but not free. RAID 10 with 4 drives will be easy to rebuild. I've done 12 disk RAID 10s before and 6+ spindle RAID5s successfully.