RHEL 7 multipath devices missing 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

Critical SAN-backed volumes do not appear after reboot, causing application and database startup failures. Recovery may require manual storage intervention and extended downtime.

Environment & Reproduction

Common when multipathd is disabled, WWID bindings drift, or initramfs lacks required modules. Reproduce by disabling multipath startup and rebooting host with SAN LUN dependencies.

Root Cause Analysis

Device discovery occurs without proper multipath coordination, so maps are not assembled in time for dependent mounts/services. Configuration mismatch in multipath.conf can also suppress expected aliases.

Quick Triage

Check systemctl status multipathd, run multipath -ll, and inspect journalctl -b for SCSI/path errors. Verify SAN path visibility and firewalld/iSCSI rules where applicable.

Step-by-Step Diagnosis

Validate WWID binding files, multipath blacklist/whitelist rules, and initramfs contents. Correlate storage path events with service startup failures in journalctl and systemd dependency logs.

Solution – Primary Fix

Enable multipathd at boot, correct multipath.conf entries, rebuild initramfs if required, and restart storage services using systemctl. Re-scan buses and confirm maps before app startup.

Solution – Alternative Approaches

Use static device mapper aliases, tune path checker settings, or fail over workloads to standby nodes while SAN zoning/host config is corrected.

Verification & Acceptance Criteria

All required multipath maps should appear consistently after reboot, mountpoints must recover, and journalctl should show healthy path detection without repeated failures.

Rollback Plan

Revert recent multipath config changes and restore prior initramfs if newly built image regresses boot behavior. Keep manual mount and app hold procedures ready.

Prevention & Hardening

Audit multipath startup state, validate SAN path redundancy, and include reboot tests in storage change windows. Maintain documented systemctl/service operations for storage stack components.

Related Errors & Cross-Refs

Related events include LVM PV missing after boot and mount dependency failures. Cross-reference HBA driver updates, kernel changes from yum, and SAN controller maintenance.

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

View all rhel-7 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Consult Red Hat multipath administration docs, vendor SAN integration guides, and internal storage DR procedures for deterministic reboot recovery.