[Mr.Scott]

You're screwed. Bios sees raid card and array and the raid card sees the array, but neither can boot to it because the OS controls the registry for the boot order and required driver for the raid card..............and it's stuck in an endless loop waiting for the first scannow to be started or finished.
There is no repair. Wipe your OS drives and start from scratch.

[MaadDaawg]

That's what I figured, but, how do I wipe my SSDs in the array when I can't reach the operating system and windows setup doesn't see them? Can you do this in the BIOS?

[kikicoco1334]

i think you have to boot it from a flash drive or maybe boot it from a install drive and pull the driver from a flash drive of some kind i can't remember

i HATE raid cards and raid ANYTHING!

[Mr.Scott]

Originally Posted by MaadDaawg

That's what I figured, but, how do I wipe my SSDs in the array when I can't reach the operating system and windows setup doesn't see them? Can you do this in the BIOS?

No. You have to split the drives and wipe them one at a time from another rig. Even a bootable thumbdrive won't see them through the raid card. You might be able to do it on the same rig through a bootable thumb drive if you run the drives one at a time off the mobos SATA ports, but that's only IF the bootable thumb drive can see the drives.
It would be easier to just run the SSD's through the USB on your laptop and wipe them that way.
I'd be more worried about what caused the corruption to start with.

[GFDuke]

If they're sandforce drives you should just use Secure erase. You don't need an OS to use secure erase. If i remember correct yours are the OCZ vertex 2. Correct?
Go here and get the OCZ Toolbox for your drives then follow the instructions in this thread. You have to burn the iso to a boot disk.

http://www.ocztechnology.com/files/s..._7_11_2011.pdf

[Gunslinger]

I was able to get into windows, then after about 60 seconds it would lock up for about 3 minutes, then I would get the BSOD.

Then following the restart it would not see the SSD.

[Neuromancer]

When doing the reinstall/repair are you loading the RAID card drivers?

Also if you do get around to secure erasing the SSDs (which is the only way to properly erase an SSD) you might as well go ahead and update the firmware on them too if there are some updates available.

You can do it from the R3E with one of two methods. (I use a partedmagic boot stick) you will either have to connect them to the marvel controller onboard, or run hotswap mode on the intel ports, and detach/reattach them after parted magic loads up.

Pmagic might even work on the RAID (albeit with array broken) I am not certain however what storage controllers linux supports natively.

[MaadDaawg]

Originally Posted by GFDuke

If they're sandforce drives you should just use Secure erase. You don't need an OS to use secure erase. If i remember correct yours are the OCZ vertex 2. Correct?
Go here and get the OCZ Toolbox for your drives then follow the instructions in this thread. You have to burn the iso to a boot disk.

http://www.ocztechnology.com/files/s..._7_11_2011.pdf

Cool, thanks Bro Your memory is precise, vertex 2s. Ordered a vertex 3 to be delivered tomorrow to get the gamer up and running faster

[MaadDaawg]

Originally Posted by Gunslinger

I was able to get into windows, then after about 60 seconds it would lock up for about 3 minutes, then I would get the BSOD.

Then following the restart it would not see the SSD.

yeah, same thing I had

[MaadDaawg]

Originally Posted by Mr.Scott

No. You have to split the drives and wipe them one at a time from another rig. Even a bootable thumbdrive won't see them through the raid card. You might be able to do it on the same rig through a bootable thumb drive if you run the drives one at a time off the mobos SATA ports, but that's only IF the bootable thumb drive can see the drives.
It would be easier to just run the SSD's through the USB on your laptop and wipe them that way.
I'd be more worried about what caused the corruption to start with.

i booted around 4.8ghz at 1.46 vcore, and upped the bclk until I hit 4.999 then watched the temps until ... it died. Temps were really low with the rads in the window, but the vcore was probably too low. Not sure what caused it