Error Message

Possible error message found in the System Event Log:

V-204-57344-6 
vxboot: Failed to auto-import disk group <DG_Name>. All volumes in the disk group are not available

or

vxboot: dg_import_finish: Setting the in-core pending tid as xxxx

Note: If either of these errors are seen, please follow the steps in the Solution section (Enabling Diskgroup for Delayed Import)
 

Clustered Diskgroups do not auto-import at startup when configured as the cluster software (VCS, Windows Failover Cluster) needs to be in control of these diskgroups. For example, if the diskgroup ClusDG is imported (online) on Node2 of a cluster and Node1 is rebooted, the ClusDG Diskgroup should not attempt to auto-import on startup. The cluster software needs to control all resources in the cluster, including the Volume Manager Diskgroup (VMDg) resource.

From a command prompt, run command: vxdg list, and ensure that the ‘Diskgroup Type’ is listed as Dynamic (Secondary):

If ‘Disk Group Type’ shows as: Dynamic (Cluster), the software assumes this Diskgroup is controlled by the cluster, hence it will not auto-import.

- If a Secondary Diskgroup is deported and the server is rebooted, the Diskgroup will not auto-import as it keeps the Diskgroup in its last known state. In these instances, it will be necessary to manually import the diskgroup through VEA or from the command line.

- If imported Secondary Diskgroups do not auto-import during system startup, and no vxboot messages are seen in the System Event Log, it is possible the vxboot driver was not properly installed. In these cases, it is recommended to perform the steps to reinstall the vxboot driver which can be found in the following technical article:

https://isearch.veritas.com/internal-search/en_US/article.100009335.html
 

If the Diskgroup is NOT part of a cluster but is mistakenly configured as a Dynamic (Cluster) Diskgroup, it must be converted to the 'Disk Group Type': Dynamic (Secondary). Follow the steps below to implement this change:

1. If the Diskgroup is currently imported, deport the Diskgroup from within VEA, or by running command: vxdg -g deport (Ex: vxdg -g DG1 deport)

2. Import the Diskgroup using the -d option to convert to Dynamic (Secondary): vxdg -g -d import (Ex: vxdg -g DG1 -d import)

3. Run command: vxdg list, and confirm the Diskgroup is now showing as Dynamic (Secondary).

4. Ensure the Diskgroup is imported during the next reboot, and it should now auto-import at system startup.

If the Diskgroup is configured as Dynamic (Secondary), and vxboot errors are reported to System Event Log, the issue is that not all of the disks are available at the time the software attempts to import the Diskgroup (via the vxboot driver). Enabling ‘LateStart’ should resolve this issue. Follow the steps below to implement this option:

Note: There are different steps for SFW 6.x and InfoScale 7.x
 

Storage Foundation for Windows (SFW) 6.x:

The vxdg command includes a LateStart option which can be used to enable (on) and disable (off) the LateStart feature. Perform the following steps. For InfoScale for Windows products, see the next section on implementing this change.

1. Open a command prompt (Run as Administrator)

2. Run command: vxdg -g <DG_name> latestart on (ex: vxdg -g DG1 latestart on).

3. Repeat Step 2 for all Secondary Diskgroups that should auto-import.

4. During the next reboot, as long as the Diskgroup is imported, it will auto-import at system startup.
 

InfoScale 7.x:

The vxdg command no longer includes the LateStart option; therefore, the registry entry needs to be created manually. Perform the following steps to enable LateStart with the InfoScale product:

1. From a command prompt, run the command vxdg list, and copy the Disk Group ID value as this will be needed.

2. Open the Registry Editor (start > run > regedit), and browse to the following registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vxio\Late Start

3. Right-click on the ‘Late Start’ key > New > Key

4. Name the key the ‘DiskGroup ID’ value from Step 1.

5. Perform the same steps for each Secondary Diskgroup that needs to auto-import at system startup.

6. During the next reboot, as long as the Diskgroup is imported, it will auto-import at system startup.