Sata RAID in ASROCK H67M-GE makes it impossible to install Windows due to no SSD bootable

wimmerd

Prominent
Jun 16, 2017
2
0
520
Hello

I have an ASROCK H67M-GE (I know, it's not the newest) and I'm at a complete loss.

I have one SSD which had my OS, and 2 drives that operate in RAID 1. Both came from my previous system.

When I put the sata controller on AHCI,I could boot from the SSD. But when I put it in RAID mode I can only boot from USB devices.

So,I tried booting from win10 install cd and deleting all partitions on the SSD, also disconnecting the other drives. Both the UEFI and the Windows install can see the drive, but the Windows warns that it might not be able to boot from the drive. This is true, as it does a reboot after copying the files, but I can't get it to go to the SSD for the rest of the installation.
I have tried 'floppy' thing, which doesn't help.

Also, I do not see the CTRL + I screen. I have no chance of entering that screen, even if I spam the combination without actually seeing the screen. The option rom just doesn't seem to load, no matter if I choose to show the brand logo or not.

Does anyone have any ideas?
 
Solution
Seems like I fixed it myself after a day of struggles.
The problem seemed to reside within the a faulty bios version. The previous owner must have installed the 2.17a version. When I flashed back to the 2.10 (I had to download a rom from a non official site as the official site only listed the 2.10, but only the win version, which didn't work) I was able to boot from the ssd with the sata in raid. The ctrl+i became visible

wimmerd

Prominent
Jun 16, 2017
2
0
520
Seems like I fixed it myself after a day of struggles.
The problem seemed to reside within the a faulty bios version. The previous owner must have installed the 2.17a version. When I flashed back to the 2.10 (I had to download a rom from a non official site as the official site only listed the 2.10, but only the win version, which didn't work) I was able to boot from the ssd with the sata in raid. The ctrl+i became visible
 
Solution