A volume group in the partial state along with its missing drive are present in the same storage array, however their respective metadata are in conflict, making it impossible to complete the volume group.
What Caused the Problem?
A volume group that is native to this storage array considers a foreign drive to be a member of the volume group. 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) that might have previously been a member of the native volume group.
The affected volume group will be in a Partially Complete state until you fix this problem. Any additional drive failures could result in loss of access to the volume group data.
To resolve this problem, you will need to remove the foreign drive, 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 volume group). If this scenario occurs, follow the Recovery Steps for the other problem 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 | 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 the Recheck button.
|
| Target | NetAppSANtricity.StorageArray | ||
| Parent Monitor | NetAppSANtricity.StorageArrayAvailability | ||
| Category | Custom | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | NetAppSANtricity.FailureUnitMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Machine generated entity |
Home<UnitMonitor ID="NetAppSANtricity.FailureID_0214_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppSANtricity.StorageArray" ParentMonitorID="NetAppSANtricity.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppSANtricity.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="NetAppSANtricity.REC_NATIVE_VG_REFERS_TO_FOREIGN_DRIVE_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="NetAppSANtricity.StateId9E850328D887410A431AA50B500CB3B0" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppSANtricity.StateId3917268FB2A6F8EBC3DD2E7FF7474D23" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>214</FailureID>
<IntervalSeconds>361</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>