OK, I really appreciate that you want to fix this and I really want to help, but this has been driving me nuts. I can reproduce it *way too* reliably with a "normal" boot (i.e. it happens 8 times out of 10) but when trying to get a log it suddenly refused to happen :/ I started to think that the echo line added to the mdadm script caused a sufficient lag to avoid the trap and rebooted without this line, I could reproduce it and get a log at the first boot! Unfortunatly I messed somethings up and thus tryed to make a new one without much success.
Then I put the "echo running...." line back and I have tried again and again for half an hour to finally get one, but I forgot to put a ">>" instead of a ">" when redirecting udevd's output. I give up for now as I have been unable to reproduce it since (except twice with "normal" boot, but not willing to wait 3minutes...) so, here it is, I attach a tar.gz of the log I made, and I put my initramfs here: http://crfb.univ- mrs.fr/~naldi/initrd.img-2.6.20-13-generic What I did: boot with break=premount launch udevd & udevtrigger, check that the bug happened, collect some info to fix it: /scripts/local-top/mdadm lvm vgscan lvm vgchange -a y collect some more info mount /dev/sda1 on /mnt # an ext2 partition for /boot copy my log files here umount /mnt pkill udevd (sorry, I might have get nicer logs if I stopped it before, right ?) exit watch it finish booting ** Attachment added: "some log files" http://librarian.launchpad.net/7045516/aurelien_mdadmrace_logs.tgz -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
