LVs in a volume group with missing PVs fail to auto-activate on boot, even if the missing PVs should not prevent activation of those LVs.

Issue

• LVM logical volumes (LVs) that are part of a volume group (VG) with one or more missing physical volumes (PVs) do not automatically activate on boot, leading to filesystem timeouts and boot failures, even though the missing PVs are not actually used for any logical volumes.
• The auto_activation_volume_list setting has not been configured to allow only specific VGs to auto-activate.
• The LVs in question are able to be activated manually with commands such as vgchange -ay or lvchange -ay.