[Bug 1829620] Re: cryptsetup stuck at loading initramfs

[TJ]

Mark

I just realised your report isn't about cryptsetup being the problem and
you never reach the initialramfs shell.

Your report that the last thing you see is "my system gets stuck at
"Booting, Loading initramfs" tells us the kernel isn't starting. Those
messages come from GRUB when it loads the kernel and initrd.img into
memory.

I'm wondering if the recent Intel microcode updates and related kernel
patches could be responsible? Can you tell us what CPU the system has?

$ cat /proc/cpuinfo

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup 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