My Raid0 has just unraided itself :s

[PinkFloyd]

Had windows installed on the setup in my sig.

Swapped to a new cpu, and fired up into windows. Computer then bsod, and after restarting in the Intel Matrix Storage Manager my raid array status is showing as failed

Chances that one of my drives has just died? They're detecting fine in bios.
The physical disks in this menu are showing as one being a member disc (0), and the other as a non-raid disk. If I was to create a new raid array of them is that going to completely kill my windows install?

I'm really starting to think I'm just so damn unlucky with pcs, everytime I go near one it seems to develop some sort of weird problem absolutely nothing to do with anything I have touched

 

[rpstewart]

Did you disconnect the HDDs when swapping the CPU? It might be that you've plugged one back into the wrong port.

Depending on the RAID BIOS it's sometimes possible to create a RAID0 array without wiping the drives which might recreate the array successfully but it's a might at best.

The final option is to create the RAID from scratch and recover from your backups.

 

[PinkFloyd]

From that I'm assuming it is unlikely that the harddrive is broken then?

Didn't unplug either drives, although my have knocked one of the cables when removing my graphics card to reset bios. (re-enabled raid etc and system booted up into windows first time after the reset)

Not done a backup since installing (just over a week)
All my progress in COD4 gone. Nothing important though, all that is on my storage drives and usb sticks. Damn inconvenience though.

 

[schumi84]

I had the very same issue with my RAID0 when i was trying out my mates new CPU in my system. When i put mine back in it had unraided my hard drives forcing me to break the RAID and recreate it, was a right pain as i hadnt backed up for quite a while.

 

[PinkFloyd]

Just reset the raid array, won't boot straight up, going to see if I can repair the instalation. if not I'll just stick with non raid...

 

[eggnoodle]

I recently had this problem upon updating my bios on my gigabyte x38t-dq6, with my RAID 0 array going to one member, one non-member. I had updated the bios to previous versions before with no problem whatsoever.

I could not fix the issue - tried rerolling bios, changing sata cables, clearing cmos blah de blah. It was not possible to recreate and find the pre-existing raid with the intel matrix on the x38 chipset, so I emailed the techs at gigabyte and they confirmed that it was not possible to fix the issue and my only option was to start the RAID from scratch again. If I can find the mail I will paste what they said, something about confusion between the intel RAID controller and the chipset when certain issues occur upon updating/changing certain hardware ID's iirc.