VERITAS Volume Manager 3.5 Troubleshooting Guide (September 2004)
Error Messages
vxconfigd Error Messages
Chapter 3
69
• 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 an I/O failure on the root
file 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.
vxvm:vxconfigd: ERROR: Unexpected configuration tid for group
group
found
in kernel
vxvm:vxconfigd: ERROR: Unexpected error during volume
volume
reconfiguration:
reason
vxvm:vxconfigd: ERROR: Unexpected error fetching disk for disk volume:
reason
vxvm:vxconfigd: ERROR: Unexpected values stored in the kernel
• Description: These internal errors should not occur unless there is a bug in VxVM.
• Action: Contact Customer Support.
vxvm:vxconfigd: ERROR: Version number of kernel does not match vxconfigd
• Description: The release of vxconfigd does not match the release of the Veritas
Volume Manager kernel drivers. This should happen only as a result of upgrading
VxVM, and then running vxconfigd without a reboot.