Courseiva
System Architecture →mediumMultiple Choice

LPIC-1 System Architecture Practice Question

A Linux system fails to boot with the error: 'Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)'. What is the most likely cause?

⚠ Common exam trap

The LPIC-1 exam often tests the distinction between a missing root filesystem and a missing initrd, trapping candidates who assume the error means the root partition itself is absent, when in fact the kernel cannot access it due to missing drivers in the initrd.

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 incorrect initrd

The error 'VFS: Unable to mount root fs on unknown-block(0,0)' indicates the kernel cannot locate or access the root filesystem during boot. The most common cause is a missing or incorrect initrd (initial RAM disk) that contains the necessary drivers (e.g., for SCSI, SATA, or filesystem modules) to mount the root partition. Without a proper initrd, the kernel lacks the modules to access the storage device, resulting in this panic.

Answer analysis

Option-by-option breakdown

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

  • ✗

    Missing root filesystem

    Why it's wrong here

    A missing root filesystem means the device node or filesystem is absent, giving 'unknown-block(0,0)' only after the kernel cannot find the volume; the stem's panic arises from the kernel lacking the driver to mount it. Tempting because the message names the root filesystem, but it would be correct if the disk were detached.

  • ✗

    Corrupt kernel image

    Why it's wrong here

    A corrupt kernel image usually fails earlier with checksum or decompression errors, or panics before reaching VFS initialisation. It is tempting because the panic originates in the kernel, and would be correct if the boot loader reported an unreadable or invalid kernel file rather than an unmountable root filesystem.

  • ✗

    Damaged bootloader

    Why it's wrong here

    A damaged boot loader produces GRUB errors or drops to a rescue prompt before the kernel loads; the kernel here runs and panics itself. It is tempting because boot failures often trace to GRUB, and would be correct if the system never reached kernel startup or displayed a missing-stage error.

  • ✓

    Missing or incorrect initrd

    Why this is correct

    The kernel has mounted neither root nor initramfs, so it cannot load the storage driver needed to reach the root filesystem. A missing or mismatched initrd leaves the kernel without those modules, producing exactly this unknown-block(0,0) panic at boot.

Visual reference

Client Server SYN (seq=100) SYN-ACK (seq=200, ack=101) ACK (ack=201) Connection established — data transfer begins

About these practice questions

One of 402 original LPIC-1 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 →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This LPIC-1 practice question is part of Courseiva's free LPI 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 LPIC-1 exam.