That last screen shot confirms it. The UUID link is not being created. That combined with the errors about /dev/dm-x make me think that there is a race condition causing udev to try accessing the dev node before the kernel has actually created it. Often times this just results in the inotify messages, but my guess is, that in your case udev is getting to the point where it runs blkid before the device node is ready so it fails to identify the UUID and create the link.
I'm going to try to dig more into this. ** Package changed: dmraid (Ubuntu) => udev (Ubuntu) ** Summary changed: - [LUCID, MAVERICK, NATTY] do not boot reliably on dmraid set + [LUCID, MAVERICK, NATTY] udev has a race condition with device mapper devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/631795 Title: [LUCID, MAVERICK, NATTY] udev has a race condition with device mapper devices -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
