Dear Maintainer,

`/usr/lib/udev/rules.d/69-lvm.rules` file expects completion of a volume group before activating it. While the logic behind this behaviour is pretty clear (we continue to enumerate physical volumes until the group gets completed at last), it kinda defeats the purpose of `activation/activation_mode` configuration option, which can allow activation of partially failed volumes. Say, in a case of a single failed physical volume of a RAID1 LV, the VG would never be "complete", so won't be activated, which (if this VG contains an FS accessed at boot time) usually leads to falling into init maintenance mode at boot. While in a case of a desktop PC it's usually not that hard to enter root password and give `vgchange -ay` command, in a case of unattended system this can be rather problematic.