this post was submitted on 27 Oct 2023
19 points (100.0% liked)

Linux

48137 readers
498 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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

My system keeps booting into the live image of Pop!_OS 22.04 rather than my encrypted partition. I ran boot-repair-disk but the system keeps going to the install image. I verified that the bios is pointing to the correct disk at boot and I verified that my data is still in the encrypted partition.

Any help would be appreciated.

ThinkPad X1 Extreme Gen 2 Pop!_OS 22.04 LTS Nvidia

EDIT: I found the fix. I was able to dig out a System76 article that fixed me right up. See below.

https://support.system76.com/articles/bootloader/

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago (1 children)

Well then there's yer problem 👍

[–] [email protected] 2 points 1 year ago

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.