Help - Reset BIOS, lost RAID

Associate
Joined
20 Dec 2006
Posts
211
Location
the virtual world
I just did something stupid...

My boot drive is actually 2 SSDs in RAID 0.

I reset my BIOS to remove any overclocked settings forgetting this would also unset the RAID settings.

Tried to boot, it obviously fails to load the OS (Windows XP)
I have now set the SATA drives back to RAID in the BIOS but it still won't boot.

At the moment I can't even enter the RAID setup either (ctrl-G at post I think).

Any ideas? Can I get it back? The drives themselves should be untouched.

(Setup is Gigabyte GA-MA790XT-UD4P with AMD Phenom II X3 Tri Core 720)

Ta!
 
make sure your disks are set to RAID in the disk section of your BIOS

once this is done it should enable you to go into the RAID BIOS, another BIOS alltogether, once in there you should be able to rebuild or reconfigure the RAID.

If you worried about loss of your DATA you should have not chosen RAID 0 .....
 
I'm aware of the risks of RAID 0. My data is on another drive, but I'd still prefer to get my boot drive back as is, if possible!

The drives are now set to RAID in the BIOS as I said above.
I'm getting the message 'press ctrl-G to enter RAID setup', but it won't actually go into it.
 
is there an issue that you where trying to overcome by setting the bios to defaults?

I see no reason why it wont go into the RAID bios unless your keyboard is faulty and its not picking up your key presses, or there is an issue with the motherboard?

Possibly try a BIOS update but I doubt that will change anything?
 
The PC was freezing occasionally, no big deal, but I hadn't touched the BIOS or done any overclocking for months. I was being lazy and figured I'd just reset the BIOS to clear out anything left from the last overclock.

No idea why I can't get into the RAID setup, that is odd. Doing it before the prompt causes it to hang, doing it at the prompt does nothing and it carrys on trying to boot. The keyboard is working though.

Seems this is a common occurance. Reseting the BIOS results in one RAID member dropping out of the array - this is what's happened to me. Both disks are working fine. Some folks have managed to get the array back by rebuilding it, but it looks complicated and unless I can get into the RAID setup I don't stand a chance anyway :-(
 
There must be a reason its not letting you into the raid bios, a setting you are missing or something.

With both sata discs unplugged can you get into the raid bios?

This will soon tell us if its a drive issue or motherboard/setting issue.
 
What model are your SSD drives as some have to be set up in your BIOS as SCSI or AHCI if you have a specific controller or are you running the SSD's from your internal RAID controller in which case the standard setting is RAID and that should enforce the inbuilt controller RAID BIOS.

Check your set up from the original SSD manufacture guide, you could be missing something in the BIOS set up if the above is no help.
 
You have 2 RAID controllers on the motherboard.

One for the native AMD SATA ports and one for the Gigabyte ports.

If you're seeing the RAID setup screen which is accessed by Ctrl-G then that's for the Gigabyte ports so presumably you've enabled Gigabyte RAID in the BIOS.

If your drives are connected to the native AMD ports then that's the controller you need to set to RAID in the BIOS.

The RAID setup screen for AMD is accessed by Ctrl-F during boot up. You shouldn't need to access the RAID setup though. Hopefully if you set the correct controller in the BIOS to RAID the PC should just boot as before.
 
The keyboard works. Delete gets me into the BIOS setup.

I'm using the Gigabyte RAID controller. Ctrl-G is not getting me into the RAID setup however. I still haven't found out why.

In the BIOS, everything is now set correctly, however, as I already explained, one of the drives has dropped out of the array, even though there's nothing wrong with it. A quick google shows this often happens when the BIOS is reset, reflashed etc.

I'm going to connect the two drives to another PC and use Runtime's 'RAID reconstructor' to build an image of the drive on to a single disk and see if this will then boot the afflicted machine.
 
Back
Top Bottom