My system keeps booting into an install instead of the encrypted disk. [FIXED]

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.

support.system76.com/articles/bootloader/

ReakDuck, (edited )

~~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.

JoMiran,
@JoMiran@lemmy.ml avatar

The upgrade was about six months ago

Skerse,
@Skerse@lemmy.world avatar

I assume Pop!_OS shows the Systemd-boot selection at boot. If so, is it possible to switch which partition to boot to?

just_another_person,

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.

JoMiran,
@JoMiran@lemmy.ml avatar

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.

just_another_person,

Well then there’s yer problem 👍

JoMiran,
@JoMiran@lemmy.ml avatar

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.

MentalEdge,
@MentalEdge@sopuli.xyz avatar

How did you install? Why is the install image still around to even be able to boot?

JoMiran,
@JoMiran@lemmy.ml avatar

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.

MentalEdge,
@MentalEdge@sopuli.xyz avatar

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.

JoMiran,
@JoMiran@lemmy.ml avatar

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.

MentalEdge,
@MentalEdge@sopuli.xyz avatar

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.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • uselessserver093
  • Food
  • [email protected]
  • aaaaaaacccccccce
  • test
  • CafeMeta
  • testmag
  • MUD
  • RhythmGameZone
  • RSS
  • dabs
  • oklahoma
  • Socialism
  • KbinCafe
  • TheResearchGuardian
  • SuperSentai
  • feritale
  • KamenRider
  • All magazines
    •