Messages

This section contains a list of messages that you may encounter during the operation of VERITAS Volume Manager. However, the list is not exhaustive and the second field may contain the name of different command, driver or module from that shown here.

If you encounter a product error message, record the unique message number preceding the text of the message. When contacting VERITAS Technical Support, either by telephone or by visiting the VERITAS Technical Support website, be sure to provide the relevant message number. VERITAS Technical Support will use this message number to quickly determine if there are TechNotes or other information available for you.

V-5-0-2

• Description: A read or write operation from or to the specifiedVERITAS Volume Manager object failed. An error is returned to the application.
• Action: These errors may represent lost data. Data may need to be restored and failed media may need to be repaired or replaced. Depending on the type of object failing and on the type of recovery suggested for the object type, an appropriate recovery operation may be necessary.

V-5-0-4

• Description: An uncorrectable error was detected by the mirroring code and a mirror copy was detached.
• Action: To restore redundancy, it may be necessary to add another mirror. The disk on which the failure occurred should be reformatted or replaced.

---

  Note    This message may also appear during a plex detach operation in a cluster. In this case, no action is required.

---

V-5-0-34

• Description: A new disk array has been added to the host.
• Action: None.

V-5-0-35

• Description: An attempt is being made to disable the one remaining active path to the root disk controller.
• Action: The path cannot be disabled.

V-5-0-55

• Description: The boot path retrieved from the system PROMs cannot be converted to a valid device number.
• Action: Check your PROM settings for the correct boot string.

V-5-0-106

• Description: Either a double-failure condition in the RAID-5 volume has been detected in the kernel or some other fatal error is preventing further use of the array.
• Action: If two or more disks have been lost due to a controller or power failure, use the vxrecover utility to recover them once they have been re-attached to the system. Check for other console error messages that may provide additional information about the failure.

V-5-0-108

• Description: A close was received for an object that was not open. This can only happen if the operating system is not correctly tracking opens and closes.
• Action: No action is necessary; the system will continue.

V-5-0-110

• Description: All paths through the controller connected to the disk array are disabled. This usually happens if a controller is disabled for maintenance.
• Action: None.

V-5-0-111

• Description: A DMP node has been marked disabled in the DMP database. It will no longer be accessible for further IO requests. This occurs when all paths controlled by a DMP node are in the disabled state, and therefore inaccessible.
• Action: Check hardware or enable the appropriate controllers to enable at least one path under this DMP node.

V-5-0-112

• Description: A path has been marked disabled in the DMP database. This path is controlled by the DMP node indicated by the specified device number. This may be due to a hardware failure.
• Action: Check the underlying hardware if you want to recover the desired path.

V-5-0-144

• Description: I/O errors have been received in more than one column of a RAID-5 volume. This could be caused by:
• a controller failure making more than a single drive unavailable
• the loss of a second drive while running in degraded mode
• two separate disk drives failing simultaneously (unlikely)
• Action: Correct the hardware failures if possible. Then recover the volume using the vxrecover command.

V-5-0-145

• Description: A Dirty Region Logging volume became detached because a DRL log entry could not be written. If this is due to a media failure, other errors may have been logged to the console.
• Action: The volume containing the DRL log continues in operation. If the system fails before the DRL has been repaired, a full recovery of the volume's contents may be necessary and will be performed automatically when the system is restarted. To recover from this error, use the vxassist addlog command to add a new DRL log to the volume.

V-5-0-146

• Description: All paths through the controller connected to the disk array are enabled. This usually happens if a controller is enabled after maintenance.
• Action: None.

V-5-0-147

• Description: A DMP node has been marked enabled in the DMP database. This happens when at least one path controlled by the DMP node has been enabled.
• Action: None.

V-5-0-148

• Description: A path has been marked enabled in the DMP database. This path is controlled by the DMP node indicated by the specified device number. This happens if a previously disabled path has been repaired, the user has reconfigured the DMP database using the vxdctl(1M) command, or the DMP database has been reconfigured automatically.
• Action: None.

V-5-0-164

• Description: A node failed to join a cluster. This may be caused by the node being unable to see all the shared disks. Other error messages may provide more information about the disks that cannot be found.
• 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

• 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.
• 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

• Description: Indicates that a RAID-5 log has failed.
• Action: To restore RAID-5 logging to a RAID-5 volume, create a new log plex and attach it to the volume.

V-5-0-181

• Description: An attempt was made to open a volume device before vxconfigd loaded the volume configuration.
• Action: None; under normal startup conditions, this message should not occur. If necessary, start VxVM and re-attempt the operation.

V-5-0-194

• Description: A plex detach failed because the kernel log was full. As a result, the mirrored volume will become detached.
• Action: It is unlikely that this condition ever occurs. The only corrective action is to reboot the system.

V-5-0-196

• Description: Detaching a plex failed because the kernel log could not be flushed to disk. As a result, the mirrored volume became detached. This may be caused by all the disks containing a kernel log going bad.
• Action: Repair or replace the failed disks so that kernel logging can once again function.

V-5-0-207

• Description: Indicates that a RAID-5 log has failed.
• Action: To restore RAID-5 logging to a RAID-5 volume, create a new log plex and attach it to the volume.

V-5-0-216

• Description: A call made to the operating system mod_install function to load the vxio driver failed.
• Action: Check for additional console messages that may explain why the load failed. Also check the console messages log file for any additional messages that were logged but not displayed on the console.

V-5-0-237

• Description: A subdisk was detached from a RAID-5 volume because of the failure of a disk or an uncorrectable error occurring on that disk.
• Action: Check for other console error messages indicating the cause of the failure. Replace a failed disk as soon as possible.

V-5-0-243

