A degraded array and a failed array can look nearly identical on the screen — a drive icon shows red, and there's a button labeled "Rebuild." But whether that button is the right next step depends entirely on what actually happened underneath it, and clicking it without knowing can cost you data that was otherwise recoverable.
What a RAID rebuild actually is
A rebuild is a normal maintenance operation, not a recovery procedure. When a single drive in a healthy array is replaced or reinserted, the controller or NAS reconstructs that one drive's contents using the parity or mirror data stored on the other member drives. It's the same mechanism that lets RAID 5, RAID 6, and mirrored arrays tolerate a drive failure in the first place — swap the bad disk, start a rebuild, and the array restores itself to full redundancy.
This works because the process assumes something important: that every other drive in the array is fully healthy and reading correctly. When that assumption holds, a rebuild is routine and low-risk.
What RAID data recovery is
Recovery is a different discipline entirely, used when the array itself has failed, dropped offline, or already lost data — and the "everything else is healthy" assumption no longer holds. Instead of operating on the live drives, a recovery lab works from images of the drives, cloned byte-for-byte, and reconstructs the array logically from those copies. Nothing is written to the original disks, so a wrong guess costs nothing and can simply be tried again.
Why people confuse the two
The confusion is understandable, because the interface doesn't distinguish between them. When an array degrades or a drive drops out, most NAS and controller software offers the same "Rebuild" button regardless of the underlying cause. It looks like the obvious fix, and often it is — but that button assumes the other drives are fully healthy, which is frequently exactly the assumption that's wrong right when something has already gone wrong. A second drive may be quietly weak or failing, the wrong drive may have been reinserted, or drives may have been swapped into the wrong bays.
Why clicking rebuild on a failed array is dangerous
A rebuild writes across every remaining drive in the array to recompute and restore parity or mirrored data. That's fine when the assumptions behind it are true. But if any assumption is wrong — a marginal drive, bad sectors on a member that looked healthy, drives in the wrong order or slot, or outdated array metadata — the rebuild can overwrite the last good copies of your data. This is, by a wide margin, the single most common way a RAID data recovery case goes from possible to impossible.
- A rebuild assumes the surviving drives are fully healthy — an assumption that often fails right when an array first goes offline.
- Rebuilds write to every remaining disk, so a wrong assumption doesn't just fail — it overwrites data.
- Once a rebuild has overwritten parity or data blocks, that information is generally gone for good.
How a recovery lab approaches it instead
A professional lab never touches the original array. Each member drive is imaged individually, preserving its exact byte pattern, and the array is reconstructed virtually from those images rather than from the drives themselves. Different rotations, parity schemes, and drive orders can be tested against the copies until the correct configuration is found — all without risk to the originals, since mistakes made on a clone cost nothing.
A simple rule before you click anything
If a single drive failed or was swapped and the array is still online and running in a degraded state, a normal rebuild through the manufacturer's instructions is generally fine. If the array is offline, if multiple drives are involved, or if you're not sure why it dropped out in the first place, stop before rebuilding anything and get an evaluation.
Our team works with degraded and failed arrays on NAS and server-grade RAID every day — see our RAID data recovery service for more on how these cases are handled, including what to do when a second drive fails on a RAID 5. For a broader look at the situations that make recovery harder, read about common data recovery challenges.
Not sure whether your situation calls for a rebuild or a recovery? Find out before anything gets overwritten. Start with a free evaluation.
Request free evaluation →