HTML HTML Raw Broken on boot after update... again

Support
13

So, I’m struggling with what exactly am I trying to change in grub? It was up to date, seems like. GRUB version is 2.12rc1.r49

cryptomount -u c0949ed2cf414b82bcb14563689838d5
                set root='cryptouuid/c0949ed2cf414b82bcb14563689838d5'
                if [ x$feature_platform_search_hint = xy ]; then
                  search --no-floppy --fs-uuid --set=root --hint='cryptouuid/c0949ed2cf414b82bcb14563689838d5'  9072be81-7fab-440f-9f21-40c328c93b2c
                else
                  search --no-floppy --fs-uuid --set=root 9072be81-7fab-440f-9f21-40c328c93b2c
                fi
                linux   /boot/vmlinuz-5.15-x86_64 root=UUID=9072be81-7fab-440f-9f21-40c328c93b2c rw  quiet nvme_load=YES cryptdevice=UUID=c0949ed2-cf41-4b82-bcb1-4563689838d5:luks-c0949ed2-cf41-4b82-bcb1-4563689838d5:allow-discards rd.luks.options=allow-discards root=/dev/mapper/luks-c0949ed2-cf41-4b82-bcb1-4563689838d5 apparmor=1 security=apparmor udev.log_priority=3
14

Your grub entry looks fine as it has no dashes. However something changed:

/etc/fstab

UUID=9072be81-7fab-440f-9f21-40c328c93b2c       /       ext4    defaults,noatime        0       1
/dev/mapper/luks-85a84450-3cc8-464b-aeaf-96b04e3178e0   swap    swap    defaults,noatime        0       0

blkid

/dev/sdb2: UUID="c0949ed2-cf41-4b82-bcb1-4563689838d5" TYPE="crypto_LUKS" PARTLABEL="root" 
/dev/mapper/luks-c0949ed2-cf41-4b82-bcb1-4563689838d5: UUID="9072be81-7fab-440f-9f21-40c328c93b2c" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdb3: UUID="85a84450-3cc8-464b-aeaf-96b04e3178e0" TYPE="crypto_LUKS" PARTUUID="b66180e1-5ec6-cc43-9b16-b0926e0137ef"

Fstab matches you swap partition, however not your root. So check which UUID for your root partition is correct and fix that in grub.cfg.

UUID=9072be81-7fab-440f-9f21-40c328c93b2c       /       ext4    defaults,noatime        0       1

… seems wrong and this might help:

/dev/mapper/luks-c0949ed2-cf41-4b82-bcb1-4563689838d5       /       ext4    defaults,noatime        0       1

Else check if the other UUID is correct and switch it around. Have to check how fstab entries for luks normally look like. Also remember if and why you have changed system configuration files.

15

So In previous message was the grub.cfg & everything seems like matching, right? I’m not sure what I should do to help you to figure it out.

16

If I compare the UUIDs of fstab and the entries of grub and blkid, that dont match, so it needs fixing.

17

Ran update-grub > reboot.
Error messages have changed to

ERROR: device ‘UUID=9072be81-7fab-440f-9f21-40c328c93b2c’ not found. Skipping fsck.
MOUNT: /new_root: can't find UUID=9072be81-7fab-440f-9f21-40c328c93b2c.
ERROR: failed to mount ‘UUID=9072be81-7fab-440f-9f21-40c328c93b2c’ on real root
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ~]#

fstab still same

UUID=C95C-89A9  /boot/efi       vfat    umask=0077      0       2
UUID=9072be81-7fab-440f-9f21-40c328c93b2c       /       ext4    defaults,noatime        0       1
/dev/mapper/luks-85a84450-3cc8-464b-aeaf-96b04e3178e0   swap    swap    defaults,noatime        0       0
tmpfs   /tmp    tmpfs   defaults,noatime,mode=1777      0       0
UUID=9072be81-7fab-440f-9f21-40c328c93b2c       /boot   ext4    defaults        0       0

blkid

/dev/sdb2: UUID="c0949ed2-cf41-4b82-bcb1-4563689838d5" TYPE="crypto_LUKS" PARTLABEL="root" PARTUUID="a974d905-
062a-f942-97c0-4f32a31cabb2"
/dev/sdb3: UUID="85a84450-3cc8-464b-aeaf-96b04e3178e0" TYPE="crypto_LUKS" PARTUUID="b66180e1-5ec6-cc43-9b16-b0
926e0137ef"
/dev/sdb1: LABEL_FATBOOT="NO_LABEL" LABEL="NO_LABEL" UUID="C95C-89A9" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="e
ac9643c-a029-3640-9d12-9455036d70bf"

/dev/mapper/luks-c0949ed2-cf41-4b82-bcb1-4563689838d5: UUID="9072be81-7fab-440f-9f21-40c328c93b2c" BLOCK_SIZE="4096" TYPE="ext4"

grub entry I’ve booted with

menuentry 'Manjaro Linux (Kernel: 5.15.137-1-MANJARO x64)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.15.137-1-MANJARO x64-advanced-9072be81-7fab-440f-9f21-40c328c93b2c' {
        savedefault
                load_video
                set gfxpayload=keep
                insmod gzio
                insmod part_gpt
                insmod cryptodisk
                insmod luks
                insmod gcry_rijndael
                insmod gcry_rijndael
                insmod gcry_sha256
                insmod ext2
                cryptomount -u c0949ed2cf414b82bcb14563689838d5
                set root='cryptouuid/c0949ed2cf414b82bcb14563689838d5'
                if [ x$feature_platform_search_hint = xy ]; then
                  search --no-floppy --fs-uuid --set=root --hint='cryptouuid/c0949ed2cf414b82bcb14563689838d5'  9072be81-7fab-440f-9f21-40c328c93b2c
                else
                  search --no-floppy --fs-uuid --set=root 9072be81-7fab-440f-9f21-40c328c93b2c
                fi
                linux   /vmlinuz-5.15-x86_64 root=UUID=9072be81-7fab-440f-9f21-40c328c93b2c rw  quiet udev.log_priority=3
                initrd  /intel-ucode.img /initramfs-5.15-x86_64.img
        }
18

At this point I don’t understand what I need to do, not being software engineer.

Everything matches now with the /root UUID (except it’s LUKS which can’t be mounted).

19

Again, your fstab is not correct. Try either

/dev/mapper/luks-c0949ed2-cf41-4b82-bcb1-4563689838d5       /       ext4    defaults,noatime        0       1

or

UUID=c0949ed2-cf41-4b82-bcb1-4563689838d5       /       ext4    defaults,noatime        0       1

And remember how that got changed and why …

blkid states: /dev/sdb2: UUID="c0949ed2-cf41-4b82-bcb1-4563689838d5" TYPE="crypto_LUKS" PARTLABEL="root" PARTUUID="a974d905- 062a-f942-97c0-4f32a31cabb2" for your root partition and not UUID=9072be81-7fab-440f-9f21-40c328c93b2

Grub tells the system where the kernel and root partition is located, then it starts a bare minimum Linux system. That reads fstab and actually mounts the partition. If in the chain grub.cfg > fstab some mismatch exists it will bail out. Errors can also happen if /etc/default/grub has a false entry, as that is the base to generate your grub.cfg file.

20

Changing didn’t work. In grub linux root= to both ‘/dev/mapper/luks-c0949ed2-cf41-4b82-bcb1-4563689838d5’ and ‘UUID=c0949ed2-cf41-4b82-bcb1-4563689838d5’.

21

I gave you several information on what the problem might be. blkid is the output of your current information of your system. Your root partition has UUID= c0949ed2-cf41-4b82-bcb1-4563689838d5. If you check your older posts, that matches in /etc/default/grub and /boot/grub/grub.cfg. However your /etc/fstab has a different UUID there. So read my posts again and try to fix that.

22

It matches
Fix that
What? Where?

Again, I’m not into that stuff & not the one who broke it (manjaro team did). And you can’t even explain what I need to do in OS you guys built. What do you want me to change? Fstab? Grub? Where, which line, how it should look? I’m not software engineer, I’m trying to get things working after pressing update button. Which is not recommended way to update (RLY? So why it’s there?!)

23

He mentioned a possible solution in his second-to-last reply. (Go up four replies from here)

You need to change some lines in fstab with values from blkid

24

Thanks for translating linux language, changed UUID in fstab for root, not working.

# <file system> <mount point> <type> <options> <dump> <pass>

UUID=C95C-89A9  /boot/efi       vfat    umask=0077      0       2
UUID=c0949ed2-cf41-4b82-bcb1-4563689838d5       /       ext4    defaults,noatime        0       1
/dev/mapper/luks-85a84450-3cc8-464b-aeaf-96b04e3178e0   swap    swap    defaults,noatime        0       0
tmpfs   /tmp    tmpfs   defaults,noatime,mode=1777      0       0
UUID=9072be81-7fab-440f-9f21-40c328c93b2c       /boot   ext4    defaults        0       0

Putting /dev/mapper/luks- doesn’t work either. Asking for “crypto_LUKS”.

25

Am I the only one that reacts to that there are 2 boots in there?

AFAIK systemd boot uses /boot but grub uses /boot/efi right?

There are TWO boot partitions, but maybe this has something to do with encryption?
I have read to many of these posts to decide to not use encryption (but that might have to do with me being a chicken when it comes to encryption on complete filesystems, I decided to use a vault for my most precious data like passwords and stuff and then ONLY unlock that when I need something and then locking it immediately again)

26

Not an option in oppressive governments world.

27

Not sure what you mean by that, when you run your system, the data is just as unencrypted as a non encrypted system, so if spyware is you concern, this is not a protection.
The difference is when the system is turned off, so if someone steals you computer, they should not be able to access it (assuming you enter the password every single time you boot or this wont be a protection either).
With my setup my most valuable data is ALWAYS encrypted even if I run the system. It is only unencrypted if I WANT to access it.

28

I understand that, so I would use power off button to encrypt it back. Also I would love to use TPM2, but since Manjaro Team is not capable into AES encryption. Well.

29

And by then it is already too late buddy. The data has been stolen.
I just wrote that so you understand what encryption actually is doing on your system, you seem a bit misinformed.

But if someone who actually knows encryption knows what the dual boot partitions is about, that would probably be helpful for this thread.

UUID=C95C-89A9  /boot/efi       vfat    umask=0077      0       2
UUID=9072be81-7fab-440f-9f21-40c328c93b2c       /boot   ext4    defaults        0       0

No matter what, blaming Manjaro and having an attitude will NOT help you here.
Try to stay calm and read what is said multiple times if you don’t understand, the forum is for learning, not spoon feeding solutions.
If you STILL do not understand, ask specifically about that, it is pretty clear you are not putting much effort into actually trying to learn/understand but rather lash out in frustration. I get that, I have been known to do the same. :innocent:

The risk is the thread dying if you do not follow advice.

30

Because I don’t speak telepathy.