server will not boot after updating lvm2 package

[Steve Buehrle]

After updating lvm2 from 2.02.176-4.1ubuntu3.18.04.1 to 2.02.176-4.1ubuntu3.18.04.2, server will not boot.

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
2.02.176-4.1ubuntu3.18.04.2

3) What you expected to happen
I expect the server to boot.

4) What happened instead
The server hangs at boot.

As the server will not boot, I can not provide any logs. I can only provide a screen captures of the boot failure messages.

[Steve Buehrle (sbuehrle)]

uploading log file captured from serial port.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Pablo SEMINARIO (pabluk)]

Hi,

Same issue here, after a system upgrade today my computer was not able to boot anymore. On my

It was stuck with the following message:

WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Volume group "ubuntu-vg" not found Cannot process volume group ubuntu-vg

As workaround I downgraded the package from a chroot mount via an USB key running:

apt-get install lvm2=2.02.176-4.1ubuntu3 liblvm2app2.2=2.02.176-4.1ubuntu3 liblvm2cmd2.02=2.02.176-4.1ubuntu3

and it was able to boot again.

Here's the output of /var/log/dpkg.log:

2020-02-07 12:20:00 upgrade liblvm2cmd2.02:amd64 2.02.176-4.1ubuntu3.18.04.1 2.02.176-4.1ubuntu3.18.04.2
2020-02-07 12:20:20 upgrade liblvm2app2.2:amd64 2.02.176-4.1ubuntu3.18.04.1 2.02.176-4.1ubuntu3.18.04.2
2020-02-07 12:20:36 upgrade lvm2:amd64 2.02.176-4.1ubuntu3.18.04.1 2.02.176-4.1ubuntu3.18.04.2

2020-02-07 15:07:06 upgrade liblvm2app2.2:amd64 2.02.176-4.1ubuntu3.18.04.2 2.02.176-4.1ubuntu3
2020-02-07 15:07:07 upgrade liblvm2cmd2.02:amd64 2.02.176-4.1ubuntu3.18.04.2 2.02.176-4.1ubuntu3
2020-02-07 15:07:07 upgrade lvm2:amd64 2.02.176-4.1ubuntu3.18.04.2 2.02.176-4.1ubuntu3

Please don't hesitate to ask for more details.

Best,

[Steve Dodd (anarchetic)]

Just reported my own bug #1870783 - my server appears to hang (without above message), but eventually successfully boots after ~ 180 secs.

[Steve Dodd (anarchetic)]

This has just bitten me again on yet another machine - is it ever going to be fixed? If it helps I suspect it's something to do with having snapshots kicking around ..

[Steve Dodd (anarchetic)]

This has just happened on yet another machine. It seems to occur if there's a snapshot of root volume in existence? Any chance of a fix?