• Description: An error has occurred on the last complete plex in a mirrored volume. Any sparse mirrors that map the failing region are detached so that they cannot be accessed to satisfy that failed region inconsistently.
• Action: The message indicates that some data in the failing region may no longer be stored redundantly.

V-5-0-244

• Description: A path under the control of the DMP driver failed. The device major and minor numbers of the failed device is supplied in the message.
• Action: None.

V-5-0-249

• Description: An uncorrectable error has forced a subdisk to detach. At this point, not all data disks exist to provide the data upon request. Instead, parity regions are used to regenerate the data for each stripe in the array. Consequently, access takes longer and involves reading from all drives in the stripe.
• Action: Check for other console error messages that indicate the cause of the failure. Replace any failed disks as soon as possible.

V-5-0-251

• Description: An error was detected while reading from a mirror. This error may lead to further action shown by later error messages.
• Action: If the volume is mirrored, no further action is necessary since the alternate mirror's contents will be written to the failing mirror; this is often sufficient to correct media failures. If this error occurs often, but never leads to a plex detach, there may be a marginally defective region on the disk at the position indicated. It may eventually be necessary to remove data from this disk (see the vxevac(1M) manual page) and then to reformat the drive.

If the volume is not mirrored, this message indicates that some data could not be read. The file system or other application reading the data may report an additional error, but in either event, data has been lost. The volume can be partially salvaged and moved to another location if desired.

---

  Note    This message may also appear during a plex detach operation in a cluster. In this case, no action is required.

---

V-5-0-252

• Description: A read error occurred, which caused a read of an alternate mirror and a writeback to the failing region. This writeback was successful and the data was corrected on disk.
• Action: None; the problem was corrected automatically. Note the location of the failure for future reference. If the same region of the subdisk fails again, this may indicate a more insidious failure and the disk should be reformatted at the next reasonable opportunity.

V-5-0-258

• Description: A disk array has been disconnected from the host, or some hardware failure has resulted in the disk array becoming inaccessible to the host.
• Action: Replace disk array hardware if this has failed.

V-5-0-386

• Description: The kernel has detected a subdisk failure, which may mean that the underlying disk is failing.
• Action: Check for obvious problems with the disk (such as a disconnected cable). If hot-relocation is enabled and the disk is failing, recovery from subdisk failure is handled automatically.

V-5-1-90

• Description: An invalid string was specified as an argument to the -m option. Valid strings are: enable, disable, and boot.
• Action: Supply a correct option argument.

V-5-1-91

• Description: vxconfigd cannot create a device node either under /dev/vx/dsk or under /dev/vx/rdsk. This should happen only if the root file system has run out of inodes.
• Action: Remove some unwanted files from the root file system. Then, regenerate the device node using the command:

  # vxdctl enable

V-5-1-92

• Description: The given directory could not be removed because the /usr/bin/rm utility could not be executed by vxconfigd. This is not a serious error. The only side effect of a directory not being removed is that the directory and its contents continue to use space in the root file system. However, this does imply that the /usr file system is not mounted, or on some systems, that the rm utility is missing or is not in its usual location. This may be a serious problem for the general running of your system.
• Action: If the /usr file system is not mounted, you need to determine how to get it mounted. If the rm utility is missing, or is not in the /usr/bin directory, restore it.

V-5-1-111

• Description: The given directory could not be removed because vxconfigd could not fork in order to run the rm utility. This is not a serious error. The only side effect of a directory not being removed is that the directory and its contents will continue to use space in the root file system. The most likely cause for this error is that your system does not have enough memory or paging space to allow vxconfigd to fork.
• Action: If your system is this low on memory or paging space, your overall system performance is probably substantially degraded. Consider adding more memory or paging space.

V-5-1-116

• Description: The vxconfigd console output log file could not be opened for the given reason.
• Action: Create any needed directories, or use a different log file path name as described in Logging Error Messages.

V-5-1-117

• Description: This error indicates that the volume cannot be started because it does not contain any valid plexes. This can happen, for example, if disk failures have caused all plexes to be unusable. It can also happen as a result of actions that caused all plexes to become unusable (for example, forcing the dissociation of subdisks or detaching, dissociation, or offlining of plexes).
• Action: It is possible that this error results from a drive that failed to spin up. If so, rebooting may fix the problem. If that does not fix the problem, then the only recourse is to repair the disks involved with the plexes and restore the file system from a backup.

V-5-1-121

• Description: The named disk appears to have become unusable and was detached from its disk group. Additional messages may appear to indicate other records detached as a result of the disk detach.
• Action: If hot-relocation is enabled, VERITAS Volume Manager objects affected by the disk failure are taken care of automatically. Mail is sent to root indicating what actions were taken by VxVM and what further actions the administrator should take.

V-5-1-122

• Description: This error only happens for volumes that are started automatically by vxconfigd at system startup. The plex is being detached as a result of I/O failure, disk failure during startup or prior to the last system shutdown or crash, or disk removal prior to the last system shutdown or crash.
• Action: To ensure that the file system retains the same number of active mirrors, remove the given plex and add a new mirror using the vxassist mirror operation. Also consider replacing any bad disks before running this command.

V-5-1-123

• 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 Restoring a Disk Group Configuration, and the contents of any volumes restored from a backup.

V-5-1-124

• 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

• 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.

V-5-1-135

• Description: This implies that there is insufficient memory to start up VxVM.
• Action: This error should not normally occur, unless your system has very small amounts of memory. Adding swap space probably will not help, because this error is most likely to occur early in the boot sequence, before swap areas have been added.

V-5-1-148

• Description: Either the root or the /usr file system volume could not be started, rendering the system unusable. The error that resulted in this condition should appear prior to this error message.
• Action: Look up other error messages appearing on the console and take the actions suggested in the descriptions of those messages.

