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

Chapter 6, Error Messages

Understanding Messages

V-5-1-3828

VxVM vxconfigd ERROR V-5-1-3828 upgrade operation failed: Already at

highest version

◆ Description: An upgrade operation has failed because a cluster is already running at

the highest protocol version supported by the master.

◆ Action: No further action is possible as the master is already running at the highest

protocol version it can support.

V-5-1-3848

VxVM vxconfigd ERROR V-5-1-3848 Incorrect protocol version (number) in

volboot file

◆ Description: A node attempted to join a cluster where VxVM software was incorrectly

upgraded or the volboot file is corrupted, possibly by being edited manually. The

volboot file should contain a supported protocol version before trying to bring the

node into the cluster.

◆ Action: Verify the supported cluster protocol versions using the vxdctl

protocolversion command. The volboot file should contain a supported

protocol version before trying to bring the node into the cluster. Run vxdctl init to

write a valid protocol version to the volboot file. Restart vxconfigd and retry the

join.

V-5-1-4220

VxVM vxconfigd ERROR V-5-1-4220 DG move: can’t import diskgroup,

giving up

◆ Description: The specified disk group cannot be imported during a disk group move

operation. (The disk group ID is obtained from the disk group that could be

imported.)

◆ Action: The disk group may have been moved to another host. One option is to locate

it and use the vxdg recover command on both the source and target disk groups.

Specify the -o clean option with one disk group, and the -o remove option with the

other disk group. See “Recovering from Incomplete Disk Group Moves” on page 18

for more information.