Courseiva
Troubleshooting →hardMultiple Choice

XK0-006 Troubleshooting Practice Question

During boot, a Linux system displays a kernel panic indicating 'not syncing: VFS: Unable to mount root fs on unknown-block(0,0)'. Which of the following is the most likely cause?

⚠ Common exam trap

Candidates often confuse a 'dirty filesystem' error with the 'unknown-block(0,0)' message; the latter is specifically about the kernel's inability to find the root device due to missing drivers 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

✓

Missing or corrupt initramfs

The error 'VFS: Unable to mount root fs on unknown-block(0,0)' indicates that the kernel cannot locate or access the root filesystem. This is most commonly caused by a missing or corrupt initramfs (initial RAM filesystem), which contains the necessary drivers and modules to mount the root filesystem. Without a valid initramfs, the kernel has no way to load storage drivers (e.g., for SATA, NVMe, or LVM) and thus fails to mount the root device.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Network configuration error

    Why it's wrong here

    The panic occurs before any network stack initialises, so network settings cannot produce an unknown-block root mount failure. It is tempting because misconfigured interfaces break remote access, but that scenario yields different errors after boot completes.

  • ✗

    A failed filesystem check due to dirty file system

    Why it's wrong here

    A dirty filesystem triggers fsck repair or a recovery shell, not an unknown-block(0,0) panic; the kernel cannot even locate the root device. It is tempting because filesystem faults do halt booting, but they surface after the root device is identified.

  • ✗

    Incorrect GRUB timeout value

    Why it's wrong here

    GRUB timeout only controls how long the menu waits before booting the default entry, so it cannot cause an unknown-block root mount failure. It is tempting when booting stalls at the menu, but that symptom differs from a kernel panic.

  • ✓

    Missing or corrupt initramfs

    Why this is correct

    The kernel mounts the root filesystem using drivers loaded from the initramfs. If that image is missing or corrupt, the required storage driver never loads, producing the unknown-block(0,0) panic. A missing or corrupt initramfs is therefore the likely cause.

About these practice questions

Courseiva writes every XK0-006 question from scratch — 781 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

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.