V-5-1-169

• Description: The /dev/vx/config device could not be opened. vxconfigd uses this device to communicate with the VERITAS Volume Manager kernel drivers. The most likely reason is "Device is already open." This indicates that some process (most likely vxconfigd) already has /dev/vx/config open. Less likely reasons are "No such file or directory" or "No such device or address." For either of these reasons, likely causes are:
• The VERITAS Volume Manager package installation did not complete correctly.
• The device node was removed by the administrator or by an errant shell script.
• Action: If the reason is "Device is already open," stop or kill the old vxconfigd by running the command:

# vxdctl -k stop

For other failure reasons, consider re-adding the base VERITAS Volume Manager package. This will reconfigure the device node and re-install the VERITAS Volume Manager kernel device drivers. See the VERITAS Volume Manager 3.5 for HP-UX Release Notes for information on how to add the package. If you cannot re-add the package, contact VERITAS Technical Support for more information.


VxVM vxconfigd ERROR V-5-1-169 Cannot open /etc/fstab: reason
• Description: vxconfigd could not open the /etc/fstab file, for the reason given. The /etc/fstab file is used to determine which volume (if any) to use for the /usr file system.
• Action: This error implies that your root file system is currently unusable. You may be able to repair the root file system by mounting it after booting from a network or CD-ROM root file system. If the root file system is defined on a volume, then see the procedures defined for recovering from a failed root file system in Recovery from Boot Disk Failure.

V-5-1-249

• Description: Detaching a subdisk in the named RAID-5 volume has caused the volume to enter "degraded" mode. While in degraded mode, performance of the RAID-5 volume is substantially reduced. More importantly, failure of another subdisk may leave the RAID-5 volume unusable. Also, if the RAID-5 volume does not have an active log, then failure of the system may leave the volume unusable.
• Action: If hot-relocation is enabled, VERITAS Volume Manager objects affected by the disk failure are taken care of automatically. Mail is sent to root indicating what actions were taken by VxVM and what further actions the administrator should take.

V-5-1-480

• Description: The -r reset option was specified to vxconfigd, but the VxVM kernel drivers could not be reset. The most common reason is "A virtual disk device is open." This implies that a VxVM tracing or volume device is open.
• Action: If you want to reset the kernel devices, track down and kill all processes that have a volume or VERITAS Volume Manager tracing device open. Also, if any volumes are mounted as file systems, unmount those file systems.

Any reason other than "A virtual disk device is open" does not normally occur unless there is a bug in the operating system or in VxVM.

V-5-1-484

• Description: These errors indicate that the volume cannot be started because the volume contains no valid complete plexes. This can happen, for example, if disk failures have caused all plexes to be unusable. It can also happen as a result of actions that caused all plexes to become unusable (for example, forcing the dissociation of subdisks or detaching, dissociation, or offlining of plexes).
• Action: It is possible that this error results from a drive that failed to spin up. If so, rebooting may fix the problem. If that does not fix the problem, then the only recourse is to repair the disks involved with the plexes and restore the file system from a backup.

V-5-1-525

• Description: The DRL or RAID-5 log for the named volume was detached as a result of a disk failure, or as a result of the administrator removing a disk with vxdg -k rmdisk. A failing disk is indicated by a "Detached disk" message.
• Action: If the log is mirrored, hot-relocation tries to relocate the failed log automatically. Use either vxplex dis or vxsd dis to remove the failing logs. Then, use vxassist addlog (see the vxassist(1M) manual page) to add a new log to the volume.

V-5-1-526

• Description: The specified plex was disabled as a result of a disk failure, or as a result of the administrator removing a disk with vxdg -k rmdisk. A failing disk is indicated by a "Detached disk" message.
• Action: If hot-relocation is enabled, VERITAS Volume Manager objects affected by the disk failure are taken care of automatically. Mail is sent to root indicating what actions were taken by VxVM and what further actions the administrator should take.

V-5-1-527

• Description: The specified subdisk was disabled as a result of a disk failure, or as a result of the administrator removing a disk with vxdg -k rmdisk. A failing disk is indicated by a "Detached disk" message.
• Action: If hot-relocation is enabled, VERITAS Volume Manager objects affected by the disk failure are taken care of automatically. Mail is sent to root indicating what actions were taken by VxVM and what further actions the administrator should take.

V-5-1-528

• Description: The specified volume was detached as a result of a disk failure, or as a result of the administrator removing a disk with vxdg -k rmdisk. A failing disk is indicated by a "Detached disk" message. Unless the disk error is transient and can be fixed with a reboot, the contents of the volume should be considered lost.
• Action: Contact VERITAS Technical Support.

V-5-1-543

• Description: A vxconfigd daemon was started after stopping an earlier vxconfigd with a non-matching version number. This can happen, for example, if you upgrade VxVM and then run vxconfigd without first rebooting.
• Action: Reboot the system.

V-5-1-544

• Description: The given disk is listed as shared, but the running version of VxVM does not support shared disk groups.
• Action: This message can usually be ignored. If you want to use the disk on this system, use vxdiskadd to add the disk. Do not do this if the disk really is shared with other systems.

V-5-1-545

• Description: The given disk is listed as locked by the host with the VERITAS Volume Manager host ID (usually the same as the system host name).
• Action: This message can usually be ignored. If you want to use the disk on this system, use vxdiskadd to add the disk. Do not do this if the disk really is shared with other systems.

V-5-1-546

