Hi Fabio, That deb seems to work fine for me (reporter of 68888); some comments:
1) The /etc/mdadm/mdadm.conf you create in the initrd is now very different from the mdadm.conf you would find in your running system - perhaps it should have a different name (mdadm.uuids ?) (Incidentally that is a wonderful sed line, I think I've managed to understand it all except for the '!' near the start of the first pattern) 2) I think it is actually just relying on finding at least one device out of each RAID - we seem to have a choice; ideally we would wait for all the elements of a RAID to get consistency, but if one of the devices has died what do we want to do? For a RAID5 we would want most of the devices to be there just to be able to get / up, and if the devices are on different controllers then there is no guarentee that one won't be a few seconds behind the other. 3) In the non-quiet case can you add a 'waiting for UUID's' and then list all the UUIDs in both the initial begin message and everytime we find one? 4) Why do you redirect errors from the modprobe to /dev/null? Wouldn't we want to know about the errors? -- mdadm causes boot to hang for 4 minutes https://launchpad.net/bugs/67299 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
