Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: knewsom on April 10, 2014, 02:19:50 am
-
I have a GA-Z87X-UD4H rev 1.0 - recently updated my BIOS from F5 to F9 to try and fix the USB bug, and when I rebooted after updating the BIOS, it wouldn't start Windows (running 8.1 64). Windows tried to repair disk errors or something, and it rebooted itself again. Of course this didn't work. I went into the BIOS and checked the SATA settings - it was set to AHCI and not RAID, so I switched it back to RAID, saved and rebooted.
Upon reboot, the RAID menu said my volume had failed. Two of the RAID disks are now no longer listed as a part of the RAID volume (my RAID is not my boot volume - I boot from an SSD). It is a RAID 10, all four disks in the RAID are recognized, but only two are listed as part of the RAID. How can I add them back to the volume and try to repair it?
Thanks much,
Kris
-
Found this fix at the following:
http://forum.cgsecurity.org/phpBB3/bios-update-caused-raid10-to-fail-t3544.html
"> 1. Reset both HDs to non-member using Intel BIOS utility - the utility warns that all data will be lost - in fact only metadata is lost and can be recreated using steps below.
> 2. Create a new array with identical settings as the broken array. It is critical that the HDs are in the array the same order as before. I was reconnecting the drives several times and lost track of correct order. Because of that I had to go through the steps twice (I guessed wrong the first time).
> 3. Get TestDisk from http://www.cgsecurity.org. I used Windows version (I installed a new Vista on a separate HD for this purpose).
> 4. Run TestDisk according to steps on the web site. If your HDs are connected in correct order, TestDisk should find the lost partition(s) within a few seconds. It ran for several hours, scanning my array and never found anything because I had HDs were connected in wrong order. After I changed the order and restarted from step #1 TestDisk found the missing partition immediately.
> 5. Have the TestDisk write the fixed partition table to the drive and reboot.
> 6. Now all your data on the array should be readable but the system might not boot (it didn't for me). "
Worked like a charm.
-
Kris,
Nice you were able to recover. I'm looking at this board to replace my "other vendor" z68 rig. Seems to be one that has less problems and more positive reviews than others.
I always label my disks and jot down a quick map for reference. I keep it in my MB box. Also the RAID config utility lists member disks with a serial number string... also helpful when you find yourself in a situation like yours. I'm sure you know all this now. Lesson learned. Always disconnect your drives prior to BIOS update. Have a beer, you've earned it. :)
-
I just copy both links Kris put for future info. But when it comes to Raid setups shadowsports is the man. That is some good info Kris thanks.
-
DMDILKS,
Those are kind words.
I've been using TestDisk for years. Great utility. CGsecurity started with PhotoRec, first developed to help people recover pictures deleted from SD memory cards (primarily) cameras. TestDisk showed up shortly thereafter. Both products have matured. I'm happy to see TestDisk is still being developed.
-
Thanks, it's really a useful thread!
I just think it' crucial to backup files (http://www.backup-utility.com/features/file-backup.html) before updating BIOS, in case that something unexpected happened. Updating BIOS is indeed a tough work.