Volume Manager dynamic Diskgroups fail to auto-import during system startup; however, the diskgroups can be manually imported after the server has started.

Article:TECH143003  |  Created: 2010-10-29  |  Updated: 2012-07-28  |  Article URL http://www.symantec.com/docs/TECH143003
Article Type
Technical Solution

Product(s)

Environment

Issue



Volume Manager Diskgroups fail to auto-import during system startup in Veritas Storage Foundation for Windows (SFW); however, the diskgroups can be manually imported after the server has started. This is generally seen following a server reboot and results in the diskgroups having to be manually imported.


Error



System event log Event ID 6 (vxboot): Failed to auto-import disk group %2.  All volumes in the disk group are not available.


Cause



This behavior can occur for various reasons:

1. Diskgroups that are clustered will NOT auto-import when a system starts up. Ensure that any Diskgroup you want to be automatically imported is configured as Secondary (non-clustered). This can be determined by right-clicking on the Diskgroup in the Veritas Enterprise Administrator (VEA) and verifying the 'Type' is: Dynamic (Secondary).

2. Vxboot should not try to import cluster disk groups automatically as they are under cluster control and will be imported on cluster request. If you see this message regarding a Cluster Disk Group please locate and delete the corresponding Registry key under HKEY_LOCAL_MACHINE Subkey:SYSTEM\CurrentControlSet\Services\vxio\Boot Info. The disk groups configured for auto-import are listed in subkeys called "Disk Group 1,2,3,etc" having the disk group name in the "Name" value. Once you found the right group please make sure you delete the whole subkey "Disk Group X"

2. When the vxboot service is initiated at system startup to auto-import diskgroups, at least 50% of the disks are unavailable/unreadable by SFW which results in our failure to import the Diskgroups. If all of the disks that make up the diskgroup are unavailable, no errors will be seen; however, if some disks are accessible (50% or less), the Diskgroup will fail to import and the following message will be logged to the Event Log:

vxboot: Failed to auto-import disk group <diskgroup>. All volumes in the disk group are not available

In addition, the following error may also be logged to the %vmpath%\vm_vxisis.log in SFW 5.x and later versions:

FSYS:get_os_fs_info - can't open device \Device\<device path>, status=0xc000003a

*0xc000003a = STATUS_OBJECT_PATH_NOT_FOUND


Solution



Use the Delayed Import Service to move the Storage Foundation disk group imports further along in the boot-up process. This will allow the disks more time to arrive before SFW attempts to import the diskgroups which should allow for a successful auto-import. It is important to note that even with this added delay, diskgroups will be imported before any user level services/applications attempt to start, so there will be no negative impact by enabling this feature.

To Enable a diskgroup for 'Delayed Import', perform the following step:

1. From a Windows command prompt, type the following: vxdg -g<disk_group> latestart on

* Replace <diskgroup> with the name of the actual diskgroup. If the DG name was DG1, the command would be: vxdg -gDG1 latestart on

Note: This command must be run for all diskgroups that are encountering this issue.


If the need arises to disable the late start functionality for a diskgroup in the future, the following command can be run: vxdg -g<diskgroup> latestart off


Legacy ID



357294


Article URL http://www.symantec.com/docs/TECH143003


Terms of use for this information are found in Legal Notices