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

Understanding Messages
70 VERITAS Volume Manager Troubleshooting Guide
poorly-attached 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, VERITAS Volume Manager 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.
V-5-1-554
VxVM vxconfigd WARNING V-5-1-554 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.
V-5-1-557
VxVM vxconfigd ERROR V-5-1-557 Disk disk, group group, device device:
not updated with new host ID
Error: reason
◆ Description: This can result from using vxdctl hostid to change the VERITAS
Volume Manager host ID for the system. The error indicates that one of the disks in a
disk group could not be updated with the new host ID. This usually indicates that the
disk has become inaccessible or has failed in some other way.
◆ Action: Try running the following command to determine whether the disk is still
operational:
# vxdisk check device
If the disk is no longer operational, vxdisk should print a message such as:
device: Error: Disk write failure