LFCS Storage Management Practice Question
An administrator is troubleshooting a server where the root filesystem is on an LVM logical volume. The system fails to boot and drops to an initramfs prompt with the error 'Volume group "vg_root" not found'. The administrator verifies that the physical volumes are present and the volume group exists when booting from a rescue disk. Which action is most likely to resolve the boot issue?
⚠ Common exam trap
The trap here is thinking that manually activating the volume group from the initramfs prompt is a permanent fix, when it only temporarily bypasses the real issue of missing LVM support in the initramfs.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Recreate the initramfs with the appropriate LVM configuration and modules included.
The error indicates that the initramfs is not activating the volume group during early boot. This usually happens when the initramfs was built without the necessary LVM modules or configuration, or after a kernel update that did not include LVM support. Rebuilding the initramfs with the correct LVM configuration ensures the volume group is found and activated, allowing the system to boot.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Edit /etc/lvm/lvm.conf to set the 'locking_type' to 0 and rebuild the initramfs.
Why it's wrong here
Changing locking_type to 0 disables locking, which is dangerous and not related to the volume group not being found. This setting is typically used in clustered environments or for debugging, not for resolving missing volume groups during boot. The problem is that the initramfs lacks the necessary LVM configuration, not that locking is misconfigured.
- ✗
Run vgchange -ay vg_root from the initramfs prompt and then continue booting.
Why it's wrong here
Activating the volume group manually might allow the system to continue booting, but it does not fix the underlying issue that caused the volume group to be inactive at boot. If the initramfs is not including the necessary LVM metadata or modules, the problem will recur on next reboot. This is a temporary workaround, not a permanent solution.
- ✓
Recreate the initramfs with the appropriate LVM configuration and modules included.
Why this is correct
The error indicates that the initramfs cannot find the volume group, likely because the LVM configuration or modules are missing from the initramfs. Rebuilding the initramfs with the correct LVM support, such as using dracut or update-initramfs, will ensure that the volume group is activated during early boot. This resolves the root cause permanently.
- ✗
Add the volume group to /etc/fstab with the 'noauto' option to prevent automatic activation.
Why it's wrong here
The /etc/fstab file controls filesystem mounting, not volume group activation. Adding an entry with 'noauto' would prevent the root filesystem from being mounted automatically, worsening the problem. The issue is in the initramfs, not fstab. This action does not address the missing volume group during boot.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 406 original LFCS practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Linux Foundation exam blueprint
This LFCS practice question is part of Courseiva's free Linux Foundation certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the LFCS exam.