VERITAS Volume Manager 3.1 Reference Guide

56 Chapter2
Error Messages
Volume Manager Configuration Daemon Error Messages
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 when,
after several retries, it can not resolve the set of disks belonging to
the root disk group. The algorithm for non-autoconfigure disks is to
scan disks listed in the /etc/vx/volboot file and then examine the
disks to find a database copy for the rootdg disk group. The database
copy is then read to find the list of disk access records for disks
contained in the group. These disks are then examined to ensure that
they contain the same database copy. As such, this algorithm expects
to gain convergence on the set of disks and the database copies
contained on them. If a loop is entered and convergence cannot be
reached, then this message will appear and the root disk group
importation will fail.
• Action
Reorganizing the physical locations of the devices attached to the
system may break the deadlock. Failing this, contact Customer
Support.
Open of directory failed
vxvm:vxconfigd: ERROR: Open of directory directory
failed: reason
• Description
An open failed for the /dev/vx/dsk or /dev/vx/rdsk directory (or a
subdirectory of either of those directories). The only likely cause of
such a failure should be that the directory was removed by the
administrator or by an errant program. For this case, the reason
should be “No such file or directory.” An alternate possible
cause is an I/O failure.
• Action
If the error was “No such file or directory,” then create the
directory (using mkdir). Then run the command vxdctl enable.
If the error was an I/O error, then there may be other serious damage
to the root file system. You may need to reformat your root disk and