RAID 60 Became Unreadable After a Drive Swap
If the RAID 60 became unreadable immediately after drives were swapped, the physical change may have altered member order, group membership, enclosure mapping, or the configuration the controller accepted. Do not assume the swapped drive is the only problem.
Stop changing bays. Preserve the pre-swap and post-swap order, every original drive, and all controller messages before trying another combination.
What this condition means
RAID 60 depends on the correct members inside each RAID 6 group and the correct stripe across those groups. A bay or enclosure change can affect how the controller identifies that layout.
The drives may still contain useful data even when the current arrangement will not mount. Repeated swaps make the original state harder to reconstruct.
What to record
- Original and current bay order
- Serial number and size of every drive
- Which drives were moved, removed, or inserted
- Controller state before and after the swap
- Any import, force-online, rebuild, initialization, or repair that followed
What not to do
- Try additional drive combinations
- Initialize a newly presented virtual disk
- Clear or import configuration repeatedly
- Discard a drive that now appears foreign or failed
- Repair the filesystem on an unverified layout
How ADR evaluates it
ADR reconstructs the member history from bay records, serial numbers, metadata, and controller evidence, then checks each drive independently.
Each lower group and the upper stripe are rebuilt from protected access rather than by moving drives through more live combinations.
What happens next
The best recovery path is to stop the swapping and preserve the evidence that remains. ADR can then determine whether the original compound layout can be reconstructed without bringing it online.