Additional thoughts; As I'm no expert on the whole initramfs boot sequence I'm unsure about the total workings of timing of device scanning, mdadm + lvm2 routines and rootdelay.
Imho it should be something like this; init Device scanning | some scanning delay parameter (for slow devices) | init Mdadm routine | some mdadm delay parameter? (see #633024) | LVM2 routine | Checking and setting ROOT Again, I'm not too familiar with the current workings but I see these steps are currently running in a more parallel way to speed up the boot process, as the local-top init scripts are called right at the start of the local script. I've confirmed this by trying another method of fixing my problem, instead of my previous fix; Adding 'sleep 10' at the top of /scripts/local-top/mdadm also solves the problem (mdadm is then performed after device scanning) Is there a unifiable way of getting the timings right of all the scripts and still maintaining a quick bootprocess? If not, is it possible to add extra kernel boot options providing the delay options (avoiding manual tampering with the initrd)? Best regards, Jort Koopmans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
