FS#46172 - [linux] [systemd] [mkinitcpio] [dm-crypt] failed boot if too slow to enter LUKS passphrase
Attached to Project:
Arch Linux
Opened by Moviuro (Moviuro) - Tuesday, 01 September 2015, 18:55 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 03 July 2016, 17:56 GMT
Opened by Moviuro (Moviuro) - Tuesday, 01 September 2015, 18:55 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 03 July 2016, 17:56 GMT
|
Details
Description:
When booting, LUKS passphrase must be entered "fast" after the prompt first appears. ("fast" means that 5 minutes is too long and will triger the bug) This bug happens on both UEFI and legacy BIOS boot. This bug happened for many versions of the kernel, systemd and mkinitcpio. Additional info: * local/linux 4.1.6-1 * local/systemd 224-1 * local/mkinitcpio 18-2 * local/cryptsetup 1.6.7-1 HOOKS="systemd autodetect modconf block sd-vconsole keyboard sd-encrypt filesystems" The prompt reads: [ OK ] Reached target encrypted volumes Starting file system check on ... [ OK ] Starting file system check on ... Mounting /sysroot... [ OK ] Mounted /sysroot. (And nothing more, it halts here) Steps to reproduce: * boot with the aforementioned HOOKS in your initramfs. * Wait * Enter LUKS passphrase |
This task depends upon
Closed by Dave Reisner (falconindy)
Sunday, 03 July 2016, 17:56 GMT
Reason for closing: Upstream
Additional comments about closing: Not a packaging bug. If disabling timeouts doesn't work, it's a problem for upstream systemd to resolve.
Sunday, 03 July 2016, 17:56 GMT
Reason for closing: Upstream
Additional comments about closing: Not a packaging bug. If disabling timeouts doesn't work, it's a problem for upstream systemd to resolve.
* Linux 4.2.2-1
* systemd 226-3
* mkinitcpio 18-2
* cryptsetup 1.6.7-1
luks-c3c2fcfa-9265-4da7-a927-0a18d83d8d77 UUID=c3c2fcfa-9265-4da7-a927-0a18d83d8d77 - luks,discard
luks-c3c2fcfa-9265-4da7-a927-0a18d83d8d77 UUID=c3c2fcfa-9265-4da7-a927-0a18d83d8d77 - luks,discard,x-systemd.device-timeout=0
With "base" and "udev" works fine.