I am extremely new to Linux/ Fedora, so I apologize for my ignorance and post formatting in advance.
I’ve been using Fedora 42 on my Framework laptop for around a month. I’ve had the system off for a couple of days and, when I turned it on the other day, it says that no boot device could be found. Sure enough, there are no boot partitions listed in the Boot Manager.
I used a live USB of Fedora to dig a little further. The drive was showing up and I could access files on it. Running fdisk, I got an error for the drive, stating
“GPT PMBR size mismatch… …will be corrected by write”
“The backup GPT table is not on the end of the device.”
There are also only two partitions that show up with that command,
/dev/nvme0n1p2 - 1G - Linux extended boot
/dev/nvme0n1p3 - 1.8T - Linux filesystem
There is also an unallocated portion of the drive (600MB according to KDE Partition Manager). I wondering if that’s the part that somehow got messed up.
I don’t think I would have done anything on purpose to get my device in this state. I’m hoping there’s a way I can boot back into it without have to reinstall Fedora from scratch. This has been a learning experience for me and this has left me feeling a tad discouraged.
I also want to clarify that I’m just running Fedora. Not dual booting with Windows or any other OS.
I’ve attached some relevant pictures as well. Hope that helps and thank you!
I had used my device last Friday before trying to boot it up. I didn’t download anything other than updates from the Discover app (nothing additional from Framework’s website). I’d imagine that’s also where new firmware is acquired, though.
Also, referring to your linked post, I want to clarify that I am on the KDE edition of Fedora 42. Also, my boot drive is encrypted, though I’m not sure how much that matters.
Yeah… I thought it was strange to see only two partitions. With my limited understanding of Linux thus far, I knew that one was missing.
Here’s the output from that command
PATH PARTTYPE PARTTYPENAME FSTYPE MOUNTPOINTS
/dev/nvme0n1
/dev/nvme0n1p2 bc13c2ff-59e6-4262-a352-b275fd6f7172 Linux extended boot ext4
/dev/nvme0n1p3 0fc63daf-8483-4772-8e79-3d69d8477de4 Linux filesystem crypto_LUKS
Those are the only ones that show up on my main install drive.
I have to wonder what I could have inadverently done to cause this to happen. I’ve seen a handful of forum posts and videos in the past week where people were unable to boot into Fedora following an update.
I’ve decided to just reinstall Fedora from scratch and go from there. Thank you to those that took the time to read and reply!
Seems like a very strange issue. If anyone has any insights as to how this may have happened, I’d love to hear them. I think I’ll try to set up some sort of backup so that I don’t have to do this again, haha.
There might have been helpful information in /var/log, but if you don’t have backups, a reinstall would have removed it. For future reference, you can often view logs on non-booting systems by running journalctl in a Live USB environment. Linux is a community effort, so when time and resources permit, every effort to should be made to document issues. Even if there is no good solution, the details can help others who encounter the same problem (and for every user that reports an issue, there are often many others who may search for similar problems but don’t open a forum topic).
Thank you for the advice, genuinely. I know I came across as a tad impatient. I use this device at work, so I wanted something working and stable so I wasn’t left in a bind.
I’ll definitely look at any potential logs in the future if something like this comes up again. I agree it’s good to be a team player and pass along knowledge.
