RHEL 10 Multipath Device Names Change After Reboot

📖 ~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

Applications referencing /dev/mapper names fail when aliases shift across reboots.

Environment & Reproduction

Occurs in SAN environments without stable WWID alias rules.

sudo multipath -ll

Root Cause Analysis

Map names are auto-generated from discovery order rather than fixed aliases.

Quick Triage

Capture current WWIDs and dependent mount/LVM references.

sudo ls -l /dev/mapper | grep mpath

Step-by-Step Diagnosis

Inspect /etc/multipath.conf bindings and check initramfs for updated config.

sudo multipathd show config

Solution – Primary Fix

Define explicit aliases by WWID and rebuild initramfs so boot uses stable names.

sudo mpathconf --enable && sudo dracut -f

Solution – Alternative Approaches

Use UUID-based mounts and LVM PV UUID references to reduce name dependence.

Verification & Acceptance Criteria

Aliases remain consistent after reboot and dependent services start normally.

Rollback Plan

Revert multipath.conf and restore prior bindings file from backup.

Prevention & Hardening

Enforce WWID alias standards and include post-reboot path validation checks.

Related Errors & Cross-Refs

Cross-reference path flapping, SAN zoning drift, and duplicate WWID detection.

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

View all rhel-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

RHEL DM-Multipath deployment and naming persistence guidance.