FS#60522 - [mkinitcpio] Unable to boot on encrypted LVM root after upgrade to kernel 4.18.14
Attached to Project:
Arch Linux
Opened by frank (fasseg) - Monday, 22 October 2018, 05:53 GMT
Last edited by Jelle van der Waa (jelly) - Monday, 18 September 2023, 17:44 GMT
Opened by frank (fasseg) - Monday, 22 October 2018, 05:53 GMT
Last edited by Jelle van der Waa (jelly) - Monday, 18 September 2023, 17:44 GMT
|
Details
Description:
After the kernel upgrade to 4.18.14 my Box did not boot anymore, since it was unable to find the encrypted device (/dev/sda5 in my case). I'm using a encrypted root device on a LVM volume. Fallback initrd and removing the 'autodetect' hook makes the system bootable again. Additional info: * Laptop: HP Elitebook 840 G5 * Processor: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz * Disk: SanDisk SD7TN3Q-512G-1006 * core/linux 4.18.14.arch1-1 * core/lvm2 2.02.181-1 * core/mkinitcpio 24-3 * core/cryptsetup 2.0.4-1 * core/grub 2:2.02-7 * LVM VG: --- Volume group --- VG Name kaxpi00000025-vg System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 20 VG Access read/write VG Status resizable MAX LV 0 Cur LV 7 Open LV 3 Max PV 0 Cur PV 1 Act PV 1 VG Size <476.46 GiB PE Size 4.00 MiB Total PE 121973 Alloc PE / Size 120634 / <471.23 GiB Free PE / Size 1339 / 5.23 GiB VG UUID q1ffB3-G8RF-AUhg-Cv7B-QNDU-FcnV-0jBnI3 * LUKS header data: LUKS header information for /dev/sda5 Version: 1 Cipher name: aes Cipher mode: xts-plain64 Hash spec: sha256 Payload offset: 4096 MK bits: 512 * Partition layout: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 477G 0 disk ├─sda1 8:1 0 487M 0 part /boot ├─sda2 8:2 0 1K 0 part └─sda5 8:5 0 476.5G 0 part └─sda5_crypt 254:0 0 476.5G 0 crypt ├─kaxpi00000025--vg-root 254:1 0 23.3G 0 lvm ├─kaxpi00000025--vg-var 254:2 0 9.3G 0 lvm ├─kaxpi00000025--vg-swap_1 254:3 0 23.8G 0 lvm [SWAP] ├─kaxpi00000025--vg-tmp 254:4 0 1.9G 0 lvm ├─kaxpi00000025--vg-home 254:5 0 130G 0 lvm ├─kaxpi00000025--vg-arch--root 254:6 0 128G 0 lvm / └─kaxpi00000025--vg-arch--home 254:7 0 155G 0 lvm /home sdb 8:16 0 1.8T 0 disk ├─sdb1 8:17 0 1.1T 0 part /backup └─sdb2 * Grub kernel and inird lines: linux /vmlinuz-linux root=/dev/mapper/kaxpi00000025--vg-arch--root cryptdevice=/dev/sda5:sda5_crypt resume=/dev/mapper/kaxpi00000025--vg-swap_1 initrd /intel-ucode.img /initramfs-linux.img Steps to reproduce are probably: 1. Install arch on encrypted lvm root device 2. Boot non-fallback kernel with the autodetect hook in mkinitcpio.conf |
This task depends upon
Closed by Jelle van der Waa (jelly)
Monday, 18 September 2023, 17:44 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/m kinitcpio/mkinitcpio/issues/203
Monday, 18 September 2023, 17:44 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/m kinitcpio/mkinitcpio/issues/203
Comment by Doug Newgard (Scimmia) -
Friday, 26 October 2018, 15:40 GMT
Comment by frank (fasseg) - Monday,
29 October 2018, 07:27 GMT
Comment by Rowan Ruseler (rowanr) -
Wednesday, 14 November 2018, 17:54 GMT
Comment by
Buggy McBugFace (bugbot) - Tuesday,
08 August 2023, 19:11 GMT
Still an issue with mkinitcpio 25-1?
Yes, I still have the same issue.
removed previous comment, apologies I didn't fully read your log.
This is an automated comment as this bug is open for more then 2
years. Please reply if you still experience this bug otherwise
this issue will be closed after 1 month.