The volboot file will be re-initialized during boot if the /etc/vx/reconfig.d/state.d/install-db file exists in VERITAS Volume Manager (tm) 3.1.1 with patch02 or patch03.
vxvm:vxconfigd: ERROR: enable failed: Error in disk group configuration copies Rootdg disk group has no configuration copies; transactions are disabled. vxvm:vxdctl: ERROR: enable failed: Error in disk group configuration copies
install-db file exists in the
/etc/vx/reconfig.d/state.d directory, Volume Manager will be disabled during boot. Volume Manager can be re-enabled during boot by removing the
install-db file in the
In Volume Manager 3.1.1 with patch02 or patch03, if
/etc/vx/reconfig.d/state.d/install-db exists, the Volume Manager boot file,
/etc/vx/volboot, will be re-initialized. If any simple disk is included in rootdg, Volume Manager can not be started properly even if the file
install-db is removed. This problem only occurred in Volume Manager 3.1.1 with patch02 or patch03, and the Volume Manager 3.1.1 Japanese version.
NOTE: This problem does not occur in Volume Manager 3.1.1 without patches and Volume Manager 3.2.
/etc/vx/reconfig.d/state.d/install-db file is created, an error message will not be displayed during the boot process. But, after the machine boots up, running the
vxdctl enable command to enable the
vxconfigd daemon will generate an error message as shown below:
# vxdctl enable vxvm:vxconfigd: ERROR: enable failed: Error in disk group configuration copies Rootdg disk group has no configuration copies; transactions are disabled. vxvm:vxdctl: ERROR: enable failed: Error in disk group configuration copies
If simple disks are used in Volume Manager, run the following command to re-add all simple disk entries to the
volboot file in order to re-enable the
vxconfigd daemon. If more than one simple disk is used in Volume Manager, repeat the command until all of the simple disk entries have been added.
# vxdctl add disk <device>
If no simple disks are used in Volume Manager, then the above step is not necessary. If the prior Volume Manager host ID was different than the operating system host name, it must run the following command to change the Volume Manager host ID, which is saved in the
volboot file, to get Volume Manager started properly.
# vxdctl hostid <oldhostid>
vxconfigd can be re-enabled by executing the following commands:
# vxdctl -k stop # vxconfigd -d # vxdctl enable
To fix the problem permanently, apply the following solution after installing the patch, but before reboot, to avoid the problem. If the problem has already occurred, apply the solution after recovering the volboot file using the steps above.
1. Find the following lines in the startup script
/etc/init.d/vxvm-reconfig in line 165 to 171:
165> if [ -f $mkdbfile ]; then
166> xcmd vxiod set 10
167> xcmd $VOLD -k -r reset -m disable
168> xcmd vxdctl init
169> xcmd vxdctl initdmp
170> xcmd vxdg init rootdg
2. Find the following line in line 222:
222> [ -f $reconfigfile ] || exit 0
3. Move the lines in step 1 to appear below the line in step 2
4. The modified
vxvm-reconfig file will appear as shown below: