Home
  •  

Monitor REC_HOTSPARE_DRIVE_MISSING (203)

NetAppSANtricity.FailureID_0203_Monitor (UnitMonitor)

A drive designated as a standby hot spare is missing from the configuration.

Knowledge Base article:

Missing Hot Spare Drive

What Caused the Problem?

A hot spare drive has been removed from the storage array. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Important Notes

Recovery Steps

1

If...

Then...

You removed the hot spare drive because you intend to replace the drive

Insert the replacement drive. When the replacement drive is spun up, go to step 2.

You removed the hot spare drive but intend to reinsert the same drive back into the original slot

Reinsert the drive. It will remain a hot spare drive unless you unassign it using the storage management software. Go to step 3.

Note: If at any time you want to unassign the hot spare drive, you can refer to the online help or complete the steps in Unassigning a Hot Spare Drive.

You intend to leave this drive slot empty

You must unassign this drive in the Hot Spare Coverage dialog. Go to

Unassigning a Hot Spare Drive

.

2

If...

Then...

You want the new drive to be a hot spare

You need to assign the new drive as a hot spare AND you need to unassign the previous drive in the "Hot Spare Coverage" dialog (even though it is no longer in the system).

a

Complete the steps in

Unassigning a Hot Spare Drive

to unassign the previous drive. When you have completed those steps, go to step b.

b

Complete the steps in

Assigning a Hot Spare Drive

to assign the new drive as a hot spare.

You do NOT want the new drive to be a hot spare

You do not need to do anything to the new drive. After the drive is spun up, it will be an unassigned drive. However, you must unassign the previous drive in the Hot Spare Coverage dialog (even though it is no longer in the system). Go to

Unassigning a Hot Spare Drive

.

3

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.

Assigning a Hot Spare Drive

1

Highlight the drive on the

Hardware

tab in the Array Management Window.

2

Select the

Hardware > Hot Spare Coverage

menu option.

3

Select the "Manually assign individual drives" radio button, and then click

OK

.

Note:  This option assigns the drive you highlighted in step 1 - the drive will change to a hot spare drive on the Hardware tab.  If you want to assign multiple drives, you can select the "View/change current hot spare coverage" radio button.

4

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.

Unassigning a Hot Spare Drive

1

Highlight the drive on the

Hardware

tab of the Array Management Window.

2

Select the

Hardware > Hot Spare Coverage

menu option.

3

Select the "View/change current hot spare coverage" radio button, and then click

OK

.

4

Highlight the affected hot spare drive slot in the Hot Spare Drives table, and then click

Unassign

.

Note: If you unassigned a drive that is physically present in the system, it will change to an unassigned drive on the Hardware tab. Otherwise, if the drive had been reported as missing from the storage array, then the removed hot spare drive will no longer appear on the Hardware tab.

5

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.

Element properties:

TargetNetAppSANtricity.StorageArray
Parent MonitorNetAppSANtricity.StorageArrayAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeNetAppSANtricity.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_HOTSPARE_DRIVE_MISSING
A drive designated as a standby hot spare is missing from the configuration. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="NetAppSANtricity.FailureID_0203_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_HOTSPARE_DRIVE_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="NetAppSANtricity.StateId3E559FBE259967971769D42E365AA71B" MonitorTypeStateID="NoIssue" HealthState="Success"/>

    <OperationalState ID="NetAppSANtricity.StateId7BBF0038978D9DC42FC92A62D7B5FFDF" MonitorTypeStateID="IssueFound" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <FailureID>203</FailureID>

    <IntervalSeconds>361</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>