RAID 10 Configuration Import Failed: Preserve Every Version
A failed import means the controller could not accept or assemble the configuration it found. That may reflect missing members, conflicting metadata, a controller or enclosure change, or mirror copies from different points in the array history.
Do not clear the foreign configuration or recreate the RAID 10. Save the import preview and preserve every member in its present bay.
What this condition means
Configuration records identify members, mirror pairs, geometry, and virtual-disk state. A failed import is evidence of disagreement, not proof that the member data is gone.
Clearing, reimporting, or moving the set through different controllers can write or replace metadata that helps distinguish the original layout from later states.
What to record
- Original and current controller make, model, firmware, and cache state
- Import preview, foreign-configuration details, and exact failure message
- Bay, serial number, size, and status of every member
- Original mirror-pair assignments if known
- Controller replacement, power, member movement, rebuild, and import history
What not to do
- Clear the foreign configuration
- Retry imports on different subsets of members
- Create a replacement RAID 10
- Force members online
- Initialize a virtual disk presented after a partial import
How ADR evaluates it
ADR compares configuration generations with member identity, mirror relationships, readability, and write history.
Candidate pair and stripe layouts are tested outside the production controller before a volume is accepted.
What happens next
The failed import does not have to succeed on the controller for recovery to begin. Preserved configuration evidence and member access can support an independent reconstruction.