• Description: No physical disk can be found that matches the named disk in the given disk group. This is equivalent to failure of that disk. (Physical disks are located by matching the disk IDs in the disk group configuration records against the disk IDs stored in the VERITAS Volume Manager header on the physical disks.) This error message is displayed for any disk IDs in the configuration that are not located in the disk header of any physical disk. This may result from a transient failure such as a poorly-attached cable, or from a disk that fails to spin up fast enough. Alternately, this may happen as a result of a disk being physically removed from the system, or from a disk that has become unusable due to a head crash or electronics failure.

Any RAID-5 plexes, DRL log plexes, RAID-5 subdisks or mirrored plexes containing subdisks on this disk are unusable. Such disk failures (particularly on multiple disks) may cause one or more volumes to become unusable.

• Action: If hot-relocation is enabled, VERITAS Volume Manager objects affected by the disk failure are taken care of automatically. Mail is sent to root indicating what actions were taken by VxVM and what further actions the administrator should take.

V-5-1-554

• Description: As part of a disk group import, a disk was discovered that had a mismatched disk group name and disk group ID. This disk is not imported. This can only happen if two disk groups have the same name but have different disk group ID values. In such a case, one group is imported along with all its disks and the other group is not. This message appears for disks in the un-selected group.
• Action: If the disks should be imported into the group, this must be done by adding the disk to the group at a later stage, during which all configuration information for the disk is lost.

V-5-1-557

• Description: This can result from using vxdctl hostid to change the VERITAS 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. This usually indicates that the disk has become inaccessible or has failed in some other way.
• Action: Try running the following command 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 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

• 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

• 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.

A more serious failure is indicated by errors such as:


Configuration records are inconsistent
Disk group has no valid configuration copies
Duplicate record in configuration
Format error in configuration copy
Invalid block number
Invalid magic number 

These errors indicate that all configuration copies have become corrupt (due to disk failures, writing on the disk by an application or the administrator, or bugs in VxVM).

Some correctable errors may be indicated by other error messages that appear in conjunction with the auto-import failure message. Look up those other errors for more information on their cause.

Failure of an auto-import implies that the volumes in that disk group will not be available for use. If there are file systems on those volumes, then the system may yield further errors resulting from inability to access the volume when mounting the file system.

• Action: If the error is clearly caused by excessive disk failures, then you may have to recreate the disk group configuration by using the procedures given in Restoring a Disk Group Configuration, and restore contents of any volumes from a backup. There may be other error messages that appear which provide further information. See those other error messages for more information on how to proceed. If those errors do not make it clear how to proceed, contact VERITAS Technical Support.

V-5-1-571

• Description: Two disk groups with the same name are tagged for auto-importing by the same host. Disk groups are identified both by a simple name and by a long unique identifier (disk group ID) assigned when the disk group is created. Thus, this error indicates that two disks indicate the same disk group name but a different disk group ID.

VxVM does not allow you to create a disk group or import a disk group from another machine, if that would cause a collision with a disk group that is already imported. Therefore, this error is unlikely to occur under normal use. However, this error can occur in the following two cases:

• A disk group cannot be auto-imported due to some temporary failure. If you create a new disk group with the same name as the failed disk group and reboot, the new disk group is imported first. The auto-import of the older disk group fails because more recently modified disk groups have precedence over older disk groups.
• A disk group is deported from one host using the -h option to cause the disk group to be auto-imported on reboot from another host. If the second host was already auto-importing a disk group with the same name, then reboot of that host will yield this error.
• Action: If you want to import both disk groups, then rename the second disk group on import. See the vxdg(1M) manual page for information on how to use the import operation to rename a disk group.

V-5-1-577

• Description: The log areas for the disk group have become too small for the size of configuration currently in the group. This message only occurs during disk group import; it can only occur if the disk was inaccessible while new database objects were added to the configuration, and the disk was then made accessible and the system restarted. This should not normally happen without first displaying a message about the database area size.
• Action: Reinitialize the disks in the group with larger log areas. Note that this requires that you restore data on the disks from backups. See the vxdisk(1M) manual page. To reinitialize all of the disks, detach them from the group with which they are associated, reinitialize and re-add them. Then deport and re-import the disk group to effect the changes to the log areas for the group.

V-5-1-579

• Description: During a failed disk group import, some of the configuration copies in the named disk group were found to have format or other types of errors which make those copies unusable. This message lists all configuration copies that have uncorrected errors, including any appropriate logical block number. If no other reasons are displayed, then this may be the cause of the disk group import failure.
• 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

V-5-1-583

• 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.

V-5-1-587

• 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 ...

To clear the locks during import, use the following command:


# vxdg -C import diskgroup

---

 Caution    Be careful when using the vxdisk clearimport or vxdg -C import command on systems that have dual-ported disks. Clearing the locks allows those disks to be accessed at the same time from multiple hosts and can result in corrupted data.

---

An import operation fails if some disks for the disk group cannot be found among the disk drives attached to the system.


Disk for disk group not found
Disk group has no valid configuration copies

The first message indicates a recoverable error.

The second message indicates a fatal error that requires hardware repair or the creation of a new disk group, and recovery of the disk group configuration and data:

If some of the disks in the disk group have failed, you can force the disk group to be imported with this command:


# vxdg -f import diskgroup 

---

 Caution    Be careful when using the -f option. It can cause the same disk group to be imported twice from different sets of disks, causing the disk group to become inconsistent.

---

These operations can also be performed using the vxdiskadm utility. To deport a disk group using vxdiskadm, select menu item 8 (Remove access to (deport) a disk group). To import a disk group, select item 7 (Enable access to (import) a disk group). The vxdiskadm import operation checks for host import locks and prompts to see if you want to clear any that are found. It also starts volumes in the disk group.

V-5-1-663

