[SOLVED] New NVME SSD M.2 Storage is detected in BIOS but not in Disk Management.

[breshaiah]

Just bought a Samsung 970 evo 500gb to supplement storage (NVME SSD M.2). The storage is detected in BIOS, but not in Disk Management, so I cannot initialize. My SATA configuration is in RAID. I have one RAID 1 setup with 2 WD blues 500gb (for storage) and I am booting my PC using a Samsung NVME SSD M.2 Evo Plus.
My MOBO is AMD AM4 X570-PLUS (Wi-Fi) ATX.

Details of the M.2 for the MOBO:

3rd Gen AMD Ryzen™ Processors :
1 x M.2 Socket 3, with M Key, Type 2242/2260/2280/22110(PCIE 4.0 x4 and SATA modes) storage devices support

2nd Gen AMD Ryzen™ Processors :
1 x M.2 Socket 3, with M Key, Type 2242/2260/2280/22110(PCIE 3.0 x4 and SATA modes) storage devices support

AMD X570 chipset :
1 x M.2 Socket 3, with M Key, Type 2242/2260/2280/22110(PCIE 4.0 x4 and SATA modes) storage devices support
8 x SATA 6Gb/s port(s)

Support Raid 0, 1, 10

My CPU is Ryzen 7 3800X.

Any ideas why my NVME M.2 storage device isn't appearing?

 

[rgd1101]

in device manager?
windows 10 storage spaces?

 

[breshaiah]

Please see the attached photos for further explanation.

BIOS showing new NVME SSD M.2 drive (Samsung EVO 970 500GB) - https://ibb.co/cJpdMyV
New drive not showing up in Disk Management - https://ibb.co/N2MGKXj
Device Manager not detecting new drive, only existing drives - https://ibb.co/tJ9WMzf
Storage Controllers in Device Manager - https://ibb.co/JcqBbKn

 

[SkyNetRising]

Did you check windows storage spaces?

Also check other devices in Device Manager. There should be 2 NVME controllers. One atttached to chipset and other attached to cpu.
You may need to install nvme driver for cpu attached nvme controller.

 

[rgd1101]

check bios to see if it turn off.

 

[breshaiah]

Did you check windows storage spaces?

Also check other devices in Device Manager. There should be 2 NVME controllers. One atttached to chipset and other attached to cpu.
You may need to install nvme driver for cpu attached nvme controller.

Thanks so much - you were right - I was missing a second NVME controller. Got it working now.

Cheers!