Linux

48145 readers

872 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

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

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

submitted 1 year ago* (last edited 1 year ago) by JoMiran@lemmy.ml to c/linux@lemmy.ml

12 comments fedilink hide all child comments

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

[–] JoMiran@lemmy.ml 1 points 1 year ago (1 children)

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@sopuli.xyz 6 points 1 year ago (1 children)

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@lemmy.ml 2 points 1 year ago (1 children)

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@sopuli.xyz 2 points 1 year ago

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.