VERITAS Volume Manager 3.1 Reference Guide

48 Chapter2
Error Messages
Volume Manager Configuration Daemon Error Messages
A vxconfigd daemon was started after the stopping of an earlier
vxconfigd with a non-matching version number. This can happen,
for example, if you upgrade from an earlier release of Volume
Manager to VxVM 3.0 and run vxconfigd without a reboot.
• Action
To fix, reboot the system.
Disk, group, device: not updated with new host ID
vxvm:vxconfigd: ERROR: 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 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. Most
likely, this indicates that the given disk has become inaccessible or
has failed in some other way.
• Action
Try running the following 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
This will result in the disk being taken out of active use in its disk
group, if it has not been taken out of use already. If the disk is still
operational (which should not be the case), vxdisk will print:
device : Okay
If the disk is listed as Okay, try vxdctl hostid again. If it still results
in an error, contact Customer Support.
Disk group, Disk: Cannot auto-import group
vxvm:vxconfigd: ERROR: Disk group group , Disk disk :
Cannot auto-import group: reason