Multipath device map missing on startup

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

LUN-backed filesystems fail to mount because multipath device aliases are not present.

Environment & Reproduction

RHEL 8 SAN-attached host rebooted; run `multipath -ll` and observe missing maps.

Root Cause Analysis

Multipath service disabled, WWID blacklist issue, path daemon race condition, or stale initramfs config.

Quick Triage

Confirm `multipathd` service state and visible block devices before making persistent config edits.

Step-by-Step Diagnosis

Check `/etc/multipath.conf`, run `multipath -v3`, verify WWIDs, and inspect `journalctl -u multipathd`.

Solution – Primary Fix

Enable `multipathd`, correct blacklist/whitelist entries, rebuild initramfs if required, and rescan SCSI paths.

Solution – Alternative Approaches

Use explicit device mapper naming strategy and storage vendor-recommended profile defaults.

Verification & Acceptance Criteria

Expected maps appear in `multipath -ll` and dependent mounts/services start normally after reboot.

Rollback Plan

Restore previous `multipath.conf` and boot artifacts if new map policy hides valid paths.

Prevention & Hardening

Audit SAN path redundancy and validate multipath behavior after kernel or HBA driver updates.

Related Errors & Cross-Refs

`device not found`, LVM PV missing on mapper device, and mount unit failures at boot.

Related tutorial: View the step-by-step tutorial for rhel-8.

View all rhel-8 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

RHEL DM-Multipath guide and storage vendor interoperability matrices.