Linux

47353 readers

1086 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

[email protected]

[Solved] UUID for root reverted to previous UUID (lemmy.ml)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

22 comments fedilink hide all child comments

I suddenly got the same problem in /efi/loader/entries all conf files reverted to previous uuid (first post ). To change uuid I just edited all conf files with the correct uuid for root.

I don't know if manually changing was correct or if I should use some sort command.

Bootctl status

UUID in status is wrong.

I have no idea what is reverting UUID back to the wrong one after updating system.

I could just reinstall but if possible I would like to try to fix this and learn.

Edit: Problem was that in /etc/kernel/cmdline had wrong UUID. Changed it to correct one and dracut-rebuild uses correct UUID.

you are viewing a single comment's thread
view the rest of the comments

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

I presume these are filesystem UUIDs. I also presume from your other post, that you used a live USB to fix nvidia drivers? Note that nvidia driver installers/packages trigger a initrd rebuild, and if you do that in a live environment, it’s possible that you will get the UUID of your live USB filesystem and not your actual boot drive… at least that’s my guess.

If you booted into a live USB you need to make sure that you chroot into your install on your disk whenever doing any operations on the boot loader. That involves mounting your actual disk (eg, /dev/nvme0p1) somewhere on the live USB (eg, /mnt/example), then bind-mounting the proc, sys, dev, tempfs filesystems under /mnt/example/proc, /mnt/example/sys, etc. You may also need to mount /efi under /mnt/example/efi or boot/efi (wherever you have it in your system). Next, chroot to /mnt/example. You should now have a fully functional install you normally boot into, with the only difference being that the kernel booted off the USB drive. Now you can try reinstalling drivers, rebuilding initrd, reconfiguring the bootloader, etc. Since you’re chrooted, the system should see the proper UUIDs, in theory…

If you want a more comprehensive tutorial on how to do this, look for bootloader fixing tutorials.

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

I managed to find a problem and fix it. The problem was that /etc/kernel/cmd had the wrong UUID. Thanks for giving advice about initrd and bootloader reconfiguring, might not have found a solution without it.

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

Ah, that would break things! Any idea how the incorrect UUID got into the kernel boot parameters?

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

It probably happened when I was messing with SSDs. I wanted a smaller one to be root and a bigger one as home.

Edit: Kind of happy that i managed to break something and fix it.

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

That is how you learn! Actually one of the best ways to learn, IMHO.

load more comments (15 replies)