Question System doesn't boot after installing a new M.2 SSD ?

[brainiak]

Hi, my system doesn't boot after installing a new Goodram PX700 4TB NVMe SSD:

GOODRAM PX700 SSD - GOODRAM

PX700 drive running on PCIe Gen 4 x4 interface

www.goodram.com

on an MSI MPG X570S CARBON MAX WiFi motherboard:
https://www.msi.com/Motherboard/MPG-X570S-CARBON-MAX-WIFI.

System doesn't boot either when SSD is installed in currently unused slot or a slot normally used by another device. However it is visible in UEFI. Is the disk borked? Or is is worth to invest some more time and try to debug? However, I don't have any other device to test the disk with. I can try update MOBO's firmware and try to install it again, and I can try running system from pendrive and see if it boots.

 

[Lutfij]

What BIOS version are you on for your motherboard? As for your SSD, which slot are you populating on the motherboard? What processor are you working with in tandem with the motherboard?

 

[brainiak]

I'll confirm the BIOS ver. later at home, but it's from late 2022. I've checked changelog of newer versions, nothing related to my problem, but I'll probably update it anyway and try again. Small chances, but maybe it will help.

I've tried 2nd and 3rd slot for the new storage, but similar effect. 2nd definitely works as it normally runs Samsung 980 pro (I have 2 of them, but smaller than 4TB). Except for the size they seem to be very similar devices.

CPU is a Ryzen 5950X

 

[brainiak]

Seems to be an issue with the OS (Fedora in my case). I was able to use Peppermint OS, it booted, and I was able to format the disk there. But even after that Fedora still fails to boot, however it enters emergency mode quicker. I'll investigate some more, but it'll probably end with OS reinstall.

For completion sake: BIOS update to the newest one didn't resolve the problem.

For for the help!

 

[brainiak]

Fixed. The problem was in incorrect fstab. Using UUID instead of the device name for the existing 2nd disk solved the issue (3rd disk has been assigned nvme1n1p1 that the 2nd one was using in fstab).