VFS: Unable to Mount Root FS on Unknown-Block — Causes & Fix
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?
Quick Answer
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.”
⚠ Common exam trap
It's easy for candidates to 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.
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
✓
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.
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.
- ✗
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'.
Go deeper
Related to this question
About these practice questions
This LPIC-2 question is part of Courseiva's 507-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on LPIC-2
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 most likely cause is that the kernel command line contains the 'ro' parameter. This parameter explicitly requests a read-only root mount, which persists after boot if no remount (e.g., by init or systemd) is performed. Option C is not the most likely because a damaged filesystem usually causes boot failures or drops to emergency mode, not a successful boot with a read-only root.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.