Stupid RAID mistake

[Masterdog]

Hi all,
I've just got meself an SSD so stuck it in the system, replacing what I thought was my old OS drive in the process (I'd labelled it 'Windows', so one would think I'd got it right). I also disconnected my two RAID 0 drives just to avoid any complications when reinstalling Windows. Did that, installed the nVidia storage drivers (which control the RAID), then plugged back in the RAID drives and booted up.
At this point the RAID flashed up saying it was degraded, but was rebuilding. Stupidly, I thought 'Ok, I've reinstalled the RAID drivers, it wants to check everything's okay'. I assumed that the RAID controller wouldn't overwrite a drive that wasn't originally part of the RAID by checking a serial number or something.
As you've probably guessed by now, I'd accidentally put in my OS drive as one of the RAID drives. At about 35% rebuilt, I got nervous and checked the drive I hadn't put in the system. It had a mirror copy of the RAID on it.
So two questions...first of all, is there any chance I've made two mistakes? I was surprised that the RAID controller doesn't remember what disks were part of it originally, but I suppose there's no guarding against stupidity. Secondly, is there any chance of me getting anything back off the OS drive? There isn't actually anything particularly important on there - all the important stuff is either backed up to DVD or cloud - but there are a few things I wouldn't mind getting back. I've had a quick check with FTK Imager, but it doesn't show anything recoverable.

Ta!

MD

PS: SSD drives are awesome.

 

[Ch3m1c4L]

If theres nothing important on it, then dont bother, itll be more hassle than its work. I use free undelete but I imagine the RAID rebuildwould have been copying the data off the RAID 1 drive and onto the "new" drive you had put in for the array. So its likely that its written over it and as such would need much more expensive software/techniques to recover anything useful.

The RAID controller does remember what disks were in it, hence it knew it was degraded (only one drive was reporting it had raid infomation on it) and this signifies to the controller that a drive has failed (which you would then replace but until a rebuild its still degraded) and as such rebuild as soon as you have added a disk in the array to replace it.

So two mistakes are putting wrong disk in, then letting rebuild it. Re doing the drivers wont make it rebuild. If its the same controller it will recognize its own raid data "stuff" it marks the drive with, rebuilding is only needed if you change drives and/or sometimes controllers (some swap over fine, some dont).