Business-critical storage failure?1-800-228-8800
ADRADR Data RecoveryRAID · Server · NAS · Virtualization Start Emergency Triage

RAID Degraded and Unstable: What to Do Before Rebuilding

A degraded array has already lost redundancy. If it is also slowing down, dropping members, producing read errors, or making the volume disappear, the surviving set may not be healthy enough to support a rebuild.

Preserve the current state.

Reduce nonessential writes and do not begin a rebuild until the failed member, the remaining members, and the sequence of events are understood.

What this condition means

Degraded describes the RAID membership state. Unstable describes what the remaining storage is doing. The combination can point to unreadable sectors, timeouts, a controller or path problem, inconsistent metadata, or another member beginning to fail.

A rebuild places sustained read load on every required source and writes a new member state. If the sources are not trustworthy, restoring redundancy can turn a recoverable outage into a failed rebuild.

What to record

What not to do

How ADR evaluates it

ADR separates member failure from controller, enclosure, and metadata problems, then determines whether the active sources are readable enough for a controlled recovery plan.

Stable cases may be evaluated at the client location. If a member is unstable, it is protected before reconstruction proceeds away from the original controller.

Do not make a rebuild the next diagnostic step.

ADR can review the failure sequence, connect to stable members independently, and protect any unstable member before reconstruction. The degraded array does not need to remain online or accept another controller write for that work to begin.

What happens next

A degraded array is often recoverable and may still be serving data. The unstable behavior is the reason to preserve the current state before asking the remaining members to rebuild it.