How did you install? Why is the install image still around to even be able to boot?
this post was submitted on 27 Oct 2023
19 points (100.0% liked)
Linux
48112 readers
636 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
The system has been around for years. It was originally a 20.04 install which I upgraded to 22.04. My guess is that the "install" is actually the recovery image partition.
In that case you should be able to rule out borked boot priority.
I'd be looking at the bootloader, next. You don't mention having multiple boot options, but it could be defaulting to the wrong one for some reason. Or because the one you want is unable to boot despite being otherwise fine.
I never multiboot (had enough of that pain years ago). I'll look into the bootloader but I assumed that Boot Repair would have corrected that. It might be that it didn't see the bit pointing towards the rescue partition as a problem.
You still have a bootloader, even if you only have one OS. And if you do have a recovery image as you say, you are multi-booting.
I recall the ability to boot from an encrypted partition requiring some additional config for grub, but I see no reason for boot repair not to account for that.
If you use some other bootloader, I've no experience.
~~Doesn't it even tell you to unplug your Install medium.
Just unplug your USB drive and boot.
(I don't want to sound too obvious, but at least do it first and tell me if it was really the only issue)~~
EDIT: I read in a comment that you did an upgrade.
The upgrade was about six months ago
Boot into the live image and check your disks and boot partitions. If nothing looks off there, try and force your Bios to boot from the install disk directly. If still not helpful, you may need to chroot from the live image and update/repair grub to make sure it's loading properly. Lots of guides on how to do this out there if you're unfamiliar.
Ok. The encrypted partition is nvme0n1p3. The /boot partition is n1p1 and the recovery/install partition is n1p2. For some reason the laptop is booting off of n1p2 instead of n1p1. N1p1 has the BOOT directory as well as the .efi files.
Well then there's yer problem 👍
I found the fix. It was a bit more involved than I expected but I'm back up and running. I've added the article to my original post.
I assume Pop!_OS shows the Systemd-boot selection at boot. If so, is it possible to switch which partition to boot to?