Veritas Volume Manager 4.1 Troubleshooting Guide (HP-UX 11i v3, February 2007)

Understanding Messages
80 VERITAS Volume Manager Troubleshooting Guide
◆ Action: This error can result from a kernel error that has made the configuration
daemon process unkillable, from some other kind of kernel error, or from some other
user starting another configuration daemon process after the SIGKILL signal. This
last condition can be tested for by running vxconfigd -k again. If the error message
reappears, contact VERITAS Technical Support.
V-5-1-2197
VxVM vxconfigd ERROR V-5-1-2197 node N: missing vxconfigd
◆ Description: The vxconfigd daemon is not running on the indicated cluster node.
◆ Action: Restart the vxconfigd daemon.
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.