Quick Answer
The answer is an incorrect root filesystem UUID in /etc/fstab. This error occurs because the kernel, upon encountering the unknown-block(8,17) designation, cannot match the specified filesystem identifier to any available partition; block device 8,17 corresponds to /dev/sdb1, meaning the device exists but the UUID in the fstab entry does not match the actual partition’s UUID, causing the mount to fail and triggering the kernel panic. On the LPIC-2 exam, this scenario tests your understanding of block device naming and the boot process, often appearing as a trap where candidates mistakenly suspect a missing driver or hardware failure rather than a simple configuration mismatch. A common memory tip is to think of the “unknown block” as a UUID mismatch—always verify with blkid or lsblk that the UUID in /etc/fstab matches the root partition’s actual identifier.
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.
A technician is troubleshooting a system that fails to boot after adding a new SATA SSD and editing /etc/fstab. The error message is 'Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,17)'. What is the most likely issue?
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.
The root filesystem UUID in /etc/fstab is incorrect.
Incorrect UUID leads to unknown-block error.
The kernel image is missing.
Why wrong: Missing kernel would prevent any boot messages.
The kernel lacks SATA driver support.
Why wrong: Most kernels include SATA drivers.
The initramfs was not regenerated after adding the disk.
Why wrong: Initramfs regeneration is not required for an additional disk unless the root filesystem changes.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
The root filesystem UUID in /etc/fstab is incorrect.
The error 'unknown-block(8,17)' indicates the kernel cannot find the root filesystem. Block device 8,17 corresponds to /dev/sdb1 (major 8 for SCSI/SATA, minor 17). The most likely cause is an incorrect UUID in /etc/fstab, which prevents the system from mounting the root partition. The kernel can see the device, but the mount fails because the UUID specified does not match any available partition.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
The root filesystem UUID in /etc/fstab is incorrect.
Why this is correct
Incorrect UUID leads to unknown-block error.
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 missing.
Why it's wrong here
Missing kernel would prevent any boot messages.
The kernel lacks SATA driver support.
Why it's wrong here
Most kernels include SATA drivers.
The initramfs was not regenerated after adding the disk.
Why it's wrong here
Initramfs regeneration is not required for an additional disk unless the root filesystem changes.
Common exam traps
The trap here is that candidates confuse a missing initramfs with an incorrect fstab entry, but the specific block device number proves the kernel sees the disk, so the issue is a mount configuration error, not a driver or initramfs problem.
Detailed technical explanation
The block device number (8,17) is a kernel-assigned major/minor pair: major 8 for sd devices, minor 17 for the second partition on the second disk (sdb1). The kernel parses /etc/fstab to find the root filesystem; if the UUID is wrong, it falls back to a kernel panic. A common real-world scenario is cloning a disk without updating the UUID in fstab, or manually editing fstab with a typo. The initramfs can also specify root=UUID=..., but the error here points to fstab because the kernel has already loaded the initramfs and is attempting the final root mount.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
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 — study guide chapter
Learn the concepts, then practise the questions
Linux Kernel and System Startup practice questions
Targeted practice on this topic area only
All LPIC-2 questions
511 questions across all exam domains
Linux Professional Institute Certification Level 2 LPIC-2 study guide
Full concept coverage aligned to exam objectives
LPIC-2 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise LPIC-2 questions linked to Linux Kernel and System Startup.
Practise LPIC-2 questions linked to Block Devices, Filesystems and Advanced Storage.
Practise LPIC-2 questions linked to Advanced Networking Configuration.
Practise LPIC-2 questions linked to DNS, Web and Mail Services.
Practise LPIC-2 questions linked to File Sharing and Samba.
Practise LPIC-2 questions linked to System Security.
Practise LPIC-2 questions linked to Network Client Management.
Practise LPIC-2 questions linked to LPIC-2 fundamentals.
Practise LPIC-2 questions linked to LPIC-2 scenario.
Practise LPIC-2 questions linked to LPIC-2 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Linux Kernel and System Startup — This question tests Linux Kernel and System Startup — Read the scenario before looking for a memorised answer..
The correct answer is: The root filesystem UUID in /etc/fstab is incorrect. — The error 'unknown-block(8,17)' indicates the kernel cannot find the root filesystem. Block device 8,17 corresponds to /dev/sdb1 (major 8 for SCSI/SATA, minor 17). The most likely cause is an incorrect UUID in /etc/fstab, which prevents the system from mounting the root partition. The kernel can see the device, but the mount fails because the UUID specified does not match any available partition.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
Same concept, more angles
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. A systems administrator is troubleshooting a server that fails to boot after a kernel upgrade. The boot process hangs at the stage where the kernel attempts to mount the root filesystem. Which of the following is the most likely cause?
hardWhy A: When the kernel fails to mount the root filesystem during boot, the most common cause is an incorrect or missing `root=` parameter in the kernel command line. This parameter specifies the device (e.g., `/dev/sda1` or `UUID=...`) that the kernel should mount as the root filesystem; if it points to a non-existent device, the kernel cannot proceed past the mount stage, resulting in a hang or kernel panic.
Variation 2. A server with a custom kernel fails to boot after a kernel update. The system displays a kernel panic: 'VFS: Unable to mount root fs on unknown-block(0,0)'. The root filesystem is on an LVM volume. What is the most likely cause?
hardWhy D: The kernel panic 'VFS: Unable to mount root fs on unknown-block(0,0)' indicates the kernel cannot locate the root filesystem. Since the root filesystem resides on an LVM volume, the initramfs must contain LVM tools and modules to activate the volume group and logical volumes before the kernel can mount the root. If the initramfs was not rebuilt after the kernel update, it will lack LVM support, causing the boot failure.
Last reviewed: Jun 11, 2026
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.