Veritas Volume Manager 5.0.1 Troubleshooting Guide, HP-UX 11i v3, First Edition, November 2009

Recommended action:
Use the vxdisk -s list command on the master node to see what disks should
be visible to the slave node. Then check that the operating system and VxVM on
the failed node can also see these disks. If the operating system cannot see the
disks, check the cabling and hardware configuration of the node. If only VxVM
cannot see the disks, use the vxdctl enable command to make it scan again for
the disks. When the disks are visible to VxVM on the node, retry the join.
V-5-0-166
VxVM vxio WARNING V-5-0-166 Failed to log the detach of the DRL volume
volume
Description:
An attempt failed to write a kernel log entry indicating the loss of a DRL volume.
The attempted write to the log failed either because the kernel log is full, or because
of a write error to the drive. The volume becomes detached.
Recommended action:
Messages about log failures are usually fatal, unless the problem is transient.
However, the kernel log is sufficiently redundant that such errors are unlikely to
occur.
If the problem is not transient (that is, the drive cannot be fixed and brought back
online without data loss), recreate the disk group from scratch and restore all of
its volumes from backups. Even if the problem is transient, reboot the system
after correcting the problem.
If error messages are seen from the disk driver, it is likely that the last copy of
the log failed due to a disk error. Replace the failed drive in the disk group. The
log re-initializes on the new drive. Finally force the failed volume into an active
state and recover the data.
V-5-0-168
VxVM vxio WARNING V-5-0-168 Failure in RAID-5 logging operation
Description:
Indicates that a RAID-5 log has failed.
Recommended action:
To restore RAID-5 logging to a RAID-5 volume, create a new log plex and attach
it to the volume.
71Error messages
Types of messages