VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

Chapter 3, Error Messages
vxconfigd Error Messages
55
Evaluate the error messages to determine the root cause of the problem. Make
changes suggested by the errors and then try rerunning the command.
vxvm:vxconfigd: ERROR: Failed to store commit status list into kernel:
reason
vxvm:vxconfigd: ERROR: GET_VOLINFO ioctl failed: reason
vxvm:vxconfigd: ERROR: Get of current rootdg failed: reason
◆ Description: These internal errors should not occur unless there is a bug in VxVM.
◆ Action: Contact Customer Support.
vxvm:vxconfigd: ERROR: Memory allocation failure
◆ Description: This implies that there is insufficient memory to start VxVM.
◆ Action: This error should not normally occur, unless your system has very small
amounts of memory. Adding swap space will probably not help because this error is
most likely to occur early in the boot sequence, before swap areas have been added.
vxvm:vxconfigd: ERROR: mode: Unrecognized operating mode
◆ Description: An invalid string was specified as an argument to the -m option. Valid
strings are: enable, disable, and boot.
◆ Action: Supply a correct option argument.
vxvm:vxconfigd: ERROR: Mount point path: volume not in rootdg disk
group
◆ Description: The volume device listed in the /etc/fstab file for the given
mount-point directory (normally /usr) is listed as in a disk group other than
rootdg. This error should not occur if the standard VERITAS Volume Manager
procedures are used for encapsulating the disk containing the /usr file system.
◆ Action: Boot VxVM from a network or CD-ROM mounted root file system. Then, start
up VxVM using fixmountroot on a valid mirror disk of the root file system. After
starting VxVM, mount the root file system volume and edit the /etc/fstab file.
Change the fileto usea directpartition forthe filesystem. There should be a comment
in the /etc/fstab file that indicates which partition to use.
vxvm:vxconfigd: ERROR: No convergence between root disk group and disk
list
Disks in one version of rootdg: device type=device_type info=devinfo ...
Disks in alternate version of rootdg: device type=device_type info=devinfo
...
◆ Description: This message can appear when vxconfigd is not running in
autoconfigure mode (see the vxconfigd(1M) manual page) and after several retries
it cannot resolve the set of disks belonging to the root disk group. The algorithm for
non-autoconfigure disks scans disks listed in the /etc/vx/volboot file and then
examines the disks to find a database copy for the rootdg disk group. It next reads