Courseiva
Block Devices, Filesystems and Advanced StoragemediumMultiple ChoiceObjective-mapped

LPIC-2 Practice Question: Block Devices, Filesystems and Advanced Storage

After adding a new LUN to an existing SAN, the administrator runs multipath -ll but sees the new LUN as 'failed'. The multipathd service is running. What is the most likely cause?

⚠ Common exam trap

LPI often tests the misconception that multipathd needs a restart or configuration change for new LUNs, but the real issue is almost always the SCSI layer not having discovered the device due to incomplete SAN presentation or missing bus rescan.

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 new LUN has not been presented to the host from the SAN

When a new LUN appears as 'failed' in `multipath -ll` output, the most common cause is that the LUN has not been properly presented to the host from the SAN. Even if the multipathd service is running, multipathd can only manage devices that the SCSI layer has already discovered. If the SAN administrator has not zoned or masked the LUN to the host, the host's SCSI subsystem never sees the device, so multipathd reports it as 'failed' because it cannot find the underlying paths.

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 multipathd daemon needs to be restarted

    Why it's wrong here

    Restarting is unnecessary; multipathd is already running and would still show failure if LUN is not presented.

  • The new LUN has not been presented to the host from the SAN

    Why this is correct

    If the LUN is not presented, the host cannot see it, causing all paths to show 'failed'.

  • The /etc/multipath.conf needs to be edited to include the new LUN

    Why it's wrong here

    Multipath discovers LUNs automatically; config editing is not required for detection.

  • The scsi device needs to be manually created with mknod

    Why it's wrong here

    SCSI devices are created automatically by udev; manual mknod is not required.

About these practice questions

One of 507 original LPIC-2 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-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.