A contingent
volume group refers to a foreign drive in the storage array which
has an inconsistent configuration database.
What Caused the Problem?
A foreign drive that is part of a Contingent volume group has an inconsistent role (for example, the drive may be assigned to a volume group and unassigned at the same time). A foreign drive is a drive that has been exported from this storage array or not yet completely imported into the storage array. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Caution: Electronic discharge can damage sensitive components. Always use proper antistatic protection when handling components. Touching components without using a proper ground may damage the equipment.
Important Notes
This problem usually results from inserting a drive (from a different storage array into this storage array) and that drive may have been assigned a role by this storage array or a different storage array that is different than what it was originally given in the Contingent Volume group.
To resolve this problem, you will need to remove the foreign drive, import the Contingent volume group, and then assign a local drive to take its place. Follow the recovery steps below to fix the problem.
Once you have completed the recovery steps, you will have fixed the logical problem for the volume group. However, if you reinsert the foreign drive, the storage array might report a different problem if the drive still has a logical problem (for example, the drive might still consider itself part of the native volume group). If this scenario occurs, follow the additional Recovery Guru steps to fix the drive's logical problem.
You can remove the drive while the storage array is receiving I/O.
Recovery Steps
1 | Refer to the Details area to find which drive slot is reporting the foreign drive. | ||||||
2 | Remove the foreign drive. | ||||||
3 | Select the Contingent volume group on the Storage and Copy Services tab in the Array Management Window, and then select the Storage > Volume Group > Advanced > Import menu option. | ||||||
4 | Follow the instructions in the Import Volume Group dialog to properly import the volume group into the storage array. Note:
| ||||||
5 | Important : Read all of the following steps thoroughly or click the Save As button before taking action, because you will lose access to these recovery steps once you click Recheck .
|
| Target | NetAppESeries.StorageArray | ||
| Parent Monitor | NetAppESeries.StorageArrayAvailability | ||
| Category | Custom | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | NetAppESeries.FailureUnitMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Machine generated entity |
Home
<UnitMonitor ID="NetAppESeries.FailureID_0217_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppESeries.StorageArray" ParentMonitorID="NetAppESeries.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppESeries.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="NetAppESeries.REC_FOREIGN_DRIVE_HAS_INCONSISTENT_ROLE_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Property[@Name='FailureDescription']$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="NetAppESeries.StateIdDA49E2FDE40D82ADE2AE05AB9106D5F5" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId2E34092F4376588D9C1124A5C202CA7" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>217</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>