• Description: The configuration of the named disk group includes conflicting device numbers. A disk group configuration lists the recommended device number to use for each volume in the disk group. If two volumes in two disk groups happen to list the same device number, then one of the volumes must use an alternate device number. This is called device number remapping. Remapping is a temporary change to a volume. If the other disk group is deported and the system is rebooted, then the volume that was remapped may no longer be remapped. Also, volumes that are remapped once are not guaranteed to be remapped to the same device number in further reboots.
• Action: Use the vxdg reminor command to renumber all volumes in the offending disk group permanently. See the vxdg(1M) manual page for more information.

V-5-1-737

• Description: The volume device listed in the /etc/fstab file for the given mount-point directory (normally /usr) is listed as in a disk group other than the boot disk group. This error should not occur if the standard VERITAS Volume Manager procedures are used for encapsulating the disk containing the /usr file system.
• Action: Boot VxVM from a network or CD-ROM mounted root file system. Then, start up VxVM using fixmountroot on a valid mirror disk of the root file system. After starting VxVM, mount the root file system volume and edit the /etc/fstab file. Change the file to use a direct partition for the file system. There should be a comment in the /etc/fstab file that indicates which partition to use.

V-5-1-768

• Description: An I/O error caused the indicated configuration copy to be disabled. This is a notice only, and does not normally imply serious problems, unless this is the last active configuration copy in the disk group.
• Action: Consider replacing the indicated disk, since this error implies that the disk has deteriorated to the point where write errors cannot be repaired automatically. The error can also result from transient problems with cabling or power.

V-5-1-809

• Description: The vxplex command fails because a previous operation to attach a plex did not complete. The vxprint command should show that one or both of the temporary and persistent utility fields (TUTIL0 and PUTIL0) of the volume and one of its plexes are set.
• Action: If the vxtask list command does not show a task running for the volume, use the vxmend command to clear the TUTIL0 and PUTIL0 fields for the volume and all its components for which these fields are set:

# vxmend -g diskgroup clear all volume plex ...

V-5-1-923

• Description: An attempt was made to snap back a plex from a different disk group.
• Action: Move the snapshot volume into the same disk group as the original volume.

V-5-1-1171

• Description: The release of vxconfigd does not match the release of the VERITAS Volume Manager kernel drivers. This should happen only as a result of upgrading VxVM, and then running vxconfigd without a reboot.
• Action: Reboot the system. If that does not cure the problem, re-add the VxVM packages.

V-5-1-1186

• Description: The system is configured to boot with /usr mounted on a volume, but the volume associated with /usr is not listed in the configuration of the boot disk group. There are two possible causes of this error:
• Case 1: The /etc/fstab file was erroneously updated to indicate the device for the /usr file system is a volume, but the volume named is not in the boot disk group. This should happen only as a result of direct manipulation by the administrator.
• Case 2: The system somehow has a duplicate boot disk group, one of which contains the /usr file system volume and one of which does not (or uses a different volume name), and vxconfigd somehow chose the wrong boot disk group. Since vxconfigd chooses the more recently accessed version of the boot disk group, this error can happen if the system clock was updated incorrectly at some point (causing the apparent access order of the two disk groups to be reversed). This can also happen if some disk group was deported and assigned the same name as the boot disk group with locks given to this host.
• Action: In case 1, boot the system on a CD-ROM or networking-mounted root file system. If the root file system is defined on a volume, then start and mount the root volume. If the root file system is not defined on a volume, mount the root file system directly. Edit the /etc/fstab file to correct the entry for the /usr file system.

In case 2, either boot with all drives in the offending version of the boot disk group turned off, or import and rename (see vxdg(1M)) the offending boot disk group from another host. If you turn off drives, run the following command after booting:


  # vxdg flush bootdg

This updates time stamps on the imported version of the boot disk group, bootdg, which should make the correct version appear to be the more recently accessed. If this does not correct the problem, contact VERITAS Technical Support.

V-5-1-1589

• Description: Regular startup of vxconfigd failed. This error can also result from the command vxdctl enable.
• Action: The failure was fatal and vxconfigd was forced to exit. The most likely cause is that the operating system is unable to create interprocess communication channels to other utilities.

VxVM vxconfigd ERROR V-5-1-1589 enable failed: Error check group configuration copies. Database file not found
• Description: Regular startup of vxconfigd failed. This error can also result from the command vxdctl enable.

The directory /var/vxvm/tempdb is inaccessible. This may be because of root file system corruption, if the root file system is full, or if /var is a separate file system, because it has become corrupted or has not been mounted.

• Action: If the root file system is full, increase its size or remove files to make space for the tempdb file.

If /var is a separate file system, make sure that it has an entry in /etc/fstab. Otherwise, look for I/O error messages during the boot process that indicate either a hardware problem or misconfiguration of any logical volume management software being used for the /var file system. Also verify that the encapsulation (if configured) of your boot disk is complete and correct.


VxVM vxconfigd ERROR V-5-1-1589 enable failed: transactions are disabled
• Description: Regular startup of vxconfigd failed. This error can also result from the command vxdctl enable.

vxconfigd is continuing to run, but no configuration updates are possible until the error condition is repaired.

Additionally, this may be followed with:


VxVM vxconfigd ERROR V-5-1-579 Disk group group: Errors in some
configuration copies:
Disk device, copy number: Block bno: error ...

Other error messages may be displayed that further indicate the underlying problem.

• Action: Evaluate the error messages to determine the root cause of the problem. Make changes suggested by the errors and then try rerunning the command.

If the "Errors in some configuration copies" error occurs again, that may indicate the real problem lies with the configuration copies in the disk group. You can recreate a disk group configuration by using the procedures given in Restoring a Disk Group Configuration.

V-5-1-2020

