F5F Stay Refreshed Hardware Desktop Encounter problems with NVMe RAID 1 during setup of a new system

Encounter problems with NVMe RAID 1 during setup of a new system

Encounter problems with NVMe RAID 1 during setup of a new system

N
NerdyPlayz_YT
Junior Member
Find
31
02-23-2021, 12:21 PM
#1
Hey everyone, after six years I chose to upgrade my setup. I own a Gigabyte Aorus Pro ICE x870e MB and two brand new WD SN850X 4TB NVMe drives that I plan to use as the main storage. This decision came after a tough experience with my old gaming PC SSD drive failing badly, which wasn’t pleasant. Now I want to keep the system drive mirrored, similar to what I’m doing on my current rig that will be moved once the new unit is up and running. I’ve faced some trouble getting BIOS settings to my liking, but eventually I got the RAID XPert 2 tool working, removed the default arrays, and set up a fresh RAID 1 array of 4TB. During the Windows 11 installation, I noticed it created four partitions next to my boot USB drive. After some research, I realized the disks were initialized with MBR instead of GPT, so after a quick reboot and some commands I had two 4TB drives ready. The next task is installing the AMD Raid Bottom driver, followed by the other two, which I’m struggling to remember. The issue is that when I load the USB stick and run the bottom driver, both disks vanish except the stick itself, leaving me completely confused and stuck. I’ve been working through this for hours without clear guidance. Recently, I changed the USB port from 3.2 to 2.0 and renamed a file from prepped to_unattended.xml to to_unattended.xml, so it won’t run automatically. Now during the Windows 11 setup I have to manually pick options like language and keyboard layout. Once that’s done, I expect the disk selection screen to show both NVMe drives and the USB stick. After loading the bottom driver I’m directed to accept conditions, where the drives disappear but I can still click Load driver. I moved forward with the controller and config driver install, but now I’m stuck again—two disks listed instead of one. It’s a frustrating cycle of progress and setbacks.
Reply
Reply
N
NerdyPlayz_YT
02-23-2021, 12:21 PM #1

Hey everyone, after six years I chose to upgrade my setup. I own a Gigabyte Aorus Pro ICE x870e MB and two brand new WD SN850X 4TB NVMe drives that I plan to use as the main storage. This decision came after a tough experience with my old gaming PC SSD drive failing badly, which wasn’t pleasant. Now I want to keep the system drive mirrored, similar to what I’m doing on my current rig that will be moved once the new unit is up and running. I’ve faced some trouble getting BIOS settings to my liking, but eventually I got the RAID XPert 2 tool working, removed the default arrays, and set up a fresh RAID 1 array of 4TB. During the Windows 11 installation, I noticed it created four partitions next to my boot USB drive. After some research, I realized the disks were initialized with MBR instead of GPT, so after a quick reboot and some commands I had two 4TB drives ready. The next task is installing the AMD Raid Bottom driver, followed by the other two, which I’m struggling to remember. The issue is that when I load the USB stick and run the bottom driver, both disks vanish except the stick itself, leaving me completely confused and stuck. I’ve been working through this for hours without clear guidance. Recently, I changed the USB port from 3.2 to 2.0 and renamed a file from prepped to_unattended.xml to to_unattended.xml, so it won’t run automatically. Now during the Windows 11 setup I have to manually pick options like language and keyboard layout. Once that’s done, I expect the disk selection screen to show both NVMe drives and the USB stick. After loading the bottom driver I’m directed to accept conditions, where the drives disappear but I can still click Load driver. I moved forward with the controller and config driver install, but now I’m stuck again—two disks listed instead of one. It’s a frustrating cycle of progress and setbacks.

Reply
Reply
B
Bifes_PT
Member
Find
205
02-23-2021, 02:52 PM
#2
I discovered a fix. The issue lay in the autounattend.xml file on my install USB. It really disrupted the raid driver installation. When I deleted that file, the RAID drive worked properly in BIOS, allowing me to install all three required drivers. After that, it was just the usual next steps in Windows installation. Perhaps one day, someone else will find this helpful.
Reply
Reply
B
Bifes_PT
02-23-2021, 02:52 PM #2

I discovered a fix. The issue lay in the autounattend.xml file on my install USB. It really disrupted the raid driver installation. When I deleted that file, the RAID drive worked properly in BIOS, allowing me to install all three required drivers. After that, it was just the usual next steps in Windows installation. Perhaps one day, someone else will find this helpful.

Reply
Reply