Happy to hear that you could solve it yourself!
I have some experience with AMD’s motherboard RAID software and encountered a few bugs, one sounded like the situation you had been in:
-
To use drives with AMD’s RAID software you have to initialize them, this means the software is writing a bit of meta data to the drives “Yay, I am drive 1 of 2 of a RAID0 volume, my serial number is abcd1234, drive 2 of 2 has serial number efg5678” and similar meta data is written to drive 2;
-
In current Windows versions normal NVMe SSDs are mostly handled by a generic Microsoft “Standard NVM Express Controller” storage controller in Windows Device Manager;
-
When using NVMe SSDs with AMD’s RAID software, two AMD devices “steal” the NVMe SSD away from the “Standard NVM Express Controller”, these are called “AMD-RAID Bottom Device” and “AMD-RAID Controller [storport]”, you get one of each for each physical NVMe SSD that is handled by AMD RAID;
Bugs:
-
Sometimes, if you delete an AMD RAID volume the SSD isn’t “returned” to Microsoft’s “Standard NVM Express Controller” which leads to it not showing up in Windows at all, but just fine in the UEFI and other operating systems like Linux;
-
To solve this you have to uninstall the devices “AMD-RAID Bottom Device” and “AMD-RAID Controller [storport]” in Windows Device Manager with its drivers and sometimes reboot the system;
-
This would be catastrophic IF Windows itself is installed on and booting from an AMD RAID volume since then Windows would no longer be able to boot since it doesn’t have the required drivers to do so.