• Description: The -k (kill existing vxconfigd process) option was specified, but a running configuration daemon process could not be killed. A configuration daemon process, for purposes of this discussion, is any process that opens the /dev/vx/config device (only one process can open that device at a time). If there is a configuration daemon process already running, then the -k option causes a SIGKILL signal to be sent to that process. If, within a certain period of time, there is still a running configuration daemon process, the above error message is displayed.
• Action: This error can result from a kernel error that has made the configuration daemon process unkillable, from some other kind of kernel error, or from some other user starting another configuration daemon process after the SIGKILL signal. This last condition can be tested for by running vxconfigd -k again. If the error message reappears, contact VERITAS Technical Support.

V-5-1-2197

• Description: The vxconfigd daemon is not running on the indicated cluster node.
• Action: Restart the vxconfigd daemon.

V-5-1-2198

• Description: The vxconfigd daemon is not responding properly in a cluster.
• Action: Stop and restart the vxconfigd daemon on the node indicated.

V-5-1-2274

• Description: A volume that vxconfigd should start immediately upon booting the system (that is, the volume for the /usr file system) has a RAID-5 layout. The /usr file system should never be defined on a RAID-5 volume.
• Action: It is likely that the only recovery for this is to boot VxVM from a network-mounted root file system (or from a CD-ROM), and reconfigure the /usr file system to be defined on a regular non-RAID-5 volume.

V-5-1-2290

• Description: This message is returned by the vxdmpadm utility when an attempt is made to enable a controller that is not working or is not physically present.
• Action: Check hardware and see if the controller is present and whether I/O can be performed through it.

V-5-1-2353

• Description: This can happen if you kill and restart vxconfigd, or if you disable and enable it with vxdctl disable and vxdctl enable. This error indicates a failure related to reading the file /var/vxvm/tempdb/group. This is a temporary file used to store information that is used when recovering the state of an earlier vxconfigd. The file is recreated on a reboot, so this error should never survive a reboot.
• Action: If you can reboot, do so. If you do not want to reboot, then do the following:
1. Ensure that no vxvol, vxplex, or vxsd processes are running.

Use ps -e to search for such processes, and use kill to kill any that you find. You may have to run kill twice to make these processes go away. Killing utilities in this way may make it difficult to make administrative changes to some volumes until the system is rebooted.

2. Recreate the temporary database files for all imported disk groups using the following command:

    # vxconfigd -x cleartempdir 2> /dev/console

The vxvol, vxplex, and vxsd commands make use of these tempdb files to communicate locking information. If the file is cleared, then locking information can be lost. Without this locking information, two utilities can end up making incompatible changes to the configuration of a volume.

V-5-1-2524

• Description: The number of VERITAS Volume Manager kernel daemons (vxiod) is less than the minimum number needed to join a cluster.
• Action: Increase the number of daemons using vxiod.

V-5-1-2630

• Description: This warning may safely be ignored.
• Action: None required.

V-5-1-2824

• Description: A node failed to join a cluster, or a cluster join is taking too long. If the join fails, the node retries the join automatically.
• Action: No action is necessary if the join is slow or a retry eventually succeeds.

V-5-1-2829

• Description: The version of the specified disk group does not support disk group move, split or join operations.
• Action: Use the vxdg upgrade diskgroup command to update the disk group version.

V-5-1-2830

• Description: An attempt was made to online a disk whose controller has been reserved by another host in the cluster.
• Action: No action is necessary. The cluster manager frees the disk and VxVM puts it online when the node joins the cluster.

V-5-1-2860

• Description: One of the disk groups specified in a disk group move, split or join operation is currently involved in another unrelated disk group move, split or join operation (possibly as the result of recovery from a system failure).
• Action: Use the vxprint command to display the status of the disk groups involved. If vxprint shows that the TUTIL0 field for a disk group is set to MOVE, and you are certain that no disk group move, split or join should be in progress, use the vxdg command to clear the field as described in Recovering from Incomplete Disk Group Moves. Otherwise, retry the operation.

V-5-1-2862

• Description: DCO and snap objects dissociated by Persistent FastResync, and VVR objects cannot be moved between disk groups.
• Action: None. The operation is not supported.

V-5-1-2866

• Description: A disk group join operation failed because the name of an object in one disk group is the same as the name of an object in the other disk group. Such name clashes are most likely to occur for snap objects and snapshot plexes.
• Action: Use the following command to change the object name in either one of the disk groups:

# vxedit -g diskgroup rename old_name new_name

For more information about using the vxedit command, see the vxedit(1M) manual page.

V-5-1-2870

• Description: An attempt was made to perform a disk group move, split or join on a disk group containing an open volume.
• Action: It is most likely that a file system configured on the volume is still mounted. Stop applications that access volumes configured in the disk group, and unmount any file systems configured in the volumes.

V-5-1-2879

• Description: The named subdisk is not a top-level object.
• Action: Objects specified for a disk group move, split or join must be either disks or top-level volumes.

V-5-1-2907

• Description: The disk group does not exist or is not imported
• Action: Use the correct name, or import the disk group and try again.

V-5-1-2908

• Description: The specified disk device is not configured in the source disk group for a disk group move or split operation.
• Action: Correct the name of the disk object specified in the disk group move or split operation.

V-5-1-2911

• Description: The specified disk has become unusable.
• Action: Do not include the disk in any disk group move, split or join operation until it has been replaced or repaired.

V-5-1-2922

• Description: A slave tried to join a cluster, but a shared disk group already exists in the cluster with the same name as one of its private disk groups.
• Action: Use the vxdg -n newname import diskgroup operation to rename either the shared disk group on the master, or the private disk group on the slave.

V-5-1-2928

