[SOLVED] 980 Pro no longer recognised as such

[Kornmod]

I bought a used 980 Pro (MZVL25120) to use as my new C drive. I installed it and checked that it worked ok. The uefi as well as Samsung Magician recognized it as a 980 Pro, and everything worked fine. I then booted from a win 11 installation USB to perform a fresh installation. I did as I've always done, and deleted the partitions on the drive to create a new one for the installation, and apparently this isn't a good thing on a NVME. Win 11 installed fine but now I'm unable to see the drive in the uefi, but when I boot from my old win 10 drive I can see and use the drive, but Samsung Magician now recognise it as a PM9A1 (MZVL2512HCJQ-00BL7).

I want to update the firmware to the latest 980 Pro firmware as I hope that this would fix the problem, but unable to do so in Samsung Magician as the drive isn't recognised correctly. I've downloaded the firmware ISO and used it to create a boot USB with Rufus but I'm unable to boot from the USB drive. I've disabled secure boot but when I choose to boot from the USB (which is recogniced in the bios) it just boot into a black screen. No prompt or anything. According to Samsungs installation guide the boot USB should open a Linux shell and automatically start the firmware update process.

Any ideas of how to manually update the firmware? Or any other posible fixes?


TIA

Ryzen 5600x
MSI Tomahawk X570
32 GB g.skill ripjaw
Corsair MP600 core
Samsung 980 Pro
Corsair AXi 860

 

[dwd999]

You could try a partitioning app like Gparted, making sure that the drive has a GPT partition initializer and not an MBR partition initializer. That might solve your windows installation problem. Alternately you could try the Samsung disk wipe option just in case there's something on the ssd blocking a firmware update. Also, does your MSI bios include a disk wipe option which might be easier than using Samsung's wipe?

 

[USAFRet]

I did as I've always done, and deleted the partitions on the drive to create a new one for the installation, and apparently this isn't a good thing on a NVME.

No, that is not a problem specific to NVMe.