Raid Menu CTRL-R not showing up

close enough I hope to post this here: Bios 2.70 on Taichi, does not show the Ctrl-R either.
The RAID setup guide states on page 5: Use legacy RAID-ROM to create and configure array disks. True enough the options in the UEFI Bios are insufficient. Hot spares cannot be managed, array creation is impossible,etc. I am for example stuck with a Raidable array where I cannot add another disk to transition to RAID1. No, Windows installation comes after that ... all friendly Sata, not even NVME. The AMD RaidExpert Manual is not helpful either, as it lists options that do not show up in the ASRock Bios.

So ... has anyone been able to rais a ctrl-R Raid setup on a Taichi or Aqua yet? What is the trick? Yes it is only in Legacy mode, the network boot rom does show up when configured appropriately, however the Raid setup does not. What's up with that? RAID appears more useful than LEDs, no?

1. Agreed, a full UEFI version would be desirable moving forward.
2. At this time the UEFI version appears incomplete, bare bones, only permitting configuration of two empty disks as RAID 1 or switch a disk to global hot spare. Please kindly refer to the AMD RaidExpert2 guide under Chapter 5, Option Rom, for comparison.
3. The Legacy opRom offers more (but as the title of this thread does not show up on my system, so no ctrl-R possible):
a) Ctrl-R not possible, option not showing (Bios deficient).
b) Dedicated hot swap for specific array missing. Just setting disk as global hot swap is insufficient. Manage hot spares item from AMD RaidExpert2 is not showing. It might merge the dedicated hot spare even into the "Raidable array" but I can't test that due to a).
c) Adding disks in whatever form, new/uninitialized or initialized/empty to a "Raidable" array is not possible under the UEFI implementation.

I would take the legacy option rom with better functionality until the UEFI implementation is fixed to full functionality. The Legacy option not showing turns out to be a showstopper in my case. The cleared path is just a tad too narrow. Thank you for understanding.


Also: The Board utility under Windows does also not retain the fan curves for whatever reason through a power cycle. No, it is not the battery :). What is up with that? I do not even care about specifically the SB fan and noise, but cooling functionality as the default, MB derived temperatures, are way too high. The voltage for the CPU with almost 1.5V appears excessive in the default.

Question then:
1. Are you on an X570 Taichi?
2. If yes, what Bios version are you on? 2.70 in this case.
3. What processor are you running? 3900X in this case.
If you can access all the options you describe, in my case that access is not possible. Looking forward to your response as there must be some significant differences that your post unfortunately does not list. Again I am running stock, no overclocking.
Will the Windows install then simply work with the Raid drivers, even when I empty the disks? No. Array can be set up, even with difficulties deleting automatically created arrays. Following there are more roadblocks with Sata instead of NVMe disks apparently as I cannot configure them as boot device. Windows install on array cannot continue, even wiht RAID drivers available due to lack of support in Bios.

ASRock support was so far not helpful, they just sent me to the dealer ...

Watched your video. I get the same options, quite familiar with them by now, and they do not work. If your read what I posted, the features I mention and are implemented in RaidExpert2 are not available.
- Global Hot Spare != Dedicated Hot Spare.
- Raidable Single disk array cannot have a second disk assigned to upgrade to RAID 1.

What you show ONLY works for 2 empty disks and global hot spare. The Bios Oprom is hobbled compared to the bios oprom as described in the AMD document, chapter 5.

FYI, I just tossed a week of setup to get to two empty disks and form an array. There are STILL issues as arrays will not consistently delete on the X570 Taichi with the 2.70 Bios. Also, once the array is formed and shows as working, the windows install on the Sata drives fails, with the drivers on the setup disk, as well as on the nvme_sata_raid_windows_driver_9_3_0_38 from the AMD site. Why? Win 10 setup points to Bios, with unallocated space "not sure Windows can be installed on the machine" and with a formatted partition a specific error listing that the RAID array does not show up in Bios. Not thrilled. This is not my first setup but it starts to feel like Socket 462 days when AMD Bios and Raid also had real issues on a nightmarish MSI board.

I agree with you it should not make a difference between X470 and X570.
To your question: AMD offers basically a JBOD mode called Volume, Raidable, wich should upgrade to Raid 1 when it sees a second matchin empty new disk, and the usual RAID modes. So a Raidable can start with a single disk, e.g., writing RAID signatures on one of two drives, bringing an array up, then adding a second drive. None of this works as advertised and the UEFI implementation just falls short.

the dedicated hotswap can also be set later with the webgui

i think you should focus on installing windows on the array