Public bug reported:
After Ubuntu upgrade following problem occur.
One of the volumes in the libvirt volumegroup no longer has an lvm2
signature for some reason. Someone must have overwrote it.
However libvirt has been removed from /etc/fstab already, to prevent any
issues in booting.
Somehow this causes so much trouble with the multipather that even the
boot lun is not named as it was previously. (Persistence in naming is
lost)
/ gets mounted, but /boot fails to mount because of the change in naming, and
this is what is causing the rescue prompt.
I can successfully mount /boot by UUID instead.
While a corrupted volume is a corrupted volume, I would have expected
the multipather to handle it more gracefully and not impacted other LUNs
in this way.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-184392 severity-high
targetmilestone-inin1804
** Tags added: architecture-s39064 bugnameltc-184392 severity-high
targetmilestone-inin1804
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867620
Title:
Failure after Ubuntu upgrade - libvirt volumegroup no longer has an
lvm2 signature
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867620/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
