Public bug reported:
Today I updated my hirsute packages which included an update to the
following lvm2 packages:
Unpacking liblvm2cmd2.03:amd64 (2.03.11-2ubuntu2) over (2.03.07-1ubuntu4)...
Unpacking lvm2 (2.03.11-2ubuntu2) over (2.03.07-1ubuntu4) ...
Unpacking dmeventd (2:1.02.175-2ubuntu2) over (2:1.02.167-1ubuntu4) ...
Immediately after the update I rebooted and noticed my hirsute
installation would no longer boot and dropped me into a busybox shell.
I was able to downgrade these packages to the previous version which restored
proper booting.
I'm using LVM + luks/cryptsetup so I'm not sure if the filesystem encryption is
related or not.
Also I went ahead and tested this on a clean hirsute installation using
the daily build on a KVM instance with UEFI + LVM + luks/cryptsetup and
as soon as the installation finished it fails to boot into Ubuntu on the
first try as it installs the lvm2 2.03.11-2ubuntu2 packages during
installation so this is an easily reproducible bug.
Regards
** Affects: lvm2 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Today I updated my hirsuite packages which included an update to the
following lvm2 packages:
- Unpacking liblvm2cmd2.03:amd64 (2.03.11-2ubuntu2) over (2.03.07-1ubuntu4) ...
+ Unpacking liblvm2cmd2.03:amd64 (2.03.11-2ubuntu2) over (2.03.07-1ubuntu4)...
Unpacking lvm2 (2.03.11-2ubuntu2) over (2.03.07-1ubuntu4) ...
Unpacking dmeventd (2:1.02.175-2ubuntu2) over (2:1.02.167-1ubuntu4) ...
Immediately after the update I rebooted and noticed my hirsuite
installation would no longer boot and dropped me into a busybox shell.
I was able to downgrade these packages to the previous version which restored
proper booting.
I'm using LVM + luks/cryptsetup so I'm not sure if the filesystem encryption
is related or not.
Also I went ahead and tested this on a clean hirsuite installation using
the daily build on a KVM instance with UEFI + LVM + luks/cryptsetup and
as soon as the installation finished it fails to boot into Ubuntu on the
first try as it installs the lvm2 2.03.11-2ubuntu2 packages during
installation so this is an easily reproducible bug.
Regards
** Description changed:
- Today I updated my hirsuite packages which included an update to the
+ Today I updated my hirsute packages which included an update to the
following lvm2 packages:
Unpacking liblvm2cmd2.03:amd64 (2.03.11-2ubuntu2) over (2.03.07-1ubuntu4)...
Unpacking lvm2 (2.03.11-2ubuntu2) over (2.03.07-1ubuntu4) ...
Unpacking dmeventd (2:1.02.175-2ubuntu2) over (2:1.02.167-1ubuntu4) ...
- Immediately after the update I rebooted and noticed my hirsuite
+ Immediately after the update I rebooted and noticed my hirsute
installation would no longer boot and dropped me into a busybox shell.
I was able to downgrade these packages to the previous version which restored
proper booting.
I'm using LVM + luks/cryptsetup so I'm not sure if the filesystem encryption
is related or not.
- Also I went ahead and tested this on a clean hirsuite installation using
+ Also I went ahead and tested this on a clean hirsute installation using
the daily build on a KVM instance with UEFI + LVM + luks/cryptsetup and
as soon as the installation finished it fails to boot into Ubuntu on the
first try as it installs the lvm2 2.03.11-2ubuntu2 packages during
installation so this is an easily reproducible bug.
Regards
--
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/1917563
Title:
lvm2 (2.03.11-2ubuntu2) hirsute causes failure to boot and drops to
busybox
Status in lvm2 package in Ubuntu:
New
Bug description:
Today I updated my hirsute packages which included an update to the
following lvm2 packages:
Unpacking liblvm2cmd2.03:amd64 (2.03.11-2ubuntu2) over (2.03.07-1ubuntu4)...
Unpacking lvm2 (2.03.11-2ubuntu2) over (2.03.07-1ubuntu4) ...
Unpacking dmeventd (2:1.02.175-2ubuntu2) over (2:1.02.167-1ubuntu4) ...
Immediately after the update I rebooted and noticed my hirsute
installation would no longer boot and dropped me into a busybox shell.
I was able to downgrade these packages to the previous version which restored
proper booting.
I'm using LVM + luks/cryptsetup so I'm not sure if the filesystem encryption
is related or not.
Also I went ahead and tested this on a clean hirsute installation
using the daily build on a KVM instance with UEFI + LVM +
luks/cryptsetup and as soon as the installation finished it fails to
boot into Ubuntu on the first try as it installs the lvm2
2.03.11-2ubuntu2 packages during installation so this is an easily
reproducible bug.
Regards
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917563/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