• Description: The disk group's configuration database is too small to hold the expanded configuration after a disk group move or join operation.
• Action: None.

V-5-1-2933

• Description: The requested disk group move, split or join operation would leave the disk group without any configuration copies.
• Action: None. The operation is not supported.

V-5-1-3009

• Description: The target disk group of a split operation already exists as an imported disk group.
• Action: Choose a different name for the target disk group.

V-5-1-3020

• Description: This may be due to an operation inconsistent with the current state of a cluster (such as an attempt to import or deport a shared disk group to or from the slave). It may also be caused by an unexpected sequence of commands from vxclust.
• Action: Perform the operation from the master node.

V-5-1-3022

• Description: A slave node in a cluster cannot find a shared disk. This is accompanied by the syslog message:

  VxVM vxconfigd ERROR V-5-1-2173 cannot find disk disk
• Action: Make sure that the same set of shared disks is online on both nodes. Examine the disks on both the master and the slave with the command vxdisk list and make sure that the same set of disks with the shared flag is visible on both nodes. If not, check the connections to the disks.

V-5-1-3023

• Description: An attempt was made to import a disk group whose disks are stamped with the ID of another cluster.
• Action: If the disk group is not imported by another cluster, retry the import using the -C (clear import) flag.

V-5-1-3024

• Description: An error during an attempt to join a cluster caused vxclust to fail. This may be caused by the failure of another node during a join or by the failure of vxclust.
• Action: Retry the join. An error message on the other node may clarify the problem.

V-5-1-3025

• Description: vxconfigd was not able to create a portal for communication with the vxconfigd on the other node. This may happen in a degraded system that is experiencing shortages of system resources such as memory or file descriptors.
• Action: If the system does not appear to be degraded, stop and restart vxconfigd, and try again.

V-5-1-3030

• Description: A node that crashed attempted to rejoin the cluster before its DRL map was merged into the recovery map.
• Action: Retry the join when the merge operation has completed.

V-5-1-3031

• Description: A slave attempted to join a cluster, but an existing volume on the slave has the same minor number as a shared volume on the master.

This message is accompanied by the following console message:


VxVM vxconfigd ERROR V-5-1-2192 minor number minor disk group group in use
• Action: Before retrying the join, use vxdg reminor (see the vxdg(1M) manual page) to choose a new minor number range either for the disk group on the master or for the conflicting disk group on the slave. If there are open volumes in the disk group, the reminor operation will not take effect until the disk group is deported and updated (either explicitly or by rebooting the system).

V-5-1-3032

• Description: During the slave join protocol, a message without data was received from the master. This message is only likely to be seen in the case of an internal VxVM error.
• Action: Contact VERITAS Technical Support.

V-5-1-3033

• Description: An attempt was made to import or deport a shared disk group during a cluster reconfiguration.
• Action: Retry when the cluster reconfiguration has completed.

V-5-1-3034

• Description: A slave attempted to join a cluster when the master was not ready. The slave will retry automatically.
• Action: No action is necessary if the join eventually completes. Otherwise, investigate the cluster monitor on the master.

V-5-1-3042

• Description: An operation requiring a full clustering license was attempted, and such a license is not available.
• Action: If the error occurs when a disk group is being activated, dissociate all but one plex from mirrored volumes before activating the disk group. If the error occurs during a transaction, deactivate the disk group on all nodes except the master.

V-5-1-3046

• Description: The disk group could not be activated because it is activated in a conflicting mode on another node in a cluster.
• Action: Retry later, or deactivate the disk group on conflicting nodes.

V-5-1-3049

• Description: An attempt was made to upgrade a cluster to a higher protocol version when a transaction was in progress.
• Action: Retry the upgrade at a later time.

V-5-1-3050

• Description: Before trying to upgrade a cluster by running vxdctl upgrade, all nodes should be able to support the new protocol version. An upgrade can fail if at least one of them does not support the new protocol version.
• Action: Make sure that the VERITAS Volume Manager package that supports the new protocol version is installed on all nodes and retry the upgrade.

V-5-1-3091

• Description: Some volumes have subdisks that are not on the disks implied by the supplied list of objects.
• Action: Use the -o expand option to vxdg listmove to produce a self-contained list of objects.

V-5-1-3212

• Description: A volume with an insufficient DRL log size was started successfully, but DRL logging is disabled and a full recovery is performed.
• Action: Create a new DRL of sufficient size.

V-5-1-3243

• Description: The vxdmpadm start restore command has been executed while the restore daemon is already running.
• Action: Stop the restore daemon and restart it with the required set of parameters as shown in the vxdmpadm(1M) manual page.

V-5-1-3362

• Description: Disabling the controller could lead to some devices becoming inaccessible.
• Action: To disable the only path connected to a disk, use the -f option.

V-5-1-3486

• Description: Checking for the current protocol version (using vxdctl protocol version) does not work if the node is not in a cluster.
• Action: Bring the node into the cluster and retry.

V-5-1-3689

• Description: An error was detected while reattaching a snapshot volume using snapback. This happens if a volume's record identifier (rid) changes as a result of a disk group split that moved the original volume to a new disk group. The snapshot volume is unable to recognize the original volume because its record identifier has changed.
• Action: Use the following command to perform the snapback:

# vxplex [-g diskgroup] -f snapback volume plex

V-5-1-3828

• Description: An upgrade operation has failed because a cluster is already running at the highest protocol version supported by the master.
• Action: No further action is possible as the master is already running at the highest protocol version it can support.

V-5-1-3848

