VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

vxconfigd Error Messages
56 VERITAS Volume Manager Troubleshooting Guide
the database copy 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. The algorithm expects to gain convergence on the set of disks and on the
database copies that they contain. If a loop is entered and convergence cannot be
reached, this message is displayed and the root disk group importation fails.
◆ Action: Reorganize the physical locations of the devices attached to the system to try
and break the deadlock. If this does not succeed, contact Customer Support.
vxvm:vxconfigd: ERROR: Open of directory directory failed: reason
◆ Description: An open failed for /dev/vx/dsk, /dev/vx/rdsk, or one of their
subdirectories. The only likely cause of such a failure is that the directory was
removed by the administrator or by an errant program. If this is the case, the reason
should be “No such file or directory.” An alternate possible cause is an I/O failure.
◆ Action: If the reason was “No such file or directory,” use mkdir to recreate the
directory. Then run the command vxdctl enable.
If the error was an I/O error, there may be other serious damage to the root file
system. You may need to reformat your root disk and restore the root file system
from backup. Contact your system vendor or consult your system documentation.
vxvm:vxconfigd: ERROR: Read of directory directory failed: reason
◆ Description: There was a failure in reading /dev/vx/dsk, /dev/vx/rdsk, or one of
their subdirectories. The only likely cause of this error is anI/O failure on the rootfile
system.
◆ Action: 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 restore the root file
system from backup. Contact your system vendor or consult your system
documentation.
vxvm:vxconfigd: ERROR: signal [ - core dumped ]
◆ Description: The vxconfigd daemon encountered an unexpected signal while
starting up. If the signal caused the vxconfigd process to dump core, then that will
be indicated. This could be caused by a bug in vxconfigd, particularly if signal is
“Segmentation fault.” Alternately, this could have been caused by a user sending
vxconfigd a signal with the kill utility.
◆ Action: Contact Customer Support.
vxvm:vxconfigd: ERROR: System startup failed
◆ Description: Either the root or the /usr file system volume could not be started,
rendering the system unusable. The error that resulted in this condition should
appear prior to this error message.
◆ Action: Look up other error messages appearing on the console and take the actions
suggested in the descriptions of those messages.