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

[Phillip Susi]

Cryptsetup has to be done via script rather than udev rule since it has
to prompt for input, and udev rules can't do that.

I think just two things need done to fix this:

1) cryptsetup needs a failure hook
2) try_failure_hooks needs to continue trying all failure hooks rather than return as soon as one succeeds

This would allow the failure hooks to activate one or more degraded raid
arrays, and finally cryptsetup to unlock the volume.

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