As already mentioned in comment 10, we experienced the same bug at the end of 2011 and were hit by it in internal tests every few weeks.
After applying the mentioned change, it disappeared. Since somewhen in 2012, we're in the field with about hundred systems running Lucid with this patch and never ever saw the problem again. So probably applying the change to Lucid-updates would make sense? To make it easy for you, I also added our patch now. ** Patch added: "waiting for udev to settle before killing it" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/613273/+attachment/3505539/+files/usr-share-initramfs-tools-scripts-init-bottom-udev.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/613273 Title: run-init: nuking initramfs contents: directory not empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/613273/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
