A volume group has transitioned from the online or incomplete state to the missing state becauseof drive removal. The missing state means that all drives of the group are missing.
What Caused the Problem?
The storage array has detected that all of the drives associated with a volume group or disk pool are missing. 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 no drives remaining to reconstruct replacement drives for the missing drives.
This problem can occur for the following reasons:
There was a loss of power to one or more drive trays.
You removed drives because you intend to export them to another storage array. However, for volume groups, you did not use the export operation available in the storage management software to prepare these drives before removal. For disk pools, exporting drives is not supported.
You removed all drives associated with a volume group or disk pool for some other reason.
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
.
Recovery Steps
1 |
| ||||||||||||||||||||||
2 |
| ||||||||||||||||||||||
3 |
| ||||||||||||||||||||||
4 |
| ||||||||||||||||||||||
5 | 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 |
<UnitMonitor ID="NetAppESeries.FailureID_0202_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_MISSING_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.StateIdC2C3737863526D2678D2B065109261BF" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId95CD3BF53955DBC043A41DF7A9AD3652" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>202</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>