Spare Disk Management

Always trigger AutoSupport

Options autosupport.doit   ‘diskfailure’

 Verification of failed disk:

a. Confirm the failed disk id on filer:

EX:

exruefieif01*> aggr status -f

Broken disks

RAID Disk       Device  HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)

---------       ------  ------------- ---- ---- ---- ----- --------------    --------------

failed          0c.76   0c    4   12  FC:A   -  FCAL 15000 272000/557056000  274845/562884296

b. Confirm the status of Raid reconstruction:

  

Please ensure that raid reconstruction is able to start successfully otherwise another disk failure in same aggregate can lead to double degraded mode resulting in shutdown of filer or data corruption.

c. Create ticket for disk replacement as per the DC support guidelines.

Verification of replacement disk:

Once NetApp support confirms that failed disk is physical replaced verify that failed disk is replace successfully and visible on filer:

1. Run the below commands to verify that the replaced disk is available as spare disk:

2. If not visible in above command, run below command to verify if the disk is replaced but still unassigned to controller.

3. Assign the disk, this will make the disk visible as spare disk:

Ex: disk assign 1b.33

4. Confirm with below command that disk is available as spare disk:

 Spare disk Recommendation:

A controller that is the primary owner of a set of drives can allocate up to the following number of spares (per drive type):

Number of drives per controller	Number of Spares
14–27 drives	1 spare
28–100 drives	2 spares
Additional 84 drives	1 additional spare

Example: A controller with 184 drives (one drive type) can have up to three spares.