Howto:
https://wiki.ubuntuusers.de/Howto/Ubuntu_14.04_lvm_%C3%BCber_multipath_bootet_nicht_mehr/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1480399
Title:
LVM over
Lösung: https://forum.ubuntuusers.de/topic/ubuntu-trusty-lvm-ueber-
multipath-bootet-nicht/#post-8025308
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1480399
Title:
LVM
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided = High
** Changed in: multipath-tools (Ubuntu)
Status: New = Triaged
--
You received this bug notification because
** Attachment added: boot.log
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1480399/+attachment/4437052/+files/boot.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
Additional information. Output of multipath -v4 (as opposed to -v3)
shows that the ioctl reload can't happen because something else already
has a lock on it. I will need to dig in some more to verify whether that
really is LVM, and how to correct this.
Shipping the wwids file from multipath
Tried to extract as much information as possible from this system while
in the recovery console.
Note, this does not happen at all when installing directly to the
multipath device, only with LVM on top of multipath.
** Attachment added: typescript
