On Fri, Jan 18, 2019 at 03:16:26AM +0100, Andreas Bombe wrote: > This has worked for all these years until the update, which rejects the > VG with system ID without advance warning during package upgrade. Systems > may become unbootable after upgrade if these VGs contain filesystems > that are mounted in /etc/fstab. [...] > The only way to get access was to set global/system_id_source = > "lvmlocal" and set local/system_id to the affected VG's system ID.
I also ran into this on upgrading from stretch to buster. Fortunately I was keeping enough of an eye on console output from the upgrade that I was able to find this bug and I worked around it as you describe here. However, I forgot to update the initramfs after doing so, so I ended up having to sed /etc/lvm/lvm.conf and /etc/lvm/lvmlocal.conf in the initramfs anyway to get the system booting; once I got back into the system and ran "update-initramfs -u", a reboot worked fine. I mention this mainly in case anyone in the same situation finds this bug and might find it helpful. -- Colin Watson [cjwat...@debian.org]
