VERITAS Volume Manager 3.5 Troubleshooting Guide (September 2004)

Error Messages
vxconfigd Warning Messages
Chapter 3
73
cable, or from a disk that fails to spin up fast enough. Alternately, this may happen
as a result of a disk being physically removed from the system, or from a disk that
has become unusable due to a head crash or electronics failure.
Any RAID-5 plexes, DRL log plexes, RAID-5 subdisks or mirrored plexes containing
subdisks on this disk are unusable. Such disk failures (particularly on multiple
disks) may cause one or more volumes to become unusable.
• Action: If hot-relocation is enabled, 3.5 objects affected by the disk failure are taken
care of automatically. Mail is sent to root indicating what actions were taken by
VxVM and what further actions the administrator should take.
vxvm:vxconfigd: WARNING: Disk disk in kernel is not a recognized type
• Description: This internal error should not occur unless there is a bug in VxVM.
• Action: Contact Customer Support.
vxvm:vxconfigd: WARNING: Disk disk names group group, but group ID
differs
• Description: As part of a disk group import, a disk was discovered that had a
mismatched disk group name and disk group ID. This disk is not imported. This can
only happen if two disk groups have the same name but have different disk group ID
values. In such a case, one group is imported along with all its disks and the other
group is not. This message appears for disks in the un-selected group.
• Action: If the disks should be imported into the group, this must be done by adding
the disk to the group at a later stage, during which all configuration information for
the disk is lost.
vxvm:vxconfigd: WARNING: Disk group group: Disk group log may be too
small
Log size should be at least number blocks
• Description: The log areas for the disk group have become too small for the size of
configuration currently in the group. This message only occurs during disk group
import; it can only occur if the disk was inaccessible while new database objects were
added to the configuration, and the disk was then made accessible and the system
restarted. This should not normally happen without first displaying a message about
the database area size.
• Action: Reinitialize the disks in the group with larger log areas. Note that this
requires that you restore data on the disks from backups. See the vxdisk(1M)
manual page. To reinitialize all of the disks, detach them from the group with which
they are associated, reinitialize and re-add them. Then deport and re-import the disk
group to effect the changes to the log areas for the group.
vxvm:vxconfigd: WARNING: Disk group group: Errors in some configuration
copies: Disk disk, copy number: [Block number]: reason ...
• Description: During a disk group import, some of the configuration copies in the
named disk group were found to have format or other types of errors which make
those copies unusable. This message lists all configuration copies that have
uncorrected errors, including any appropriate logical block number.
• Action: There are usually enough configuration copies in any disk group to ensure
that such errors do not become a serious problem. No action is usually necessary.
vxvm:vxconfigd: WARNING: Disk group group is disabled, disks not updated
with new host ID