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

[Phillip Susi]

mdadm is event driven via udev.  The special part in the initramfs is
the failure hook so that a degraded array will only be activated after a
timeout.  I'm not sure if we want to auto degrade arrays post boot, but
I suppose if we did, we could move that logic from the failure hook to
the udev rule.

What confuses me is cryptsetup.  I see that there is an upstart job that
appears to try and prompt for the password and unlock the device, but as
an upstart task, it has no stdin/out, so that prompt can't work.  After
the system goes multi user you can no longer do a console password
prompt.  If you want an interactive prompt at that point, you will need
something that can interact with the X desktop, and anything that does
that obviously isn't going in the initramfs.

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