RAID 60 Rebuild Stuck at 0%, 5%, or 10%: Stop and Record It
A RAID 60 rebuild that stops near the beginning is usually encountering a problem it cannot read through or resolve. The source members, replacement target, controller path, and lower-group configuration all need to be preserved before another attempt.
Do not restart the rebuild or replace another drive. Keep the original member and the partial rebuild target, and record the exact stopping point and errors.
What this condition means
A low stopping percentage may point to unreadable sectors, repeated timeouts, enclosure or controller errors, a poor replacement target, or a lower group that is not assembled as expected.
The partial target is no longer blank. It may contain useful reconstructed regions and must be kept separate from the original member it was intended to replace.
What to record
- Rebuild start time, stopping percentage, and complete error messages
- Which lower RAID 6 group and member were being rebuilt
- Original member, replacement target, bay, serial number, and size
- Status of every other member in both groups
- Power, cabling, controller, enclosure, and firmware events
What not to do
- Restart the rebuild as a test
- Discard or reuse the original member
- Erase or repurpose the partial target
- Replace another reported member before diagnosis
- Run filesystem repair against the incomplete array
How ADR evaluates it
ADR checks the original sources and the partial target separately, identifies the affected lower group, and determines what can be read reliably.
Recovery proceeds from protected member access. The lower RAID 6 groups and top-level stripe are validated before data is recovered to separate storage.
What happens next
A stopped rebuild may still leave several usable sources. The safest next step is to preserve every version of the array and determine why progress stopped before asking the same drives to try again.