x570 Extreme4 - Unable to boot from PCIE M2

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hello!

I've had a fun weekend of installing a new x570 Extreme4 into my PC because I recently purchased an Apollo Twin X sound card that requires Thunderbolt 3. That part went perfectly fine and everything is working, but the reason for my post is that I'm having a strange issue with trying to get a new PCIe 3.0 x4 M2 drive (not SATA) to show in the BIOS.

The drive itself shows within Windows 10 and I can use it as a normal storage device right now. However, after cloning my Windows 10 boot partition to it, the drive doesn't show in the BIOS. Similarly, after reformatting the drive and emptying it, it still doesn't show in the BIOS despite working perfectly fine within Windows.

I've checked both the 'Boot' tab within the BIOS and also the 'Advanced' tab where it has storage options.

Is there something glaringly obvious I'm missing here?

Build:
Mobo - ASRock Extreme4 x570
CPU - Ryzen 2700X
RAM - Gskill DDR4 3200 
GFX Card - RX580 8GB DDR5
M2 SSD - Inland Premium 1TB PCIe NVME 3.0 x4
Other SSD - 2x Crucial MX500 (1 @ 500GB, 1 @ 750GB), 1x Pioneer 1TB SSD
Thunderbolt 3 Card - GC-Alpine Ridge (2.0)
CPU Cooler - NZXT x62 Kraken

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
iamfaraday Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 18 Dec 2019 Status: Offline Points: 4	Post Options Post Reply Quote iamfaraday Report Post Thanks(0) Quote Reply Topic: x570 Extreme4 - Unable to boot from PCIE M2 Posted: 18 Dec 2019 at 2:02am
	Hello! I've had a fun weekend of installing a new x570 Extreme4 into my PC because I recently purchased an Apollo Twin X sound card that requires Thunderbolt 3. That part went perfectly fine and everything is working, but the reason for my post is that I'm having a strange issue with trying to get a new PCIe 3.0 x4 M2 drive (not SATA) to show in the BIOS. The drive itself shows within Windows 10 and I can use it as a normal storage device right now. However, after cloning my Windows 10 boot partition to it, the drive doesn't show in the BIOS. Similarly, after reformatting the drive and emptying it, it still doesn't show in the BIOS despite working perfectly fine within Windows. I've checked both the 'Boot' tab within the BIOS and also the 'Advanced' tab where it has storage options. Is there something glaringly obvious I'm missing here? Build: Mobo - ASRock Extreme4 x570 CPU - Ryzen 2700X RAM - Gskill DDR4 3200 GFX Card - RX580 8GB DDR5 M2 SSD - Inland Premium 1TB PCIe NVME 3.0 x4 Other SSD - 2x Crucial MX500 (1 @ 500GB, 1 @ 750GB), 1x Pioneer 1TB SSD Thunderbolt 3 Card - GC-Alpine Ridge (2.0) CPU Cooler - NZXT x62 Kraken

Ray62 Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 01 Jul 2018 Location: Germany, Berlin Status: Offline Points: 706	Post Options Post Reply Quote Ray62 Report Post Thanks(0) Quote Reply Posted: 18 Dec 2019 at 2:36am
	Now it is the build + a new M2 drive + the sound card? I am missing to which PCIe and M2 slots you connected which devices and from which drive you are currently booting. However, sometimes after adding new hardware a CMOS reset helps the bios to detect all devices correctly. You also can swap the M2 drives for a test (if i understand it correctly that you use 2 of them).
	Asrock Fatal1ty X370 Professional Gaming Offline Under test: MSI X570_MEG_ACE \| AMD Ryzen 9 3900X \| Scythe Mugen5 \| 2x16GB F4-3200C14D-32GTZ@3466 \| ASUS GeForce GTX 1080 Ti FE

iamfaraday Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 18 Dec 2019 Status: Offline Points: 4	Post Options Post Reply Quote iamfaraday Report Post Thanks(0) Quote Reply Posted: 18 Dec 2019 at 10:41am
	Appreciate you wanting to help but I just now figured it out! It was because RAID mode was enabled for some reason. I might've turned it on by accident at some point, but now it works perfectly fine. Thank you for the response though!