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

Chapter 6, Error Messages

Understanding Messages

This will result in the disk being taken out of active use in its disk group, if it has not

already been taken out of use. If the disk is still operational, which should not be the

case, vxdisk prints:

device: Okay

If the disk is listed as “Okay,” try running vxdctl hostid again. If it still results in

an error, contact VERITAS Technical Support.

V-5-1-568

VxVM vxconfigd WARNING V-5-1-568 Disk group group is disabled, disks

not updated with new host ID

◆ Description: As a result of failures, the named disk group has become disabled. Earlier

error messages should indicate the cause. This message indicates that disks in that

disk group were not updated with a new VERITAS Volume Manager host ID. This

warning message should result only from a vxdctl hostid operation.

◆ Action: Typically, unless a disk group was disabled due to transient errors, there is no

way to repair a disabled disk group. The disk group may have to be reconstructed

from scratch. If the disk group was disabled due to a transient error such as a cabling

problem, then a future reboot may not automatically import the named disk group,

due to the change in the system’s VERITAS Volume Manager host ID. In such a case,

import the disk group directly using vxdg import with the -C option.

V-5-1-569

VxVM vxconfigd ERROR V-5-1-569 Disk group group,Disk disk:Cannot

auto-import group: reason

◆ 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 V-5-1-579 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 VxVM 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.