** Changed in: lvm2 (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) =>
(unassigned)
** Changed in: ubuntu-z-systems
Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs
Sorry, I can't answer that for huge LVM installations.
But what I can say is that it is for s390x installations (multipath with LVMs
on top) a kind of immediately responding.
One thought is to check/do this for example at the end of the dist-
upgrade process, where a potential delay wouldn't be a
> So one solution to this would be to run "vgck --updatemetadata" on
each vg in postinst... would there be downside to that?
how slow is it on very very large LVMs? Is it distructive? Maybe
something to check with devops-y people, like I.S. / bootstack?
--
You received this bug notification beca
** Changed in: lvm2 (Ubuntu Focal)
Milestone: ubuntu-20.04.2 => focal-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874381
Title:
LVM device unavailable after 18.04 to 20.04 upgrade Tim
** Changed in: lvm2 (Ubuntu Focal)
Milestone: ubuntu-20.04.1 => ubuntu-20.04.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874381
Title:
LVM device unavailable after 18.04 to 20.04 upgrade Ti
** Tags added: fr-81
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874381
Title:
LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting
for device /dev/mapper/s5lp8--v g-home
To m
Hello, please see
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887964
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874381
Title:
LVM device unavailable after 18.04 to 20.04 upgrade Timed out
So one solution to this would be to run "vgck --updatemetadata" on each
vg in postinst... would there be downside to that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874381
Title:
LVM device una
I redeployed the system where this failures was original observed and recreated
the issue.
Running 'sudo vgck --updatemetadata s5lp8-vg' did work around this bug, when
run after the upgrade but prior to the reboot.
Here is the vgdisplay output requested by Steve:
ubuntu@s5lp8:~$ sudo vgdisplay
On Fri, Jun 05, 2020 at 09:38:35AM -, veribaka wrote:
> Is there a time frame to consider that the original reporter will not be
> returning to this discussion?
>
> Should I open my own bug report with my logs?
Please do open your own bug report with the relevant log files and make
a comment
Is there a time frame to consider that the original reporter will not be
returning to this discussion?
Should I open my own bug report with my logs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18743
awaiting feedback from the original reporter to confirm that these
particular commands are applicable to his install.
** Changed in: lvm2 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Reporting back:
"sudo vgck -t vg" reports that no changes would be made, it seems to be
looking in /dev/sda rather than /dev/nvme0n1.
"sudo vgscan" first reports that /dev/sda open failed and then
successfully detects the vg using metadata type lvm2.
--
You received this bug notification becaus
You need to either execute these commands after upgrade and _before_
rebooting or chroot from a LiveUSB boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874381
Title:
LVM device unavailable afte
I too tried to upgrade from 18.04 and ended up with a busybox, Ubuntu
not finding my vg. Not sure how to enter those commands from a busybox
Steve.
Re-imaging the device with 18.04 for the time being.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Tags added: id-5ec6a06d9ddd891b690ef2e4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874381
Title:
LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting
for device /dev/mapper
John, are you able to confirm that a 'sudo vgck --updatemetadata
s5lp8-vg' fixes this for you?
Also, before running that command, can you post the output of 'sudo
vgdisplay' on this system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
You might also want to try 'sudo vgck -t s5lp8-vg' first before
committing changes with --updatemetadata.
** Changed in: lvm2 (Ubuntu Focal)
Milestone: None => ubuntu-20.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
** Package changed: ubuntu-release-upgrader (Ubuntu) => lvm2 (Ubuntu)
** Tags removed: rls-ff-incoming
** Also affects: lvm2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: lvm2 (Ubuntu Focal)
Status: New => Confirmed
** Changed in: lvm2 (Ubuntu Focal)
Import
** Changed in: ubuntu-z-systems
Status: New => Confirmed
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Tags removed: installer
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
** Chang
Ok, copying my workarounds here and closing the other report:
Volume Group metadata had to be upgraded manually with
vgck --updatemetadata yourvgname
The VG name was somehow changed from lvm-name to just name and I had to
edit /etc/crypttab and update-initramfs -u -k all
Also cryptsetup-initram
** Tags added: installer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874381
Title:
LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting
for device /dev/mapper/s5lp8--v g-home
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874381
Title:
LVM device unavailable after 18.04 to 20.04 upgrade Time
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874
See https://bugs.launchpad.net/bugs/1877473 for workarounds. While this
report was first I was able to provide workarounds. Would you agree to
mark this bug as a duplicate, please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874381
Title:
LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting
for device /dev/mapper/s5lp8--v g-
** Also affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874381
Title:
LVM device unavailable after 18.04 to 20.04
27 matches
Mail list logo
