Home
  •  

Monitor REC_VOLUME_GROUP_PARTIALLY_COMPLETE (200)

NetAppESeries.FailureID_0200_Monitor (UnitMonitor)

A volume group has transitioned from the online to the partial state because of a drive removal.The partial state means that, while some drives are missing, there is a sufficient number left tomake volume data accessible.

Knowledge Base article:

Partially Complete Volume Group or Disk Pool

What Caused the Problem?

One or more drives are missing from a volume group or disk pool. There are still enough drives remaining that the volumes can continue servicing I/O. However, the volumes may not be able to continue I/O if more drives are removed or fail. 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

Affected Volume Groups

Affected Disk Pools

Recovery Steps

1

If...

Then...

The affected object is a volume group

Go to step 2.

The affected object is a disk pool

Go to

Completing a Drive Replacement

.

2

If...

Then...

You removed the drives - either inadvertently or you need to replace the drives

Go to

Completing a Drive Replacement

.

You removed the drives because you intend to export these drives to another storage array

Go to

Completing a Volume Group Export

.

You have inserted drives from another storage array and already selected the Force Import option

If...

Then...

The missing drives were not imported with the rest of the drives because they were damaged

Go to

Completing a Drive Replacement

.

You want to import the original drives that were associated with the volume group or disk pool in the source storage array

Go to

Completing a Volume Group Import

.

Completing a Drive Replacement

1

If...

Then...

You inadvertently removed the drives

Perform the following steps:

a

Reinsert all removed drives. The fault indicator lights may be lit for a short time (one minute or less).

b

Go to step 3.

You want to use new drives or Unassigned drives as replacements

Perform the following steps:

a

Verify that the replacement drives are:

  • A capacity equal to or greater than the failed drives you removed.

  • Certified for use in this storage array.

b

Insert all replacement drives. The fault indicator lights may be lit for a short time (one minute or less).

c

If...

Then...

The affected object is a disk pool

Reconstruction will begin and the drive will automatically be incorporated into the disk pool. Go to step 3.

The affected object is a volume group

Go to step 2.

2

Assign a drive to take over for the missing drive by completing the following steps:

a

Refer to the Details area to find out which volume group has been affected.

b

Highlight the affected volume group on the

Storage and Copy Services

tab in the Array Management Window, and then select the

Storage > Volume Group > Replace Drives

menu option.

c

Select the missing drive that corresponds to the to the slot location (identified in the Details area).

d

Select an appropriate replacement drive, and then click the

Replace Drive

button.

Note:

  • When the replace operation begins, data is reconstructed on the new drive using information on the other drives comprising the volume group. This reconstruction should begin automatically. The drive's fault indicator lights will go off and the activity indicator lights of the drives in the volume group will start flashing.

  • If you are replacing a drive in a storage array that contains hot spares, data reconstruction will start on the hot spare before you insert the new drive. The data on the replacement drive may not be reconstructed until after it has completed the process on the hot spare.

e

When the drive reconstruction completes and the volume group is Optimal, go to step 3.

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.

Element properties:

TargetNetAppESeries.StorageArray
Parent MonitorNetAppESeries.StorageArrayAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeNetAppESeries.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_VOLUME_GROUP_PARTIALLY_COMPLETE
A volume group has transitioned from the online to the partial state because of a drive removal.The partial state means that, while some drives are missing, there is a sufficient number left tomake volume data accessible. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="NetAppESeries.FailureID_0200_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_PARTIALLY_COMPLETE_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.StateIdE804452054A25C1FE7A8C6DC4A97A319" MonitorTypeStateID="NoIssue" HealthState="Success"/>

    <OperationalState ID="NetAppESeries.StateIdE1218040D961A8C7FB00073A9F79C0C5" MonitorTypeStateID="IssueFound" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <FailureID>200</FailureID>

    <IntervalSeconds>59</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>