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

[Phillip Susi]

Can't the udev rule fork and let the child wait for the timeout, then
activate the array degraded?

I think the source of my confusion is that upstart is bluring the line
between udev, which was designed to do event driven processing in
response to hardware detection, and conventional sysvinit, which was
designed to run things at startup.  Doing this sort of thing with an
upstart job makes it dependent on upstart, which means we won't be able
to use systemd or sysvinit as alternatives ( which I think makes it a
deal breaker for Debian doesn't it? ).

If possible, it would be better to find a way for this processing to be
kicked off via udev without depending on upstart, either for later
system init, or especially in the initramfs, where adding it would have
significant overhead.

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