XK0-006 Troubleshooting Practice Question
During boot, a Linux system displays a kernel panic with 'VFS: Unable to mount root fs on unknown-block(0,0)'. Which of the following is the most likely cause?
⚠ Common exam trap
Many exam-takers confuse post-boot configuration files like /etc/fstab with pre-boot requirements — candidates often assume any filesystem-related error must come from fstab, but fstab is irrelevant before the root filesystem is mounted.
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
✓
Corrupt initramfs missing a necessary kernel module for the root device
The error 'VFS: Unable to mount root fs on unknown-block(0,0)' occurs when the kernel cannot locate or access the root filesystem device. This typically happens because the initramfs (initial RAM filesystem) is corrupt or missing the kernel module (e.g., storage controller driver like ahci, virtio_blk, or LVM/dm modules) needed to detect and mount the root device. Without that module, the kernel has no way to translate the root= parameter into a usable block device, resulting in unknown-block(0,0).
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Incorrect time configuration in the BIOS
Why it's wrong here
A wrong BIOS clock shifts timestamps and can break TLS or logging, but the kernel still locates and mounts the root filesystem. The panic occurs before userspace, so time configuration is irrelevant. Correcting the clock is the right action when certificates appear expired or file timestamps are skewed, not when root cannot be mounted.
- ✓
Corrupt initramfs missing a necessary kernel module for the root device
Why this is correct
The kernel mounts the root filesystem using drivers supplied by the initramfs. If that image is corrupt or omits the storage or filesystem module, the root device cannot be mounted, producing exactly this unknown-block(0,0) panic during boot.
- ✗
The /etc/fstab file has an invalid filesystem type for the root partition
Why it's wrong here
The kernel mounts the root filesystem before /etc/fstab is consulted, so an invalid entry there cannot produce this panic; fstab governs later mounts. It is tempting because fstab lists filesystem types. Editing fstab is correct when a secondary mount such as /home fails, not the root device itself.
- ✗
A defective network cable
Why it's wrong here
The panic arises from the kernel being unable to locate or mount the root block device, entirely before networking is initialised. A defective cable causes link failures and unreachable hosts, not this message. Replacing the cable is correct when a machine boots but cannot reach the network, not when root mounting fails.
Go deeper
Related to this question
Learn chapter
Installing Linux and Package Management
Key term
Mount
Mounting is the process of making a file system or storage device accessible to a computer's operating system by attaching it to a specific directory in the existing directory tree.
Key term
LVM
LVM (Logical Volume Manager) is a storage management system that allows you to create, resize, and manage disk partitions flexibly without needing to repartition the physical disk.
About these practice questions
One of 781 original XK0-006 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 CompTIA exam blueprint
This XK0-006 practice question is part of Courseiva's free CompTIA 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 XK0-006 exam.