VERITAS Volume Manager 4.1 Troubleshooting Guide

Error Messages
Understanding Messages
Chapter 6 79
V-5-1-123
VxVM vxconfigd ERROR V-5-1-123 Disk group group: Disabled by errors
• Description: This message indicates that some error condition has made it impossible for
VxVM to continue to manage changes to a disk group. The major reason for this is that too
many disks have failed, making it impossible for vxconfigd to continue to update
configuration copies. There should be a preceding error message that indicates the specific
error that was encountered.
If the disk group that was disabled is the boot disk group, the following additional error is
displayed:
VxVM vxconfigd ERROR V-5-1-104 All transactions are disabled
This additional message indicates that vxconfigd has entered the disabled state, which
makes it impossible to change the configuration of any disk group, not just the boot disk
group.
• Action: If the underlying error resulted from a transient failure, such as a disk cabling
error, then you may be able to repair the situation by rebooting. Otherwise, the disk group
configuration may have to be recreated by using the procedures given in “Backing Up a
Disk Group Configuration” on page 61", and the contents of any volumes restored from a
backup.
V-5-1-124
VxVM vxconfigd ERROR V-5-1-124 Disk group group: update failed: reason
• Description: I/O failures have prevented vxconfigd from updating any active copies of the
disk group configuration. This usually implies a large number of disk failures. This error
will usually be followed by the error:
VxVM vxconfigd ERROR V-5-1-123 Disk group group: Disabled by errors
• Action: If the underlying error resulted from a transient failure, such as a disk cabling
error, then you may be able to repair the situation by rebooting. Otherwise, the disk group
may have to be recreated and restored from a backup.
V-5-1-134
VxVM vxconfigd ERROR V-5-1-134 Memory allocation failure
• Description: This implies that there is insufficient memory to start VxVM.
• Action: This error should not normally occur, unless your system has very small amounts
of memory. Adding swap space will probably not help because this error is most likely to
occur early in the boot sequence, before swap areas have been added.