[Bug 1992371] [NEW] partition detection breaks after upgrade to 22.04

[Daniel Golle]

Public bug reported:

After upgrade to 22.04 the partitions on the fakeraid (Intel Storage
Matrix) device mapper node are no longer detected by the initramfs. This
results in the system hanging waiting for the LUKS encrypted device is a
partition on the fakeraid array, containing LVM2 volumes for rootfs and
swap/hibernate.

When being dropped into (initramfs) busybox I can get the system to boot
by running:

kpartx -a /dev/mapper/${longnameoffakeraidvolume}
cryptsetup luksOpen /dev/mapper/${longnameoffakeraidvolume}3
lvm pvs
lvm vgs
lvm lvs
lvm lvchange -a y ubuntuvg
exit

Ironically the system then asks me again to enter the password even
though the volume has already been unlocked.

I suppose that a call to 'kpartx' is missing somewhere in the script-
hooks for the initramfs.

The problem is also being discussed here:
https://unix.stackexchange.com/questions/709184/fakeraid-partition-missing-not-mapped-as-a-device-on-boot-after-upgrade-to-ubu

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


** Tags: dmraid fakeraid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dmraid in Ubuntu.
https://bugs.launchpad.net/bugs/1992371

Title:
  partition detection breaks after upgrade to 22.04

Status in dmraid package in Ubuntu:
  New

Bug description:
  After upgrade to 22.04 the partitions on the fakeraid (Intel Storage
  Matrix) device mapper node are no longer detected by the initramfs.
  This results in the system hanging waiting for the LUKS encrypted
  device is a partition on the fakeraid array, containing LVM2 volumes
  for rootfs and swap/hibernate.

  When being dropped into (initramfs) busybox I can get the system to
  boot by running:

  kpartx -a /dev/mapper/${longnameoffakeraidvolume}
  cryptsetup luksOpen /dev/mapper/${longnameoffakeraidvolume}3
  lvm pvs
  lvm vgs
  lvm lvs
  lvm lvchange -a y ubuntuvg
  exit

  Ironically the system then asks me again to enter the password even
  though the volume has already been unlocked.

  I suppose that a call to 'kpartx' is missing somewhere in the script-
  hooks for the initramfs.

  The problem is also being discussed here:
  https://unix.stackexchange.com/questions/709184/fakeraid-partition-missing-not-mapped-as-a-device-on-boot-after-upgrade-to-ubu

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