Update: I installed 5.4.0-73 via update, grub config got updated but
after reboot only
5.4.0-72 (the broken one)
4.15
4.4 (the uninstalled one)
appeared in the grub menu. After "reparing" the grub update (see:
https://askubuntu.com/a/1207143), the machine boots into 5.4.0-73
without major
FYI: my system is quite old, I started with 8.04 server LTS and upgraded
since so my problems are rarely reproducible on systems that were
conceived later.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
So I upgraded from 18.04 LTS to 20.04 LTS too and found that the
installed 5.4 kernel panics complaining something about volume group. I
booted the 4.15 kernel wich put in a volume group warning too but at
least runs. After adding 8.8.8.8 to the resolv.conf the machine is
almost ready to work with
I've encountered a similar issue for a root volume group w/ encryption.
How can I try the same workaround as @veribaka starting from a busybox
prompt? In busybox /etc/crypttab does not exist.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
After more testing, it seems the file is not read because the line in
/etc/crypttab doesn't have end of line.
This returns empty:
hexdump /etc/crypttab | grep 0a
This adds end of line, fixing the problem:
sudo sed -i -e '$a\' /etc/crypttab
--
You received this bug notification because you are
Small update. After several tests, I found that if I duplicate the
encrypted block device configuration line in /etc/crypttab, the upgrade
is successful.
I.e., in my case:
nvme0n1p3_crypt UUID=c9ffc13a-cad1-49a2-83eb-fb9002b3ebff none luks
changes to
nvme0n1p3_crypt
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
exactly the same happened here. Help would be much appreciated!
thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1887964
Title:
VG unavailable after upgrade from 18.04
I thought so too initially, but the proposed solution doesn't work in my
case, and also I get a different error message booting up.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
However, this could even be marked as duplicate of LP 1874381 ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1887964
Title:
VG unavailable after upgrade from 18.04 to
I'm changing this ticket to lvm2 and focal, removing the currently marked as
affected "Ubuntu on IBM z Systems" project, since the logs show that they come
from a amd64 system.
Nevertheless, the referenced LP 1874381, was on s390x.
** Project changed: ubuntu-z-systems => lvm2 (Ubuntu)
** Also
12 matches
Mail list logo
