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

Understanding Messages
74 VERITAS Volume Manager Troubleshooting Guide
◆ Action: If some of the copies failed due to transient errors (such as cable failures), then
a reboot or re-import may succeed in importing the disk group. Otherwise, the disk
group configuration may have to be restored. You can recreate a disk group
configuration by using the procedures given in “Restoring a Disk Group
Configuration” on page 45
V-5-1-583
VxVM vxconfigd ERROR V-5-1-583 Disk group group: Reimport of disk group
failed: reason
◆ Description: After vxconfigd was stopped and restarted (or disabled and then
enabled), VxVM failed to recreate the import of the indicated disk group. The reason
for failure is specified. Additional error messages may be displayed that give further
information describing the problem.
◆ Action: A major cause for this kind of failure is disk failures that were not addressed
before vxconfigd was stopped or disabled. If the problem is a transient disk failure,
then rebooting may take care of the condition. The error may be accompanied by
messages such as ‘‘Disk group has no valid configuration copies.’’ This indicates that
the disk group configuration copies have become corrupt (due to disk failures,
writing on the disk by an application or the administrator, or bugs in VxVM). You can
recreate a disk group configuration by using the procedures given in “Restoring a
Disk Group Configuration” on page 45.
V-5-1-587
VxVM vxdg ERROR V-5-1-587 disk group groupname: import failed: reason
◆ Description: The import of a disk group failed for the specified reason.
◆ Action: The action to be taken depends on the reason given in the error message:
Disk is in use by another host
No valid disk found containing disk group
The first message indicates that disks have been moved from a system that has
crashed or that failed to detect the group before the disk was moved. The locks stored
on the disks must be cleared.
The second message indicates that the disk group does not contain any valid disks
(not that it does not contain any disks). The disks may be considered invalid due to a
mismatch between the host ID in their configuration copies and that stored in the
/etc/vx/volboot file.
To clear locks on a specific set of devices, use the following command:
# vxdisk clearimport devicename ...