LVM storage issue while starting container after core20 switch

[tomp (Thomas Parrott)]

Its likely you’ve been affected by the snap core20 switch.

Does your /dev/mapper/nvme-lxd exist on another LVM volume?

Please see:

LXD snap transitioning to core20 and losing i386 support

There have been a few issues caused by the switch to core20 which I thought would be worth documenting in case any body is affected: Core20 prevented LXD’s ability to detect and use the xtables firewall driver LXD supports two firewall drivers; xtables (iptables, ip6tables, ebtables and arptables), and nftables. LXD will detect the presence of the firewall commands available, as well as the rule sets already in use, and will pick what it thinks is the most appropriate firewall driver to use. …

and

LVM storage problem - all container stopped and doesn't start anymore after switch to core20

Hello, I have a huge problem: all containers stopped and doesn’t start anymore. When I try to start a container I have this error: Error: Failed preparing container for start: Failed to activate LVM logical volume "/dev/pool_0/containers_iceCast": Failed to run: lvchange --activate y --ignoreactivationskip /dev/pool_0/containers_iceCast: Volume group "pool_0" not found Cannot process volume group pool_0 But with vgs/lvs commands I see vg and lv volumes. Some one have experienced this kind …