RAID Array Offline and Data Inaccessible: What to Do
When a RAID array goes offline, the controller is no longer presenting the member set as the volume the server expects. The drives may still contain the data, but the controller, detected members, or configuration evidence no longer produces one trusted array state.
Do not recreate or initialize the array, force members online, clear foreign metadata, or run filesystem repair. Record the current controller and drive state before another change.
Tell an ADR technician what the system reports and what has already been attempted. The failed system does not have to be brought online first.
What this condition means
An offline array can follow a failed or missing member, power loss, controller or cache problem, cabling fault, interrupted rebuild, foreign configuration, or disagreement between member metadata.
The controller status is a starting clue, not a complete diagnosis. A drive shown as healthy can still be unstable, and a drive shown as failed may remain readable enough to contribute to recovery.
What to record
- Server, controller or NAS model and firmware
- RAID level, member count, and last known usable capacity
- Slot, serial number, and status of every original and replacement drive
- Virtual-disk, physical-disk, cache, and event-log messages
- The failure sequence and every rebuild, import, force-online, replacement, or repair attempt
What not to do
- Create or initialize a replacement virtual disk
- Force drives online by trial and error
- Clear or import configuration without the complete member set
- Change drive order without documenting it
- Run filesystem repair on an uncertain reconstruction
How ADR evaluates it
ADR compares controller evidence, member identity, drive readability, and RAID metadata to establish the last defensible array state.
Unstable members are protected before reconstruction. Candidate layouts are assembled away from the failed controller and validated through the filesystem and priority files before data is delivered.
ADR can start from the preserved controller evidence and independently connected members. The failed server can remain offline while the array is identified, protected, reconstructed, and checked in a controlled recovery environment.
What happens next
An offline array can remain recoverable when the original members are preserved and configuration changes have not overwritten the evidence needed to reconstruct it.