VERITAS Volume Manager 3.1 Reference Guide

Chapter 2 49
Error Messages
Volume Manager Configuration Daemon Error Messages
• Description
On system startup, vxconfigd failed to import the disk group
associated with the named disk. A message related to the specific
failure is given in reason . Additional error messages may be
displayed that give more information on the specific error. In
particular, this is often followed by:
vxvm:vxconfigd: ERROR: Disk group group: Errors in
some
configuration copies: Disk device , copy number : Block
bno : error ...
The most common reason for auto-import failures is excessive
numbers of disk failures, making it impossible for the Volume
Manager to find correct copies of the disk group configuration
database and kernel update log. Disk groups usually have enough
copies of this configuration information to make such import failures
unlikely.
A more serious failure is indicated by error types of:
Format error in configuration copy
Invalid magic number
Invalid block number
Duplicate record in configuration
Configuration records are inconsistent
These errors indicate that all configuration copies have become
corrupt (due to disk failures, writing on the disk by an application or
the administrator, or bugs in the Volume Manager).
Some correctable errors may be indicated by other error messages
that appear in conjunction with the auto-import failure message.
Look up those other errors for more information on their cause.
Failure of an auto-import implies that the volumes in that disk group
will not be available for use. If there are file systems on those
volumes, then the system may yield further errors resulting from
inability to access the volume when mounting the file system.
• Action
If the error is clearly caused by excessive disk failures, then you may
have to recreate the disk group and restore contents of any volumes
from a backup. There may be other error messages that appear which
provide further information. See those other error messages for more