luks encrypted drive not decrypted at boot and weird TTY issue

Topic: luks encrypted drive not decrypted at boot and weird TTY issue (Read 497 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.

luks encrypted drive not decrypted at boot and weird TTY issue

26 July 2023, 17:34:27

Hi,

Today i switched my init systemd from runit to openrc
Everything went well, but my 2nd drive isn't decrypted at boot, i don't understand why.

Once booted, i dont see the decrypted block device in /dev/mapper corresponding to my 2nd drive.
the 2nd drive is a sata ssd, which appears in /dev/sda
and the encrypted partition /dev/sda1 appears in /dev as well.

here is my /etc/crypttab

Code: [Select]

nvCrypt               UUID=643e22ae-5982-4c78-8447-f028e362496d     /root.key   luks,discard
datasCrypt      UUID=5da7a264-3f98-4fcd-aec4-f5cee4597a63       /datas.key      luks,discard

in the blkid command output, i can see the partition from my 2nd drive:

Code: [Select]

/dev/sda1: UUID="5da7a264-3f98-4fcd-aec4-f5cee4597a63" TYPE="crypto_LUKS" PARTUUID="17513405-01"

in the services list, i have device-mapper, dmcrypt and dmeventd started on the 'boot' runlevel

normally, when booting, it asks for my luks password and decrypt the 1st drive, which works.
Then it should use the key to decrypt the 2nd drive, but it doesn't.
It worked flawlessly with runit.

Once booted, i can decrypt manually my 2nd drive with cryptsetup luksOpen ... and mount it.

So, i must have forgotten something... but what ?

thanks

Re: only 1 luks encrypted drive decrypted at boot, instead of 2

Reply #1 – 26 July 2023, 18:01:06

Ok, i found the sollution, thanks to https://forum.artixlinux.org/index.php/topic,3346.msg21658.html#msg21658

The /etc/crypttab file is not used anymore in OpenRC, one should instead edit the /etc/conf.d/dmcrypt and write in there the descrition of the drive/key. which now works for me

Re: only 1 luks encrypted drive decrypted at boot, instead of 2

Reply #2 – 26 July 2023, 18:07:44

aaaand a last issue with my TTY :

now when i'm in the graphical interface (kde plasma), i want to go in the TTY
so i hit CTRL ALT F1
and this is what i get:

and no login prompt

same with CTRL ALT F2/F3/F4
(last line says it loads the nvidia module, then nothing after)

when not using the nvidia driver but the 'nouveau' one, i can see the full openrc sequence, with a login prompt at the end.

in my services; i have agetty.tty1-4 launched and running.

any idea ?

Re: luks encrypted drive not decrypted at boot and weird TTY issue

Reply #3 – 27 July 2023, 10:52:37

Disable early KMS?

Re: luks encrypted drive not decrypted at boot and weird TTY issue

Reply #4 – 27 July 2023, 12:58:19

after a lot of digging, it turns out there is a weird race condition between the nvidia driver and the i915 one.
with or without early KMS.
after setting i915.modeset=0 in /etc/default/grub, update-grub and reboot, problem is now solved.

thanks nous for this hint that pointed me in the good direction (again, the archlinux wiki)