What to do if creating a recovery group or adding a node command fails

This topic describes the steps that you need to take when the command for creating a recovery group or adding a node fails.

Note: The following error messages on checking slot location string are supported from 5.0.5.4 release.
When you use the installation toolkit or mmvdisk command to create a recovery group or add a node to the recovery group, you might get one of the following error messages:
  • Error message: mmvdisk: Recovery group descriptor for pdisk n014p013 of recovery group rg_2 could not be written because volatile write caching is enabled on this drive.

    Interpretation: This error message indicates that volatile write cache is enabled on the drive.

    What action needs to be taken: Check the write cache of the drives on each node and create a recovery group again after you disable the volatile write cache. For more information, see Hardware checklist.

  • Error messages: mmvdisk: Slot location is missing from pdisk n003p013 device(s) //client23-ib0/dev/nvme0n1 of declustered array DA2 in recovery group rg1 with hardware type NVMe.

    Interpretation: This error message indicates that the slot location is missing for NVMe drive.

    What action needs to be taken: Check the NVMe drive slot location with the tslsenclslot command and make any corrections if needed. For more information, see Mapping NVMe disk slot location.

  • Error messages: mvdisk: Slot location is missing from pdisk n015p012 device(s) //client28-ib0/dev/sds of declustered array DA1 in recovery group rg_2 with hardware type Rotating 10500

    Interpretation: This error message indicates that the slot location is missing for SAS drive.

    What action needs to be taken: Check for any missing or duplicated slot location string with the tslsenclslot command and make any corrections if needed. For more information, see Mapping LMR disk location.
    Note: If the disk is not listed in the tslsenclslot -a command, proceed as follows: