Gigabyte SATA Raid

[cheyenne]

I have a problem with Raid 0 at a friends computer.
The computer didnt start at all so I clean up the memorys and PCIE slots (phisicaly) and reset the bios on the mainboard. After that the computer works good but the RAID (didnt know he had RAID in the first place) dont work - one of the HDD is in non-Raid state. The computer boots up on another HDD witch is on normal SATA (set up as Defaul in Bios) and the RAID is on Gigabyte SATA (setup as RAID in bios). When I access Gigabyte SATA Raid with Ctrl-G I got RAID 0 status Failed with one HDD in a Non-Raid state.

The motherboard is GA-X38T-DG6 Rev 1.1 and the Raid have 2 Seagate 500GB HDDs.

I have two questions for you guys:
1. Did I broke the Raid 0 with the bios reset or that was just a coincidence?
2. Can I rebuild the Raid and how? I'm thinking of recreate the RAID 0 with the same name and block capacity.

Thanks in advance!
Mihai

[cheyenne]

Nevermind the first question, I put 2 new HDD in RAID 0 and reset the bios, setup the bios again and the RAID was ok.
Do you know any good RAID Recovery programs?

[Fatman]

I think once you break RAID 0 and lose data then you need to reload the OS.

[Dark Mantis]

Hi

Don't forget that you must enable RAID in the BIOS as well as loading the drivers once you have reset the BIOS before the OS has loaded.

[cheyenne]

Thanks for replay guys!
Ok, I ll give u guys more info this time.
The computer have 4 HDD:
- one with OS which is Windows7 x64, second as a storage; both on normal SATA controller on motherboard (Sata mode in bios is Default - which is IDE I think);
- and 2 HDD on Raid 0, for speed, this guy do video editing on this and didnt backup some data; those 2 are on Gigabyte Sata controller (RAID/IDE in bios).

The problem is on Raid 0 before the OS becoze on Gigabyte Raid (accessed with Ctrl-G) I see only one HDD in Raid, the other is in Non-Raid State and the status of RAID 0  is failed.

In Windows, I was very carefull not to alter info btw with chkdsk and format the partition, the disk that is in non-raid state apears like non-alocated and the other one is in RAW which I think is normal.