Comment 2 for bug 1349986
Revision history for this message
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
------- Comment From <email address hidden> 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/
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/
/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.