Veritas Volume Manager 5.0 Troubleshooting Guide Guide (September 2006)

82 Error messages
Understanding messages
V-5-1-2198
VxVM vxconfigd ERROR V-5-1-2198 node N: vxconfigd not ready
■ Description: The vxconfigd daemon is not responding properly in a cluster.
■ Action: Stop and restart the vxconfigd daemon on the node indicated.
V-5-1-2274
VxVM vxconfigd ERROR V-5-1-2274 volume:vxconfigd cannot boot-start
RAID-5 volumes
■ Description: A volume that vxconfigd should start immediately upon booting the
system (that is, the volume for the /usr file system) has a RAID-5 layout. The /
usr file system should never be defined on a RAID-5 volume.
■ Action: It is likely that the only recovery for this is to boot VxVM from a network-
mounted root file system (or from a CD-ROM), and reconfigure the /usr file
system to be defined on a regular non-RAID-5 volume.
V-5-1-2290
VxVM vxdmpadm ERROR V-5-1-2290 Attempt to enable a controller that
is not available
■ Description: This message is returned by the vxdmpadm utility when an attempt is
made to enable a controller that is not working or is not physically present.
■ Action: Check hardware and see if the controller is present and whether I/O can be
performed through it.
V-5-1-2353
VxVM vxconfigd ERROR V-5-1-2353 Disk group group: Cannot recover temp
database: reason
Consider use of "vxconfigd -x cleartempdir" [see vxconfigd(1M)].
■ Description: This can happen if you kill and restart vxconfigd, or if you disable
and enable it with vxdctl disable and vxdctl enable. This error indicates a
failure related to reading the file /var/vxvm/tempdb/group. This is a
temporary file used to store information that is used when recovering the state of an
earlier vxconfigd. The file is recreated on a reboot, so this error should never
survive a reboot.
■ Action: If you can reboot, do so. If you do not want to reboot, then do the following:
1 Ensure that no vxvol, vxplex, or vxsd processes are running.
Use ps -e to search for such processes, and use kill to kill any that you find.
You may have to run kill twice to make these processes go away. Killing