What Causes a RAID Array to Stay Degraded After a Replacement Disk Is Added?
A RAID array stays degraded when the replacement is visible but has not become a valid rebuilding member. Common causes are wrong size, foreign metadata, unsupported state, missing manual assignment, or another failing source disk.
Do not initialize the replacement or import a foreign configuration at random. First identify the exact array, missing role, replacement serial number, controller state, and rebuild eligibility. The goal is to attach an empty eligible target without changing the trusted source configuration.
Confirm the Replacement Is Seen by the Correct Controller
A disk can appear in the operating system while remaining unavailable to the RAID controller, or appear to the controller in a different enclosure slot than expected. Compare the physical serial number, bay, controller port, and reported sector count.
If the new drive is not visible at the RAID layer, check power, backplane, cable, HBA mode, and enclosure mapping before changing array metadata. Repeated insertion without identifying the serial can lead to servicing the wrong member.
Ready, Unconfigured, and Spare Are Not Rebuilding
Many hardware controllers place a new disk in a neutral state such as Ready or Unconfigured Good. The array remains degraded until the disk is assigned as the replacement, dedicated spare, or eligible global hot spare according to that controllerโs workflow.
A new drive in Ready state is a useful example: presence alone does not fill the missing RAID role. Check whether hot insertion, manual replacement, or spare assignment is required.
Software RAID Usually Needs an Explicit Add
Linux md arrays do not necessarily re-add a disappeared disk merely because a block device returned at the same path. The old member may still be marked removed, while the replacement exists only as an unused device.
The manual mdadm re-add behavior reflects a safety boundary: automatically trusting a device that previously disappeared can be worse than requiring an administrator to verify it and add it deliberately.
Foreign Metadata Can Block the Replacement
A reused disk may contain RAID signatures from another array. Controllers label this as foreign because importing it could alter the active configuration. A brand-new disk can also carry factory, test, or previous-use metadata that prevents automatic eligibility.
Do not import foreign configuration from a disk intended to be an empty replacement. In a foreign replacement-disk state case, changing the new member to an unconfigured-good state was the relevant path, not importing its old array definition.
Capacity and Sector Geometry Must Meet the Array Minimum
The replacement must provide at least as many usable sectors as the failed member. A nominally equal drive can be a little smaller. Some controllers also reject a change in logical or physical sector format, interface type, firmware qualification, or encryption capability.
Compare exact size and sector format rather than only the label on the box. If the controller reports the new disk as unsupported or too small, do not force it online; choose a compatible larger target.
Another Source Disk May Be Preventing Reconstruction
A rebuild needs readable data from the surviving members. If another disk has unrecoverable sectors, repeated timeouts, or drops from the array, the controller may abort, keep the replacement as a spare, or remain degraded after a failed reconstruction attempt.
Review the event log from the moment the original disk failed through the replacement attempt. The newest alert may refer to the target, while the actual blocker is a read error on a different source member.
Use a State-Based Troubleshooting Order
| Replacement state | Likely meaning | Next check |
|---|---|---|
| Not detected | Connection or controller-path issue | Power, cable, bay, HBA, serial map |
| Ready / Unconfigured Good | Visible but not assigned | Replacement or spare assignment |
| Foreign | Old RAID metadata present | Verify identity; clear only the new target metadata |
| Too small / unsupported | Eligibility failure | Exact sectors, format, controller support |
| Spare, not rebuilding | No trigger or source error | Missing role, policy, surviving-member logs |
| Rebuild aborted | Source or path could not complete | Read errors, timeouts, second failure |
A controller-specific manual rebuild assignment may use a hot-spare action to trigger recovery. Use the platformโs documented state transition rather than generic commands copied from another RAID stack.
Verify the Rebuild Trigger Before Leaving the System
Once the replacement is assigned, watch long enough to confirm that processed blocks increase and the intended serial number is the target. A state transition that starts and immediately aborts is still a degraded array, even when the dashboard briefly displayed rebuilding.
Save the first error after an abort. It often identifies the actual blocker more clearly than the final summary, especially when a surviving source disk times out or the controller rejects the target geometry.
FAQ
Should I initialize the replacement disk first?
Usually no. Initialization can write metadata and may be destructive if the wrong disk is selected. Prepare only the confirmed empty target using the controllerโs replacement workflow.
Why did cold swapping leave the new disk unused?
Some controllers detect and associate a replacement differently during hot insertion. Cold swapping can leave a missing role plus a separate ready disk that must be assigned manually.
Can I force the drive online?
Force-online actions are intended for specific recovery situations and can promote stale data. For a new empty replacement, assign it as the rebuild target or spare instead of pretending it contains current array data.
The Array Becomes Healthy Only After Membership Changes
A visible replacement does not remove degraded status. It must be eligible, assigned to the missing role, rebuilt from readable sources, and promoted to an active synchronized member.
Support & Tips
More to Read
Why Does a RAID Array Become Inactive After a Power Loss?
An inactive array often means metadata was found but the system did not have enough confidence or members to start it safely after an...
What Are the Risks of Forcing a Missing RAID Member Back Online?
Force options can bypass safety checks around stale metadata, dirty parity, missing writes, or active pools; inspect and preserve evidence before using them.
How to Distinguish a Bad SATA Cable From a Failing NAS Drive
Track whether errors follow the disk or remain with the SATA path, and separate transport counters from media-health evidence before replacing hardware.
