Part 1 – Begin the recovery process
Answer:
vgcfgrestore vg01 -f /etc/lvm/archive/vg01_00001-810050352.vg
Part 2 – Continue the recovery process
Answer:
lvchange -ay /dev/vg01/lv01
Part 3 – Complete recovery and access data
Answer:
mount /dev/vg01/lv01 /important_data
This performance-based question tests LVM recovery, a critical System Management skill in CompTIA Linux+ V8. The scenario indicates that a logical volume was removed, but the underlying physical volume and volume group metadata still exist.
???? Part 1: Restoring Volume Group Metadata
The first screenshot shows that:
Physical volumes (pvdisplay, pvs) still exist
The logical volume is missing
/etc/lvm/archive/ contains archived VG metadata
Linux automatically stores backups of LVM metadata in /etc/lvm/archive whenever changes are made. The correct first step is to restore the volume group metadata using:
vgcfgrestore vg01 -f /etc/lvm/archive/vg01_00001-810050352.vg
This restores the logical volume definitions but does not activate them yet.
This is the only correct starting point in Linux+ V8 recovery workflows.
???? Part 2: Activating the Logical Volume
After metadata restoration:
The LV exists but is inactive
blkid shows the LV as TYPE= " LVM2_member "
The logical volume must be activated before it can be mounted:
lvchange -ay /dev/vg01/lv01
This makes the LV available under /dev/vg01/lv01.
Linux+ explicitly requires LV activation after recovery.
???? Part 3: Accessing the Data
The final output shows:
The filesystem type is xfs
The logical volume is now visible
Since there is no indication of filesystem corruption, no repair is required.
The correct final step is to mount the filesystem:
mount /dev/vg01/lv01 /important_data
This restores full access to the underlying data.
