Updating bios and raid
On the format dialog box check the box next to “Create MS-DOS startup disk” Next when prompted (Fig-b) install the correct driver from the floppy disk provided with the motherboard, press the S key to specify the driver, and select the correct driver depending on which controller you are using, then press enter key to continue.Select Array mode, and choose either Striping or Mirroring, then select the first option, Auto Setup to configure the RAID Array (Fig-b), then go back to the Main Menu screen, and select the Select Boot Array option (Fig-a), to make the array you just created bootable .The Basic troubleshooting guide is intended to provide you with a guide to problems that you may experience with the system: • Not Posting (no display on power up) • Stability Problems • No BOOT (system will boot to a display but will not boot to operating system) The image at the right is an typical power supply rating and wattage, notice the wattage of the power supply on the label.Along with the wattage, the make and model of the power supply as well as the DC & AMP output are listed ------ To create an MS-DOS startup disk under Windows XP, right click on the 3.5” floppy drive icon under my computer and select format.The prior 2 times I wasn't able to find info and had to "bite the bullet" and re-established my array from scratch and installing everything again. Again tonight, after a BIOS Flash and restart on my UD3P, I saw in the RAID BIOS again the "Non-Member Disk" flag and my array in "Failure" mode Fear not. I provided this as-is but the thread where this was sourced had many with the same success.
As you see it shows one disk in the array but for some reason not the other two!
The Volume, where the microcode, fixed by changing the size.3) "File size exceeds the volume size" - is no free space, frequent updating on BIOS ASRock mainboard BIOSes.
According the feedback we got until now the usage of the tool with Desktop mainboard UEFI BIOSes is very safe.
Beyond that, you're looking at thousands of dollars for professional data recovery.
Other than that, the only thing I can recommend you do about this situation is learn from it.