Skip to main content

Replace failed software RAID drives for ONTAP Select

Contributors dmp-netapp netapp-cgoff netapp-pcarriga
PDFs

When a drive using software RAID fails, ONTAP Select assigns a spare drive if one is available and starts the rebuild process automatically. This is similar to how ONTAP works on FAS and AFF. However if no spare drive is available, you need to add one to the ONTAP Select node.

Note Both the removal of the failed drive and the addition of a new drive (marked as a spare) must be performed through ONTAP Select Deploy. Attaching a drive to the ONTAP Select VM using vSphere is not supported.

Identify the failed drive

When a drive fails you need to use the ONTAP CLI to identify the failed disk.

KVM
Before you begin

You must have the VM ID of the ONTAP Select virtual machine, as well as the ONTAP Select and ONTAP Select Deploy administrator account credentials.

About this task

You should only use this procedure when the ONTAP Select node is running on KVM and configured to use software RAID.

Steps

  1. At the ONTAP Select CLI, identify the disk to be replaced:

    1. Identify the disk by serial number, UUID, or target address in the virtual machine.

      disk show -fields serial,vmdisk-target-address,uuid

    2. Optionally, display a complete list of the spare disk capacity with the partitioned disks.
      storage aggregate show-spare-disks

  2. At the Linux command line interface, locate the disk.

    1. Examine the system devices, searching for the disk serial number or UUID (disk name):

      find /dev/disk/by-id/<SN|ID>

    2. Examine the virtual machine configuration, searching for the target address:

      virsh dumpxml VMID
ESXi
Steps

  1. Sign in to the ONTAP CLI using the administrator account.

  2. Identify the disk drive that failed.

    <cluster name>::> storage disk show -container-type broken
Usable Disk Container Container
Disk Size Shelf Bay Type Type Name Owner
---------------- ---------- ----- --- ------- ----------- --------- --------
NET-1.4 893.3GB - - SSD broken - sti-rx2540-346a'

Remove the failed drive

After you identify the drive that failed, remove the disk.

KVM using Deploy

You can detach a disk from a KVM host as part of replacing the disk or when it is no longer needed.

Before you begin

You must have the ONTAP Select and ONTAP Select Deploy administrator account credentials.

Steps

  1. Sign in to the Deploy utility web user interface using the administrator account.

  2. Select the Clusters tab at the top of the page and select the desired cluster from the list.

  3. Select + next to the desired HA pair or node.

    If the option is disabled, Deploy is currently refreshing the storage information.

  4. Select Edit Storage on the Edit Node Storage page.

  5. Deselect the disks to be detached from the node, enter the ONTAP administrator credentials, and select Edit Storage to apply the changes.

  6. Select Yes to confirm the warning in the popup window.

  7. Select the Events tab for the cluster to monitor and confirm the detach operation.

    You can remove the physical disk from the host if it is no longer needed.

KVM using CLI

After you identify the disk, follow the steps below.

Steps

  1. Detach the disk from the virtual machine:

    1. Dump the configuration.

      virsh dumpxml VMNAME > /PATH/disk.xml

    2. Edit the file and remove everything except the disk to be detached from the virtual machine.

      The target address for the disk should correspond to the vmdisk-target-address field in ONTAP.

      <disk type='block' device='lun'>
  <driver name='qemu' type='raw' cache='directsync'/>
  <source dev='/dev/disk/by-id/ata- Micron_5100_MTFDDAK960TCC_171616D35277'/>
  <backingStore/>
  <target dev='sde' bus='scsi'/>
  <alias name='scsi0-0-0-4'/>
  <address type='drive' controller='0' bus='0' target='0' unit='4'/>
</disk>

    3. Detach the disk.

      virsh detach-disk --persistent /PATH/disk.xml

  2. Replace the physical disk:

    You can use a utility such as ledctl locate= to locate the physical disk if needed.

    1. Remove the disk from the host.

    2. Select a new disk and install it in the host if necessary.

  3. Edit the original disk configuration file and add the new disk.

    You should update the disk path and any other configuration information as needed.

    <disk type='block' device='lun'>
  <driver name='qemu' type='raw' cache='directsync'/>
  <source dev='/dev/disk/by-id/ata-Micron_5100_MTFDDAK960TCC_171616D35277'/>
  <backingStore/>
  <target dev='sde' bus='scsi'/>
  <alias name='scsi0-0-0-4'/>
  <address type='drive' controller='0' bus='0' target='0' unit='4'/>
</disk>
ESXi
Steps

  1. Sign in to the Deploy web user interface using the administrator account.

  2. Select the Clusters tab and select the relevant cluster.

    Node details

  3. Select + to expand the storage view.

    Edit node storage

  4. Select Edit to make changes to the attached disks and uncheck the failed drive.

    Storage disk details

  5. Provide the cluster credentials and select Edit Storage.

    ONTAP credentials

  6. Confirm the operation.

    Warning

Add the new spare drive

After you remove the failed drive, add the spare disk.

KVM using Deploy
Attaching a disk using Deploy

You can attach a disk to a KVM host as part of replacing a disk or to add more storage capacity.

Before you begin

You must have the ONTAP Select and ONTAP Select Deploy administrator account credentials.

The new disk must be physically installed on the KVM Linux host.

Steps

  1. Sign in to the Deploy utility web user interface using the administrator account.

  2. Select the Clusters tab at the top of the page and select the desired cluster from the list.

  3. Select + next to the desired HA pair or node.

    If the option is disabled, Deploy is currently refreshing the storage information.

  4. Select Edit Storage on the Edit Node Storage page.

  5. Select the disks to be attached to the node, enter the ONTAP administrator credentials, and select Edit Storage to apply the changes.

  6. Select the Events tab to monitor and confirm the attach operation.

  7. Examine the node storage configuration to confirm that the disk is attached.

KVM using CLI

After you identify and remove the failed drive, you can attach a new drive.

Steps

  1. Attach the new disk to the virtual machine.

    virsh attach-disk --persistent /PATH/disk.xml
Results

The disk is assigned as a spare and is available to ONTAP Select. It may take a minute or longer for the disk to become available.

After you finish

Because the node configuration has changed, you should perform a cluster refresh operation using the Deploy administration utility.

ESXi
Steps

  1. Sign in to the Deploy web user interface using the administrator account.

  2. Select the Clusters tab and select the relevant cluster.

    HA pair

  3. Select + to expand the storage view.

    Edit node storage

  4. Select Edit and confirm that the new drive is available and select it.

    Storage disk details

  5. Provide the cluster credentials and select Edit Storage.

    Storage disk details

  6. Confirm the operation.

    Storage disk details