Boot fails with newer kernel

[Eugen]

I get a
"cryptsetup: Waiting for encrypted source device UUID=<UID>"

message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45
and then nothing happens

pressing ESC displays
"Volume group "vgubuntu" not found
Cannot process volume group vgubuntu"

System was dm-crypt/LUKS encrypted at installation

kernel 5.4.0-42 still works

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Tue Sep 8 16:41:34 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset ---
InstallationDate: Installed on 2019-10-18 (326 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: eugen 1907 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-10-18 (332 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20Q7001CGE
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-42-generic N/A
 linux-backports-modules-5.4.0-42-generic N/A
 linux-firmware 1.187.3
Tags: focal
Uname: Linux 5.4.0-42-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 03/24/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: R0ZET40W (1.18 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q7001CGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L590
dmi.product.name: 20Q7001CGE
dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590
dmi.product.version: ThinkPad L590
dmi.sys.vendor: LENOVO

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD). You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM. You might also retry your installation with new media. In the event that is is not in fact an error with your installation media please set the bug's status back to New. Thanks and good luck!

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Eugen (netzwerkdude)]

it has nothing to do with the installation media - the system was setup with 1910 and upgraded to 2004 - was running fine ever since, the problem is with the mentioned kernels: not booting, no real error message

[Eugen (netzwerkdude)]

after the update today I get a Initramfs unpacking failed: decoding failed

[Eugen (netzwerkdude)]

But I get the message with all kernels, 5.4.0-42 is still the only bootable

[Eugen (netzwerkdude)]

I can gladly post more config or log files, just need to know which of them

[Paul White (paulw2u)]

Eugen, normally the kernel bot posts the following text but it hasn't done so as the bug report has a status of 'Incomplete' and was initially filed against the installer rather than the kernel:

---
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

  apport-collect 1894860

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
---

Make sure you update the status even if you can't run the 'apport-collect' command.

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

apport information

[Eugen (netzwerkdude)]

okay, here you go, done both, hopefully you guys can work with the provided info

[Calvin (calvin8923789234789)]

I can confirm I'm experiencing the same problem.

[Calvin (calvin8923789234789)]

The happens even with a fresh install. This is also mentioned in https://askubuntu.com/questions/1274460/cryptsetup-ubuntu-20-04-no-longer-asks-for-my-password

[Anton (catastrofe)]

Kernel update to 5.4.0-48 fixed issue for me. What about you, Eugen?

[Eugen (netzwerkdude)]

I was a few weeks away from work, updated now to 5.4.0-51 - the problem seems fixed now

[K. (kar-bo)]

The problem appeared again for 5.11.0-25.27~20.04.1.
Works fine on 5.8.0-63.71~20.04.1