After I updated to the new 2023 BIOS for my ASUS P8P67 Pro mobo, the computer rebooted in AHCI mode. I rebooted and set it back to 'RAID' but could not recover the RAID volumes. I had most everything backed up, so not a huge problem, but would sure like to recover the configuration. Strange thing is the Windows disk manager lists the RAIDs twice. N and O are two 2-disk volumes - Disk 1 and 4. They are listed again as 2 and 3 'Not initialized' and 'Unallocated' Is it possible to recover them?
I don't know whether you can get your RAIDs back, but I do know how to avoid the losing of them happening.
Usually when you update the BIOS, you either have to load optimised BIOS defaults (eg. with Gigabyte boards), or these are loaded automatically, before the first re-boot after the BIOS update (sounds as though the latter happened to you).
What you MUST do at this re-boot is enter the BIOS before Windows starts to load and re-enter the settings that you need - in this case alter the SATA port settings to RAID. You also need to enter any other BIOS settings that were not at default.
It pays to keep either a written record of your non-default BIOS settings, or take screen shots of the relevant screens before you start.
One odd thing I notice from your screen shot is that your pair of drives are not identical capacity - this is not a good idea.
You could try disconnecting the drives, then re-boot. Enter the BIOS and check that the SATA ports are set to RAID and let Windows boot. Check that both sets of entries for the drives are gone. Now shut down, and re-connect your drives exactly as they were before. Now re-boot and see if your RAID array has re-appeared.
If one of the experts appears, they may have some better advice.
I have not used either of the following utilities, but thought they could help for your rather nasty sounding situation:
Sometimes the onboard raid controllers get confused when the controller mode switches and you boot past the controller initialization. They essentially recognize the Raid Volume data/XML data on the primary drives of the array but not the secondary drives. That is why the Intel Management utility still shows the array but the secondary drives as unconfigured. Disk management just does not recognize the disk type so lists those 2 drives as you see them because the Disk record has been adjusted by the raid data. Normally there is no way to recover the raid from this or atleast that I have found with the onboard raid controller. Raid Controller cards with a good firmware/driver/management give you the option to import foreign configurations to try and resolve this. However this is not an option with the onboard controllers. Essentially you have to delete the raid volumes and redo them. One thing they may prevent this in the future should it happen again is if you change the disk type in Disk management from MBR Disk to GPT. GPT stores the partition table at the beginning and end of the drive so that should store the table essentially on both drives. Does not mean the controller will recognize this but it may.
Also using the Rapid Storage Manager is essentially the same as using the bios utility. It just has a different GUI interface. So setting the raid up in the bios utility would nnot have changed this or any other function.
So I ended up deleting the arrays and creating new ones. GPT. I had to set up RAIDs in BIOS IRST as well as Windows Disk manager. All seems to be working. I lost a couple of things, but no show stoppers. We'll see if the new BIOS 2303 has any issues. If stable, I will attempt an overclock - but that's another discussion
The Intel RST User Guide states that any RAID arrays set up after Windows has been installed should be done using the RST software in Windows. Obviously this could be done only if the SATA controllers had been set at RAID in BIOS before installing Windows.
Someone, somewhere, needs to make clear the ramifications of the three possible settings for the SATA controllers in BIOS, and the need to be careful when upgrading either BIOS or SSD firmware - you have to have the drive on port 0-3, with the SATA ports set at EIDE, or possibly AHCI, to avoid losing your RAID arrays. In both cases it is essential to re-enter the BIOS and set the ports back to RAID BEFORE allowing Windows to start loading.
There is also the problem caused by changing to either of the two higher levels when Windows has been installed with the ports set at EIDE, which leads to a non-booting system. Microsoft have a document (KB922976) which sets out a way round this, but it has to be done before the change is made. It appears that their method cannot recover the system after the event
Perhaps this is another job for you?
I am disappointed that my method of recovering your arrays did not work for you. It worked for me when I made the same mistake.
Europe, Middle East and Africa