Just checked that the same applies for encrypted non-rootfilesystems, too. (/etc/init.d/cryptdisks*) If for example external disks are slow crypdisk fails.
Since md and lvm devices are set up by udev: init.d/cryptdisk-early and cryptdisks (or just cryptdisk.functions) need to contain a timeout loop checking for their source device before failing.
Or better: If the cryptsetup can done by udev rules. (Maybe udev rules that are created on the fly by the boot script with the help of crypttab and a raw signature of the device?)
Just checked that the same applies for encrypted non-rootfilesys tems, too. (/etc/init. d/cryptdisks* ) If for example external disks are slow crypdisk fails.
Since md and lvm devices are set up by udev: init.d/ cryptdisk- early and cryptdisks (or just cryptdisk. functions) need to contain a timeout loop checking for their source device before failing.
Or better: If the cryptsetup can done by udev rules. (Maybe udev rules that are created on the fly by the boot script with the help of crypttab and a raw signature of the device?)