RAID 50 Foreign Configuration Detected on One Group
A foreign-configuration warning means the controller sees RAID metadata that does not match the configuration it currently accepts. In RAID 50, importing or clearing one group can affect the compound array above it, so the complete member set must be reviewed together.
Do not import or clear the foreign configuration in isolation. Save every controller screen and preserve the bay order of all groups.
What this condition means
The warning may follow a controller change, member movement, enclosure change, interrupted rebuild, firmware event, or reappearance of a previously missing drive.
Foreign does not mean bad, current, or safe to import. It is evidence of another recorded array state that must be compared with the rest of the members.
What to record
- Controller model, firmware, cache state, and replacement history
- Every foreign, online, offline, missing, or unconfigured member
- Bay, serial number, size, and expected group assignment
- Preview or import details shown by the controller
- Power, cable, enclosure, rebuild, and member-movement history
What not to do
- Import the foreign group without reviewing every member
- Clear the foreign configuration
- Force a member online to make the group complete
- Move drives through different bays or controllers
- Initialize a virtual disk presented after an import
How ADR evaluates it
ADR compares the foreign metadata with the controller state, member identities, group geometry, and write history.
Candidate lower groups are tested outside the production controller before the top-level stripe and filesystem are accepted.
What happens next
The foreign record may contain useful configuration evidence. Preserving it gives ADR more information for identifying the correct RAID 50 layout without committing an import.