A partial volume group refers to a foreign drive in the storage array; a foreign volume group refersto the same drive; and the foreign drive considers itself assigned to the foreign volume group.
What Caused the Problem?
A Partially Complete volume group considers a foreign drive to be a member of the volume group; however, the drive is a member of a foreign volume group (a volume group that is in a Contingent or Exported state). 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 because ALL of the following are true:
You inserted one or more drives (from a different storage array into this storage array)
Those foreign drives are members of a volume group
That volume group contains a drive that was previously a member of the native Partially Complete Volume Group
The drive that is shared between the two volume groups may or may not be physically inserted in the storage array, rather the two volume groups could be sharing a reference to the same absent drive
To resolve this problem, you will need to remove all of the drives in the foreign volume group (including the drive reporting the problem), reassign a drive to take over for the missing drive in the Partially Complete Volume Group, and then re-insert the foreign volume group.
You can remove the drive while the storage array is receiving I/O.
Recovery Steps
1 | Refer to the Details area to find which drives are in the foreign volume group. | ||||||
2 | Remove all of the drives in the foreign volume group including the drive that is reporting the problem. | ||||||
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 if you click Recheck .
Note : By replacing the missing drive, you have removed the reference from this volume group to the drive in the other volume group. | ||||||
4 | Re-insert each drive that you removed in step 2 until all have been re-inserted into the storage array. | ||||||
5 | When all of the drives are spun up and recognized, a Contingent volume group should appear on the Storage and Copy Services tab. Select the Contingent volume group on the Storage and Copy Services tab, and then select the Storage > Volume Group > Advanced > Import menu option. | ||||||
6 | Follow the instructions in the Import Volume Group dialog to properly import the volume group into the storage array. | ||||||
7 | Click Recheck to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your Technical Support Representative. |
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 |
<UnitMonitor ID="NetAppSANtricity.FailureID_0225_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_VG_HAS_DRIVE_PART_OF_MULTIPLE_VGS_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.StateId715AE182BC091B8A542A1DB8C2781AEA" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppSANtricity.StateIdA12B56BA58F6691A4ED0D9D877F53F49" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>225</FailureID>
<IntervalSeconds>361</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>