The most likely cause is that the kernel lacks the driver for the storage controller. This error occurs because the kernel, during the boot process, cannot identify or communicate with the block device holding the root filesystem, specifically when it reports an unknown-block(0,0) identifier. The kernel requires a built-in or initramfs-loaded driver for the underlying storage hardware—such as SATA, NVMe, or SCSI controllers—to access the root partition; if that driver is missing or only available as an unloaded module, the mount fails and triggers a kernel panic. On the LPIC-2 exam, this scenario tests your understanding of the boot sequence, initramfs construction, and kernel module management, often appearing as a distractor where candidates mistakenly blame a corrupted filesystem or incorrect root= parameter. A common trap is forgetting that modern storage controllers need their drivers in the initramfs, not just compiled as modules. Memory tip: “No driver, no root—block(0,0) means the kernel can’t even see the drive.”
LPIC-2 Linux Kernel and System Startup Practice Question
This LPIC-2 practice question tests your understanding of linux kernel and system startup. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
During boot, the kernel panics with 'VFS: Unable to mount root fs on unknown-block(0,0)'. Which of the following is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The kernel lacks the driver for the storage controller.
The error 'VFS: Unable to mount root fs on unknown-block(0,0)' indicates the kernel cannot find a driver for the block device containing the root filesystem. This most commonly occurs when the kernel lacks the necessary storage controller driver (e.g., for SATA, NVMe, or SCSI controllers), often because the driver was built as a module and not included in the initramfs or compiled into the kernel.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
The kernel lacks the driver for the storage controller.
Why this is correct
Missing driver prevents accessing the root filesystem.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The kernel image is corrupted.
Why it's wrong here
Corrupted kernel would cause a different panic or fail to execute.
✗
The init process is missing.
Why it's wrong here
Init missing causes panic later, not VFS error.
✗
The root filesystem is formatted with an unsupported filesystem.
Why it's wrong here
Unsupported filesystem would show different error like 'unknown filesystem type'.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse a missing init process (which occurs after mounting) with a missing storage driver (which prevents mounting entirely), leading them to select option C when the error clearly indicates the root device itself is unrecognized.
Trap categories for this question
Command / output trap
Unsupported filesystem would show different error like 'unknown filesystem type'.
Detailed technical explanation
How to think about this question
Under the hood, 'unknown-block(0,0)' means the kernel's block layer could not associate a major/minor device number with any registered driver; major number 0 is reserved for uninitialized or unclaimed devices. In real-world scenarios, this often occurs when using a custom kernel without built-in support for the system's storage controller (e.g., AHCI, NVMe, or virtio), or when the initramfs lacks the required kernel module and the root= parameter points to a device that cannot be probed.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the LPIC-2 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Linux Kernel and System Startup — This question tests Linux Kernel and System Startup — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The kernel lacks the driver for the storage controller. — The error 'VFS: Unable to mount root fs on unknown-block(0,0)' indicates the kernel cannot find a driver for the block device containing the root filesystem. This most commonly occurs when the kernel lacks the necessary storage controller driver (e.g., for SATA, NVMe, or SCSI controllers), often because the driver was built as a module and not included in the initramfs or compiled into the kernel.
What should I do if I get this LPIC-2 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Refer to the exhibit. The system boots successfully, but the root filesystem is mounted as read-only even after the boot process completes. Which of the following is the most likely cause?
medium
✓ A.The kernel command line contains the 'ro' parameter, which remains in effect.
B.The root device /dev/mapper/vg-root does not exist.
C.The root filesystem is damaged and forces read-only mount.
D.SELinux is enforcing and prevents write access to the root filesystem.
Why A: The 'ro' parameter in the kernel command line instructs the kernel to mount the root filesystem as read-only during early boot. Even after the boot process completes, if no subsequent remount (e.g., via init scripts or systemd) is performed, the root filesystem remains read-only. This is the most direct and common cause of a root filesystem staying read-only after boot.
Last reviewed: Jun 11, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This LPIC-2 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-2 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.