apt autoremove removes cryptsetup-initramfs which causes boot to drop to initramfs shell on machine with LVM and full disk encryption

Bug #1864293 reported by Neil McPhail
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubuntu-mate-meta (Ubuntu)
Fix Released
High
Martin Wimpress 

Bug Description

Ubuntu Mate 20.04 dev release, upgraded from 19.10. LVM/disk encrypion had been set up from the 19.10 installer and had been working perfectly.

Today, when I try to boot, the splash screen stalls at the throbber and doesn't open a prompt for my encryption key. After a minute or so it drops to the initramfs shell. Rebooting without "silent splash" on the cmdline shows that `/dev/mapper/vgubuntu--mate-root` cannot be found, and running `ls /dev/mapper` outputs only `control`.

Rebooting with the 5.4.0-12 kernel works without any problems.

I've added `mitigations=off` to my default boot flags some time ago, if that's relevant?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-14-generic 5.4.0-14.17
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu17
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: neil 3193 F.... pulseaudio
CurrentDesktop: MATE
Date: Sat Feb 22 12:29:27 2020
InstallationDate: Installed on 2019-10-11 (133 days ago)
InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
MachineType: LENOVO 2325A39
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-12-generic N/A
 linux-backports-modules-5.4.0-12-generic N/A
 linux-firmware 1.186
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux-5.4
UpgradeStatus: Upgraded to focal on 2020-02-07 (15 days ago)
dmi.bios.date: 06/19/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ETB3WW (2.73 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2325A39
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG2ETB3WW(2.73):bd06/19/2018:svnLENOVO:pn2325A39:pvrThinkPadX230:rvnLENOVO:rn2325A39:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230
dmi.product.name: 2325A39
dmi.product.sku: LENOVO_MT_2325
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

Revision history for this message
Neil McPhail (njmcphail) wrote :
Neil McPhail (njmcphail)
summary: - Booting 5.4.0-14 drops to initramfs shell on machine with LVM and fudd
+ Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full
disk encryption
Neil McPhail (njmcphail)
summary: - Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full
- disk encryption
+ apt autoremove removes cryptsetup-initramfs which causes boot to drop to
+ initramfs shell on machine with LVM and full disk encryption
no longer affects: linux-5.4 (Ubuntu)
Revision history for this message
Neil McPhail (njmcphail) wrote :

This looks to be a problem with `apt autoremove` removing cryptsetup-initramfs. Please see https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1862215 and https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1864360 for context. i have been advised that my problem is not a duplicate of these bugs. Apt log appended. Please see the `autoremove` actions on 22nd February.

Neil McPhail (njmcphail)
tags: added: champagne
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in cryptsetup (Ubuntu):
status: New → Confirmed
Steve Langasek (vorlon)
Changed in cryptsetup (Ubuntu):
assignee: nobody → Julian Andres Klode (juliank)
Revision history for this message
Julian Andres Klode (juliank) wrote :

This is a regression in ubuntu-mate-meta which earlier added cryptsetup as a dependency to workaround a bug in ubiquity/livecd-rootfs.

Now that depends got removed, causing the package to become automatically installed.

It could run apt-mark manual cryptsetup in preinst or somewhere to reduce the chance of that happening / making it impossible for users upgrading from down (focal to focal is the real issue, really, as users might do upgrade --autoremove).

affects: cryptsetup (Ubuntu) → ubuntu-mate-meta (Ubuntu)
Changed in ubuntu-mate-meta (Ubuntu):
assignee: Julian Andres Klode (juliank) → nobody
status: Confirmed → Triaged
Changed in ubuntu-mate-meta (Ubuntu):
importance: Undecided → High
assignee: nobody → Martin Wimpress (flexiondotorg)
status: Triaged → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-mate-meta - 1.262

---------------
ubuntu-mate-meta (1.262) focal; urgency=medium

  * Refreshed dependencies
  * Added cryptsetup to core, desktop (LP: #1864293)

 -- Martin Wimpress <email address hidden> Thu, 02 Apr 2020 17:56:51 +0100

Changed in ubuntu-mate-meta (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.