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

[ceg]

I believe the initramfs only sets up the rootfs, other partitions
(/home) are set up afterwards. If I remeber correct cryptsetup is called
by udev rules. In any case, that is the way it has to be, event driven,
to catch on upon (/home) devices appearing without polling loops and
sleep delays.

When I looked, I think bootwait, mdadm and cryptsetup where all looping
and sleeping in initramfs independently in whatever course they get
called. Therefore I suggested the watchdog timers I mentioned above and
in the wiki.

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