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

Understanding Messages
72 VERITAS Volume Manager Troubleshooting Guide
A more serious failure is indicated by errors such as:
Configuration records are inconsistent
Disk group has no valid configuration copies
Duplicate record in configuration
Format error in configuration copy
Invalid block number
Invalid magic number
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 VxVM).
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 configuration by using the procedures given in “Restoring a
Disk Group Configuration” on page 45, 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 information on how to proceed.
If those errors do not make it clear how to proceed, contact VERITAS Technical
Support.
V-5-1-571
VxVM vxconfigd ERROR V-5-1-571 Disk group group, Disk disk: Skip disk
group
with duplicate name
◆ Description: Two disk groups with the same name are tagged for auto-importing by
the same host. Disk groups are identified both by a simple name and by a long unique
identifier (disk group ID) assigned when the disk group is created. Thus, this error
indicates that two disks indicate the same disk group name but a different disk group
ID.
VxVM does not allow you to create a disk group or import a disk group from another
machine, if that would cause a collision with a disk group that is already imported.
Therefore, this error is unlikely to occur under normal use. However, this error can
occur in the following two cases: