You are not logged in.

#1 2024-01-22 09:59:03

arthu
Member
Registered: 2024-01-22
Posts: 12

GRUB can't boot into encrypted partition

Hi, I recently upgraded my system and have had some issues since. Now, I can't boot into the system anymore since grub seems to have some issues with my encrypted partition. Attached, you can see the error message and my /etc/default/grub file. Notice that the UUID in the error message doesn't match the one specified in the file. Instead, it's the UUID of the decrypted partition. However, I always run mkinitcpio -P and grub-mkconfig -o /boot/grub/grub.cfg after modifying the file.

Error: https://media.discordapp.net/attachment … 205136.jpg
/etc/default/grub: https://media.discordapp.net/attachment … 205429.jpg

Last edited by arthu (2024-01-22 10:05:31)

Offline

#2 2024-01-22 10:22:18

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 1,992
Website

Re: GRUB can't boot into encrypted partition

You unlock the LUKS partition as "system" but try to mount / from "new_root".
Do you use LVM on LUKS?
If so, what's your LVM layout?
Also please show your /etc/mkinitcoip.conf.

Last edited by schard (2024-01-22 10:26:13)


macro_rules! yolo { { $($tokens:tt)* } => { unsafe { $($tokens)* } }; }

Offline

#3 2024-01-22 10:34:30

arthu
Member
Registered: 2024-01-22
Posts: 12

Re: GRUB can't boot into encrypted partition

I've changed it to this: IMG_20240122_112810.jpg?ex=65c0b950&is=65ae4450&hm=9d85208e04609592b180f060277af494e53596071da5cb6efd05554f0c38c22c&=&format=webp&width=1099&height=618 and it still isn't working.
As to whether or not I'm using LVM i'm honestly not sure.
Here's the requested file: IMG_20240122_113917.jpg?ex=65c0bae8&is=65ae45e8&hm=d7e235427d19a97b3cc0d03ba9dee15eec0817bd4d5123bc7cced6d02dc86b5c&=&format=webp&width=1099&height=618

Last edited by arthu (2024-01-22 10:41:28)

Offline

#4 2024-01-22 10:52:07

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 1,992
Website

Re: GRUB can't boot into encrypted partition

The decrypted device will be created under /dev/mapper.
i.e. cryptdevide=UUID=<UUID>:my_root will be created as /dev/mapper/my_root.
And don't use /dev/sdX? paths to specify devices as they are nondeterministic.

Last edited by schard (2024-01-22 10:54:08)


macro_rules! yolo { { $($tokens:tt)* } => { unsafe { $($tokens)* } }; }

Offline

Board footer

Powered by FluxBB