Tonight I upgraded to Bionic. The upgrade was fraught with problems, mainly due to a mixture of PAM and Postgresql where configuring postgresql asks for my PAM password and then ignores me completely forcing me to abort the upgrade mid configure.
My system appears to be mostly working now, but on boot I am told that lvmetad cannot be connected to and there follows a long delay while something is scanned. Disabling lvmetad removes the warning but not the delay.
Can anyone help? I see hints of other articles about this, but when I open the page in the search terms there is nothing useful there.
I see there was a bug reported in May about this which is now apparently fixed.
In my kernel log I see some lines like:
Sep 19 17:13:16 Shikamaru kernel: [ 1815.417699] lvm2-activation[22035]: segfault at d0 ip 00007fbc88f74856 sp 00007ffe47454da0 error 4 in liblvm2app.so.2.2[7fbc88f63000+101000]
I haven't seen these recently though and I am still getting the error.
Messing around following clues on the internet, I typed lvm lvs and got the following output that might give some more clues:
WARNING: Running as a non-root user. Functionality may be unavailable.
/run/lvm/lvmetad.socket: access failed: Permission denied
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.145 (2017-11-03) and kernel driver (unknown version).
However running it with sudo worked. Is it possible that the error during boot has a similar cause?
sudo apt install lvm2 --reinstallNothing should be removed.fsckon the drive. There is a bug report which appear to be the same issue: bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1767747 but as usual there's no solution.