• Description: A node attempted to join a cluster where VxVM software was incorrectly upgraded or the volboot file is corrupted, possibly by being edited manually. The volboot file should contain a supported protocol version before trying to bring the node into the cluster.
• Action: Verify the supported cluster protocol versions using the vxdctl protocolversion command. The volboot file should contain a supported protocol version before trying to bring the node into the cluster. Run vxdctl init to write a valid protocol version to the volboot file. Restart vxconfigd and retry the join.

V-5-1-4220

• Description: The specified disk group cannot be imported during a disk group move operation. (The disk group ID is obtained from the disk group that could be imported.)
• Action: The disk group may have been moved to another host. One option is to locate it and use the vxdg recover command on both the source and target disk groups. Specify the -o clean option with one disk group, and the -o remove option with the other disk group. See Recovering from Incomplete Disk Group Moves for more information.

V-5-1-4267

• Description: An error was detected while adding a DCO object and DCO volume to a mirrored volume. There is at least one snapshot plex already created on the volume. Because this snapshot plex was created when no DCO was associated with the volume, there is no DCO plex allocated for it.
• Action: See the section "Adding a Version 0 DCO and DCO Volume" in the chapter "Administering Volume Snapshots" of the VERITAS Volume Manager Administrator's Guide.

V-5-1-4277

• Description: When a node joins a cluster, it tries to join at the protocol version that is stored in its volboot file. If the cluster is running at a different protocol version, the master rejects the join and sends the current protocol version to the slave. The slave re-tries with the current version (if that version is supported on the joining node), or the join fails.
• Action: Make sure that the joining node has a VERITAS Volume Manager release installed that supports the current protocol version of the cluster.

V-5-1-4551

• Description: Disks involved in a disk group move operation cannot be found, and one of the specified disk groups cannot be imported.
• Action: Manual use of the vxdg recover command may be required to clean the disk group to be imported. See Recovering from Incomplete Disk Group Moves for more information.

V-5-1-4620

• Description: The vxassist command does not recognize the version of the SAN Access Layer (SAL) that is being used, or detects an error in the output from SAL.
• Action: If a connection to SAL is desired, ensure that the correct version of SAL is installed and configured correctly. Otherwise, suppress communication between vxassist and SAL by adding the following line to the vxassist defaults file (usually /etc/default/vxassist):

salcontact=no

V-5-1-4625

• Description: The SAN Access Layer (SAL) rejects the credentials that are supplied by the vxassist command.
• Action: If connection to SAL is desired, use the vxspcshow command to set a valid user name and password. Otherwise, suppress communication between vxassist and SAL by adding the following line to the vxassist defaults file (usually /etc/default/vxassist):

salcontact=no

V-5-1-5150

• Description: An attempt to snap back a specified number of snapshot mirrors to their original volume failed.
• Action: Specify a number of snapshot mirrors less than or equal to the number in the snapshot volume.

V-5-1-5160

• Description: An attempt was made to snap back a plex that is not from a snapshot volume.
• Action: Specify a plex from a snapshot volume.

V-5-1-5161

• Description: An attempt was made to snap back a detached plex.
• Action: Reattach the snapshot plex to the snapshot volume.

V-5-1-5162

• Description: An attempt was made to snap back plexes that belong to different snapshot volumes.
• Action: Specify the plexes in separate invocations of vxplex snapback.

V-5-1-5929

• Description: When VxVM detects disks with duplicate disk IDs (unique internal identifiers), VxVM attempts to select the appropriate disk (using logic that is specific to an array). If a disk can not be selected, VxVM does not import any of the duplicated disks into a disk group. In the rare case when VxVM cannot make the choice, you must choose which duplicate disk to use.

---

  Note    In releases prior to 3.5, VxVM selected the first disk that it found if the selection process failed. FromVxVM 3.5 onward, the default behavior is to avoid the selection of the wrong disk as this could lead to data corruption. Arrays with mirroring capability in hardware are particularly susceptible to such data corruption.

---

• Action: User intervention is required in the following cases:
• Case 1: When DMP is disabled to an array that has multiple paths, then each path to the array is claimed as a unique disk.

If DMP is suppressed, VxVM does not know which path to select as the true path. You must choose which path to use. Decide which path to exclude, and then either edit the file /etc/vx/vxvm.exclude,or, if vxconfigd is running, select item 1 (suppress all paths through a controller from VxVM's view) or item 2 (suppress a path from VxVM's view) from vxdiskadm option 17 (Prevent multipathing/Suppress devices from VxVM's view).

The following example shows a vxvm.exclude file with paths c8t0d0, c8t0d1, and c8t0d2 excluded from VxVM:


exclude_all 0
paths
c8t0d0 /0/4/0/0.8.0.108.0.0.0
c8t0d1 /0/4/0/0.8.0.108.0.0.1
c8t0d2 /0/4/0/0.8.0.108.0.0.2
#
controllers
#
product
#
pathgroups
• Case 2: Some arrays such as EMC and HDS provide mirroring in hardware. When a LUN pair is split, depending on how the process is performed, this may result in two disks with the same disk ID.

Check with your array vendor to make sure that you are using the correct split procedure. If you know which LUNs you want to use, choose which path to exclude, and then either edit the file /etc/vx/vxvm.exclude, or, if vxconfigd is running, select item 1 (Suppress all paths through a controller from VxVM's view) or item 2 (Suppress a path from VxVM's view) from vxdiskadm option 17 (Prevent multipathing/Suppress devices from VxVM's view).

• Case 3: If disks have become duplicated using the dd command or any other disk copying utility, choose which set of duplicate disks you want to exclude, and then either edit the file /etc/vx/vxvm.exclude, or, if vxconfigd is running, select item 1 (Suppress all paths through a controller from VxVM's view) or item 2 (Suppress a path from VxVM's view) from vxdiskadm option 17 (Prevent multipathing/Suppress devices from VxVM's view).