Bug#931628: lvm2: volumes not activated at boot after upgrade from stretch to buster

[Phil Reynolds]

The problem is caused by scripts-top/lvm2 only activating volumes if
called with one of fe[0-9]*, /dev/root, /dev/mapper/* or /dev/*/*. If
called with a UUID, it doesn't work. By using /dev/mapper references in
fstab, I now have it working, but I am not sure whether this really is
the best thing security-wise.