Feisty is not supported anymore.
** Changed in: initramfs-tools (Ubuntu)
Status: New = Invalid
--
initramfs scripts kill initial coldplug udev processing before devices needed
for root filesystem are loaded
https://bugs.launchpad.net/bugs/89366
You received this bug notification because
Confirmed here too.
My solution has been adding:
udevsettle --timeout=10
in /usr/share/initramfs-tools/init before line:
log_begin_msg Mounting root file system...
and then rebuild initrd with:
sudo update-initramfs -u -k all
I believe thi is the right way to go, as it guarantees that udev
Confirmed. My Ubuntu test box consists of all md devices and was unbootable
after the upgrade until I used the label trick. For those looking for direction:
1) Boot back up on a usable kernel. Due to the horrible bug with
update-initramfs wiping the old initrd images, you may need to boot from
I run into this bug yesterday when I upgraded my laptop from edgy to
feisty.
I have an encypted root filesystem (dm-crypt + LUKS) on /dev/sda3. The
initramfs hook script from cryptsetup tries to open /dev/sda3 before the
device has been created wich obvously fails so that the machine can't
boot.
After a little further investigation I can confirm my suspiscion: using
a LABEL specification rather than the standard md0 node allows the boot
process to complete successfully even if the sleep is removed from the
udev script.
--
initramfs scripts kill initial coldplug udev processing before
