VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

Chapter 3, Error Messages

Understanding Error Messages

VxVM is fault-tolerant and resolves most problems without system administrator

intervention. If the conﬁguration daemon (vxconfigd) recognizes the actions that are

necessary, it queues up the transactions that arerequired.VxVM providesatomic changes

of system conﬁgurations; either a transaction completes fully, or the system is left in the

same state as though the transaction was never attempted. If vxconfigd is unable to

recognize and ﬁx system problems, the system administrator needs to handle the task of

problem solving using the diagnostic messages that are returned from the software. The

following sections list error messages that may be seen along with a more detailed

description of the likely cause of the problem and suggestions for any actions that can be

taken.

Kernel Panic Messages

A panic is a severe event as it halts a systemduring itsnormal operation.A panicmessage

from the kernel indicates the nature of the hardware problem or software inconsistency

that is so severe that the system cannot continue. The operating system may also provide

a dumpof theCPU register contents anda stacktrace toaid in identifying the cause of the

panic.

vxvm:vxio:PANIC: Object association depth overflow

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

◆ Action: Contact Customer Support.

Kernel Warning Messages

A warning message from the kernel indicates that a non-critical operation has failed,

possibly because some resource is not available. Corrective action should be taken

immediately.

vxvm:vxio:WARNING: Cannot find device number for boot_path

◆ Description: The boot path retrieved from the system PROMs cannot be converted to a

valid device number.

◆ Action: Check your PROM settings for the correct boot string.