New m.2 SSD shows in BIOS, Device Manager-but not Disk Manager

[mikeski30]

Hi all,

 

I've been tearing out my remaining hair trying to figure this out, so I'm here to ask for some help and would appreciate any advice/insight!

My current system has one drive, a Samsung EVO 860 2.5in SSD in the Sata 3_0 slot. My MOBO has a couple m.2 slots and supports NVMe, so I figured I'd grab Samsung 970 EVO Plus NVMe m.2 512GB since it was on sale at BB this week. 

 

After installing, the 970 is recognized in BIOS as an NVME device and shows up in Win 10 Device Manager, so I installed the Samsung driver and the NVME Controller was updated accordingly. However, it's not showing up in Disk Manager, nor in Samsung's Magician software, nor in EaseUS partition manager. I've tried updating all my drivers with no luck. I tried moving between m.2_1 and m.2_2 with no luck as well. AHCI is also enabled in BIOS. 

 

I "believe" the BIOS is up to date, but I can't be sure as CyberpowerPC support isn't the best. The MOBO has "CyberpowerPC B360M Xtreme Powered by ASROCK" printed on it, but the CyberpowerPC site has no drivers for it and directs you to the ASRock site. The ASRock site has 4 B360M model MOBOs, but none of them is the "Xtreme"... the Pro4 layout looks to be pretty much the same, but who knows!? Either way, I downloaded the ASRock Store App, which found some drivers for the board, and I updated them without bricking anything.... so I guess it worked??

 

One strange thing I just noticed in Device Properties is both drives have the same location info: Bus Number 0, Target Id 0, LUN 0. Also in Disk Management, when listing the properties of the C drive on Disk 0 (the 860 SSD), it lists BOTH disk drives. I'm including a screen shot of all that. 

 

I assume the duplicate location info is causing a problem, but I can't find any info on how to change it for the NVME drive to clear the conflict. Of course, it could be something else as well, but I'm at a loss. Any and all help would be greatly appreciated! 

 

Thanks,

 

Mike

 

 

[mikeski30]

Got it to work! For anyone in a similar situation, I double checked the newly updated "Supported NVMe" list (for the Mobo I suspect is the right one) and while there are a few Samsung NVMe's listed, the serial for my EVO 970 Plus was not. So I went out and grabbed a WD Black NVMe (SN750... listed as supported), plugged it in, and boom Windows recognized it immediately. 

 

Lesson learned... the "supported lists" could very well be accurate!

[Grayswandir]

I just installed the same drive (1TB model) and didn't have any problems at all, but I've been around computers for a very long time. Things often go wrong even if you do everything perfectly, it's the nature of the beast. So you wound up taking the Samsung back then? That sucks, but WD makes some great hard drives. I have a WD Caviar Black 640gb (HDD) that's still going strong eleven years later!

[hudson.medina56]

i am having the same problem but mine is actually supported by the motherboard and i feel like im going crazy trying to find out what is wrong