On 28/08/12 11:17, Robie Basak wrote: > On Tue, Aug 28, 2012 at 08:42:26AM +0100, Dmitrijs Ledkovs wrote: >> On 28/08/12 06:38, Martin Pitt wrote: >>> * After that, booting fails because the generated grub configuration >>> hardcodes /dev/md0p1, but initramfs/kernel create it as /dev/md127p1. >>> It would be nice if grub/Ubiquity used UUIDs for the root partition >>> as usual; in the initramfs /dev/disks/by-uuid/... exists just fine. >>> >> >> Why mdadm started to generate md127 instead of md0, I don't know. And >> it's a bug I should look into. > > This sounds like this bug: a race between udev workers and mdadm: > > http://dev.bizo.com/2012/07/mdadm-device-or-resource-busy.html > https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1030354 >
While this is true, and I now have assigned this bug to myself, I am not sure how the two interacted during boot. At boot, udev is incrementally assembling md arrays on ubuntu. So why would it not create stable names? -- Regards, Dmitrijs.
signature.asc
Description: OpenPGP digital signature
-- ubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
