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

Understanding Messages
90 VERITAS Volume Manager Troubleshooting Guide
V-5-1-3243
VxVM vxdmpadm ERROR V-5-1-3243 The VxVM restore daemon is already
running. You can stop and restart the restore daemon with desired
arguments for changing any of its parameters.
◆ Description: The vxdmpadm start restore command has been executed while the
restore daemon is already running.
◆ Action: Stop the restore daemon and restart it with the required set of parameters as
shown in the vxdmpadm(1M) manual page.
V-5-1-3362
VxVM vxdmpadm ERROR V-5-1-3362 Attempt to disable controller failed.
One (or more) devices can be accessed only through this controller.
Use the -f option if you still want to disable this controller.
◆ Description: Disabling the controller could lead to some devices becoming
inaccessible.
◆ Action: To disable the only path connected to a disk, use the -f option.
V-5-1-3486
VxVM vxconfigd ERROR V-5-1-3486 Not in cluster
◆ Description: Checking for the current protocol version (using vxdctl protocol
version) does not work if the node is not in a cluster.
◆ Action: Bring the node into the cluster and retry.
V-5-1-3689
VxVM vxassist ERROR V-5-1-3689 Volume record id rid is not found in the
configuration.
◆ Description: An error was detected while reattaching a snapshot volume using
snapback. This happens if a volume’s record identifier (rid) changes as a result of a
disk group split that moved the original volume to a new disk group. The snapshot
volume is unable to recognize the original volume because its record identifier has
changed.
◆ Action: Use the following command to perform the snapback:
# vxplex [-g diskgroup] -f snapback volume plex