VERITAS Volume Manager 3.5 Troubleshooting Guide (September 2004)

Error Messages

vxconﬁgd Error Messages

Chapter 3

• Description: These errors indicate that the volume cannot be started because the

volume contains no valid plexes. This can happen, for example, if disk failures have

caused all plexes to be unusable. It can also happen as a result of actions that caused

all plexes to become unusable (for example, forcing the dissociation of subdisks or

detaching, dissociation, or ofﬂining of plexes).

• Action: It is possible that this error results from a drive that failed to spin up. If so,

rebooting may ﬁx the problem. If that does not ﬁx the problem, then the only

recourse is to repair the disks involved with the plexes and restore the ﬁle system

from a backup.

vxvm:vxconfigd: ERROR: Cannot store private storage into the kernel:

error

• Description: This internal error should not occur unless there is a bug in VxVM.

• Action: Contact Customer Support.

vxvm:vxconfigd: ERROR: /dev/vx/info:

reason

• Description: The /dev/vx/info device could not be opened, or did not respond to a

Veritas Volume Manager kernel request. This error most likely indicates one of the

following:

— The VERITAS Volume Manager package installation did not complete correctly.

— The device node was removed by the administrator or by an errant shell script.

• Action: Consider re-adding the base Veritas Volume Manager package. This will

reconﬁgure the device node and re-install the Veritas Volume Manager kernel device

drivers. See the VERITAS Volume Manager 3.5 for HP-UX Release Notes for

information on how to add the package.

vxvm:vxconfigd: ERROR: DG move: can’t import diskgroup, giving up

• Description: The speciﬁed 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 Chapter 1, “Recovery from Hardware Failure,” on page 9 for

more information.

vxvm:vxconfigd: ERROR: dg_move_recover: can’t locate disk(s), giving up

• Description: Disks involved in a disk group move operation cannot be found, and one

of the speciﬁed disk groups cannot be imported.

• Action: Manual use of the vxdg recover command may be required to clean the disk

group to be imported. See Chapter 1, “Recovery from Hardware Failure,” on page 9

for more information.

vxvm:vxconfigd: ERROR: Differing version of vxconfigd installed

• Description: A vxconfd daemon was started after stopping an earlier vxconfigd

with a non-matching version number. This can happen, for example, if you upgrade

VxVM and then run vxconfigd without ﬁrst rebooting.

• Action: To ﬁx, reboot the system.