A volume group has transitioned from the online state to the incomplete state because of a drive removal. The incomplete state means that the group does not have enough drives to make volume data accessible.
What Caused the Problem?
One or more drives are missing from a volume group or disk pool and there are NOT enough drives remaining for the volumes to continue servicing I/O. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Caution: Electrostatic 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
Volume data is not accessible for the volume group or disk pool because there are not enough drives remaining to reconstruct replacement drives for the missing drives.
For both volume groups and disk pools, this problem can occur for the following reasons:
There was a loss of power to one or more drive trays.
You removed drives - either inadvertently or in order to replace the drives.
As a result of one or more drives being bypassed. If there is a "Bypassed Drive" problem being reported in the Recovery Guru Summary area, complete the recovery steps to correct the "Bypassed Drive" problem first. Only continue with the recovery steps for this problem if it is still displayed after you click
Recheck
.
You can reinsert missing drives for a volume group or disk pool while the affected volumes are receiving I/O.
Affected Volume Groups
Depending on the RAID level of the volume group, you may be able to reinsert some of the original drives and be able to access the data on the volume group after it changes to the Partially Complete state.
For volume groups, this problem can also occur for the following reasons:
You removed drives because you intend to export them to another storage array. However, you did not use the export operation available in the storage management software to prepare these drives before removal.
You inserted drives because you intend to import them from another storage array. However, you selected the force import operation in the storage management software and not all of the drives for the volume group are inserted.
The volume group will be in a Failed state on the
Storage and Copy Services
tab.
If a volume is in a volume group and is receiving I/O, then the volume may be displayed as a degraded volume if there is not sufficient hot spare coverage.
Affected Disk Pools
You may be able to reinsert some of the original drives and be able to access the data on the disk pool after it has changed to the Partial state.
For disk pools, this problem can also occur if you removed drives because you intend to export them to another storage array, or inserted drives because you intend to import them from another storage array. However, the disk pool feature does not support exporting or importing drives.
The only recovery action for a disk pool is to reinsert any missing drives.
The disk pool will be in a Incomplete state on the
Storage and Copy Services
tab.
Recovery Steps
1 |
|
2 |
|
3 | Click the Recheck button 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. |
Completing a Volume Group Export
1 | Reinsert all of the missing drives associated with this volume group into the original slots. The Details area provides the physical location of the missing drives as well as the affected volume group. |
2 | Wait for the volume group and its associated volumes to display an Optimal status. |
3 | On the Storage and Copy Services tab in the Array Management Window, select the volume group you want to export. |
4 | Select the Storage > Volume Group > Advanced > Export menu option. |
5 | Follow the instructions in the Export Volume Group wizard to successfully export the volume group. |
6 | Click the Recheck button 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. |
Completing a Volume Group Import
1 | Insert all of the missing drives associated with this volume group with the original drives from the source storage array. The Details area provides the physical location of the missing drives as well as the affected volume group. Note: If the original drives are not available, you can also use the Replace Drive option in the storage management software to reconstruct other unassigned drives in the storage array to take over for the missing drives. |
2 | Wait for the volume group and its associated volumes to display an Optimal status. |
3 | Click the Recheck button 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 | 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_0201_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_VOLUME_GROUP_INCOMPLETE_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.StateId29BC8E31AE38095AAC246BAAA779632" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId159DC21505BDCF2F21334972EE8D97A9" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>201</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>