[Bug 251164] Re: boot impossible due to missing initramfs failure hook / event driven initramfs

[Phillip Susi]

If the udev rule calls cryptsetup, then it would be trying to prompt,
and so it can't do that.

What invokes cryptsetup in the normal system?  Don't you have to do it
by hand right now if you hot plug a luks disk?

The order doesn't have to match the setup as long as they keep being
called as long as any one indicates that it managed to take some
corrective action.

AFAICS, there is only one wait, and then it goes into failure hook mode.

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

Title:
  boot impossible due to missing initramfs failure hook / event driven
  initramfs

Status in “cryptsetup” package in Ubuntu:
  Triaged
Status in “mdadm” package in Ubuntu:
  Confirmed

Bug description:
  the cryptsetup package needs proper integration into the initramfs
  failure hooks

  The system must not assume a particular layered setup or sequence of
  appearance of (hotplug/udev/crypt/md/degraded-md/lvm) devices.

  It must be able to boot with any possible combination raid, lvm, crypt
  combination that the debian-installer can produce.

  
  Description of solution in comment #15

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