[Bug 2044785] [NEW] cryptsetup unlocking at boot time unreliable

[Hadmut Danisch]

Public bug reported:

Hi,

I'm having the following configuration on one of my machines:

- encrypted boot/root device on SSD (Lubuntu)
- three hard disks, luks-encrypted for zfs, linked to the root device by /etc/crypttab:

pool1a     UUID=... sde3_crypt luks,keyscript=/lib/cryptsetup/scripts/decrypt_derived
pool1b     UUID=... sde3_crypt luks,keyscript=/lib/cryptsetup/scripts/decrypt_derived
pool1c     UUID=... sde3_crypt luks,keyscript=/lib/cryptsetup/scripts/decrypt_derived

to have them opened at boot time with a single entering of the root
partition password, which was working well for ages, at least since the
last fresh installation of the machine (ubuntu 18.04), actually longer.


Since 23.04 this doesn't work realiably anymore. 

At boot time, the machine asks me for separate passwords for one or two
of these disks, *but not always the same*, not even always for the same
number. One or two, in rare cases all three. It seems as if the machine
randomly picks one or two of these disks to ask for the password.

Maybe it is some race condition, as if all three unlocks try to happen
at the same time and block each other from working.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: cryptsetup 2:2.6.1-4ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: LXQt
Date: Mon Nov 27 13:19:43 2023
InstallationDate: Installed on 2018-04-28 (2039 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: cryptsetup
UpgradeStatus: Upgraded to mantic on 2023-11-09 (18 days ago)
cmdline: BOOT_IMAGE=/vmlinuz-6.5.0-13-generic root=UUID=4b98dd7c-f5bf-45ad-9fa6-21d3fd5c3447 ro quiet nosplash

** Affects: cryptsetup (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug mantic

-- 
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/2044785

Title:
  cryptsetup unlocking at boot time unreliable

Status in cryptsetup package in Ubuntu:
  New

Bug description:
  Hi,

  I'm having the following configuration on one of my machines:

  - encrypted boot/root device on SSD (Lubuntu)
  - three hard disks, luks-encrypted for zfs, linked to the root device by /etc/crypttab:

  pool1a     UUID=... sde3_crypt luks,keyscript=/lib/cryptsetup/scripts/decrypt_derived
  pool1b     UUID=... sde3_crypt luks,keyscript=/lib/cryptsetup/scripts/decrypt_derived
  pool1c     UUID=... sde3_crypt luks,keyscript=/lib/cryptsetup/scripts/decrypt_derived

  to have them opened at boot time with a single entering of the root
  partition password, which was working well for ages, at least since
  the last fresh installation of the machine (ubuntu 18.04), actually
  longer.

  
  Since 23.04 this doesn't work realiably anymore. 

  At boot time, the machine asks me for separate passwords for one or
  two of these disks, *but not always the same*, not even always for the
  same number. One or two, in rare cases all three. It seems as if the
  machine randomly picks one or two of these disks to ask for the
  password.

  Maybe it is some race condition, as if all three unlocks try to happen
  at the same time and block each other from working.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: cryptsetup 2:2.6.1-4ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
  Uname: Linux 6.5.0-13-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Mon Nov 27 13:19:43 2023
  InstallationDate: Installed on 2018-04-28 (2039 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: cryptsetup
  UpgradeStatus: Upgraded to mantic on 2023-11-09 (18 days ago)
  cmdline: BOOT_IMAGE=/vmlinuz-6.5.0-13-generic root=UUID=4b98dd7c-f5bf-45ad-9fa6-21d3fd5c3447 ro quiet nosplash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2044785/+subscriptions