------- Comment From [email protected] 2015-02-02 16:26 EDT------- I will expand a little more on what I found out about the bug, and where it likely is.
As I described in the initial report, the UUID device that is used by the scripts to lookup for the rootfs is pointing out to a SCSI partition device. For example: /dev/disk/by-uuid/78c02bb3-9623-4fe0-b283-22f8f3fe8faa -> /dev/sda2 multipath daemon has already detected the multipath setup and created a mapping that uses sda, and creates linear mappings to the partitions using kpartx. /dev/mapper/mpathap2 -> ../dm-2 /dev/mapper/mpatha -> ../dm-0 The UUID device should point to dm-2 or mpathap2 instead of pointing out to sda2. This is needed because the mpath mapping will grab the device and that will prevent a filesystem to be mounted directly on it. The UUID device is created by udev. udev is creating that during the device probe. When the multipath partition is created, udev reads the same filesystem UUID there, but can't create the link because it already exists. What needs to be done is removing that link when multipath is detected or sda2 is removed from the system, or forcing the link creation when it already exists. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349986 Title: Ubuntu fails to boot with multipath To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1349986/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
