RAID 10 Import Config Failed
Symptom:
After replacing one or more drives, controller prompts to import foreign config — but import fails or array goes missing afterward.
What This Likely Means:
This usually indicates a mismatch between the controller’s cached config and what’s now physically connected. It can happen if:
- Drives were replaced in the wrong order
- A partial config was auto-imported during boot
- A previous rebuild was incomplete or interrupted
What Not to Do:
- Avoid forcing config imports unless you’re 100% sure of original disk order.
- Don’t delete the virtual disk to “start fresh” — this wipes access to volume headers and striping info.
What to Try First:
- Look for foreign drives — don’t clear them yet.
- Try exporting the config data or view it in controller logs.
- Use JeannieLite to extract the current RAID layout before changes.
When to Escalate:
If the import fails and the array disappears, the safest path is preservation first, then reconstruction with forensic tools — not controller guesswork.