Debian 11 – mdadm array degraded after disk failure – Fix & Prevention

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

RAID redundancy is lost and another disk fault may cause total data unavailability.

Environment & Reproduction

Triggered by physical disk failures, transport errors, or faulty controller links.

Root Cause Analysis

md subsystem marks one member failed, reducing array from healthy to degraded mode.

Quick Triage

Identify failed member device and confirm whether rebuild is already in progress.

Step-by-Step Diagnosis

Run: cat /proc/mdstat; sudo mdadm –detail /dev/md0; sudo dmesg -T | egrep -i ‘md|ata|i/o error’ | tail -n 100.

Solution – Primary Fix

Replace failed disk and run: sudo mdadm /dev/md0 –fail /dev/sdX –remove /dev/sdX; sudo mdadm /dev/md0 –add /dev/sdY; monitor /proc/mdstat.

Solution – Alternative Approaches

If hot-swap is unavailable, schedule controlled outage and rebuild from backup to new array.

Verification & Acceptance Criteria

Array returns to clean state with all expected active members.

Rollback Plan

Restore data from backup snapshot if rebuild fails or additional members degrade.

Prevention & Hardening

Enable SMART monitoring and proactive disk replacement policies by wear thresholds.

Related Errors & Cross-Refs

Often appears with read I/O errors, medium errors, and controller timeout warnings.

Related tutorial: View the step-by-step tutorial for Debian 11.

View all Debian 11 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

mdadm administration guide and Debian RAID operational best practices.