FS#67802 - Updating to kernel 5.8 doesn't boot (mdadm encrypt lvm2)
Attached to Project:
Arch Linux
Opened by lotan rm (lotanrm) - Wednesday, 02 September 2020, 10:42 GMT
Last edited by freswa (frederik) - Wednesday, 02 September 2020, 11:29 GMT
Opened by lotan rm (lotanrm) - Wednesday, 02 September 2020, 10:42 GMT
Last edited by freswa (frederik) - Wednesday, 02 September 2020, 11:29 GMT
|
Details
Description:
I have the following VFS setup: lvm2 luks md block Up to kernel 5.7, my initramfs would build the md devices, decrypt the root and build the volumes. Sine kernel 5.8 that doesn't work anymore. I tried with mkinitcpio and with dracut. Both don't work anymore. I use the following mkinitcpio hooks: HOOKS=(base udev autodetect modconf block sleep mdadm_udev encrypt lvm2 filesystems keyboard fsck) Going back to kernel 5.7 makes the initramfs boot again. When I'm dropped into an emergency shell in mkinitcpio, I can boot by manually executing: # cryptsetup luksOpen /dev/md1 crypt # lvm vgchange -ay # mount /dev/vg/arch /new_root # exit So there may be a problem with availability of devices early on. dracut doesn't offer me an emergency shell with rd.shell=1 :( but it returns the following errors: [ 19.310528] encrypted_key: failed to alloc_cipher (-2) [ 19.373443] encrypted_key: failed to alloc_cipher (-2) [ 19.453501] encrypted_key: failed to alloc_cipher (-2) [ 19.516595] device-mapper: table: 254:0: crypt: unknown target type [ 19.521050] encrypted_key: failed to alloc_cipher (-2) [ 19.573377] encrypted_key: failed to alloc_cipher (-2) [FAILED] Failed to start Cryptography Setup for luks-[...] which indicates to me a missing cipher (maybe a missing module?) When researching the issue, I encountered this link https://github.com/clearlinux-pkgs/linux-current/commit/72fa1696da50c0ba5ca1437e6582612fd5bf7985 which seems to fix a similar issue according to the commit message. |
This task depends upon
Closed by freswa (frederik)
Wednesday, 02 September 2020, 11:29 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#67597
Wednesday, 02 September 2020, 11:29 GMT
Reason for closing: Duplicate
Additional comments about closing:
FS#67597