The last udev event shown in the failure case is this one: UDEV [3.735566] change /devices/virtual/block/dm-0 (block) UDEV_LOG=3 ACTION=change DEVPATH=/devices/virtual/block/dm-0 SUBSYSTEM=block DM_COOKIE=4228816 DEVNAME=/dev/dm-0 DEVTYPE=disk SEQNUM=1092 DM_UDEV_PRIMARY_SOURCE_FLAG=1 DM_NAME=test--vg-test--lv DM_UUID=LVM-4iWtHXttRCwYKe6cxdfiFUSSU9pFQ9Zelj82pgIWg6GreSTESCmwv43yf6Nrf5s2 DM_SUSPENDED=0 DM_UDEV_RULES=1 DM_VG_NAME=test-vg DM_LV_NAME=test-lv DEVLINKS=/dev/mapper/test--vg-test--lv /dev/disk/by-id/dm-name-test--vg-test--lv /dev/disk/by-id/dm-uuid-LVM-4iWtHXttRCwYKe6cxdfiFUSSU9pFQ9Zelj82pgIWg6GreSTESCmwv43yf6Nrf5s2 /dev/test-vg/test-lv MAJOR=252 MINOR=0
So that points to an lvm problem in this case, at least. I also notice a difference in this event - DM_SUSPENDED=0 vs. =1: UDEV [3.709786] add /devices/virtual/block/dm-0 (block) UDEV_LOG=3 ACTION=add DEVPATH=/devices/virtual/block/dm-0 SUBSYSTEM=block DEVNAME=/dev/dm-0 DEVTYPE=disk SEQNUM=1091 DM_SUSPENDED=0 DM_UDEV_RULES=1 MAJOR=252 MINOR=0 DEVLINKS=/dev/disk/by-id/dm-name- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818177 Title: boot failures caused by udev race To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/818177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
