Mark: With a LUKS encrypted system, when a new kernel is installed "update- initramfs -u -k $KERNEL_VERSION" is executed.
As part of that cryptsetup hooks scripts are called. They examine /etc/fstab and /etc/crypttabto determine if the root file-system, or swap (which may be used for hibernation) are encrypted. If so cryptsetup and its supporting libraries and scripts are copied into the initrd.img-$KERNEL_VERSION file that is being built. Additionally, the /etc/crypttab entry for the root file-system device is added to the initialramfs's /conf/conf.d/cryptroot. At boot-time the initialramfs cryptsetup scripts read this file and should unlock the LUKS container. As that is not happening you should, when dropped at the initialramfs shell, check for the existence of the config and the tooling: # ls -l /conf/conf.d/cryptroot /bin/cryptroot-unlock /sbin/cryptsetup /lib/cryptsetup/askpass If they are present you can manually unlock using: # cryptsetup open /dev/sdXY sdXY_crypt Note: identify the LUKS container using: # blkid | grep crypt_LUKS and replace my example 'sdXY' with your device name. After a successful unlock scan for LVM volumes: # vgchange -ay Then let the init system resume operations by pressing Ctrl+D or typing: # exit If you're not in the initramfs but are looking at the broken system's file system from a LiveISO or similar you can check whether the cryptsetup tools are included in the initrd.img file using this command: # sudo ls -l /boot/initrd.img* # sudo lsinitramfs /boot/initrd.img-$KERNEL_VERSION | grep crypt cryptroot-keyfiles cryptroot-keyfiles/cryptswap1.key cryptroot-keyfiles/LUKS_VG02.key sbin/cryptsetup usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 conf/conf.d/cryptroot bin/cryptroot-unlock lib/cryptsetup lib/cryptsetup/askpass lib/x86_64-linux-gnu/libgcrypt.so.20.2.1 lib/x86_64-linux-gnu/libcryptsetup.so.12 lib/x86_64-linux-gnu/libgcrypt.so.20 lib/x86_64-linux-gnu/libcryptsetup.so.12.2.0 lib/modules/5.1.0-050100-lowlatency/kernel/crypto lib/modules/5.1.0-050100-lowlatency/kernel/crypto/crypto_simd.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/xor.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/cryptd.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/ecdh_generic.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/async_tx lib/modules/5.1.0-050100-lowlatency/kernel/crypto/async_tx/async_tx.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/async_tx/async_memcpy.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/async_tx/async_raid6_recov.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/async_tx/async_pq.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/async_tx/async_xor.ko lib/modules/5.1.0-050100-lowlatency/kernel/drivers/md/dm-crypt.ko lib/modules/5.1.0-050100-lowlatency/kernel/arch/x86/crypto lib/modules/5.1.0-050100-lowlatency/kernel/arch/x86/crypto/glue_helper.ko lib/modules/5.1.0-050100-lowlatency/kernel/arch/x86/crypto/aes-x86_64.ko lib/modules/5.1.0-050100-lowlatency/kernel/arch/x86/crypto/aesni-intel.ko scripts/local-bottom/cryptopensc scripts/local-block/cryptroot scripts/local-top/cryptroot scripts/local-top/cryptopensc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: cryptsetup stuck at loading initramfs Status in cryptsetup package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
