Use Control F to search for a specific error code in each catalog. To search for any error code, select the Search button at the top right of the screen.
| Code | Severity | Message | Cause/Action |
|---|---|---|---|
| 104002 | FATAL | $msg | Cause: This message indicates an internal software error. Action: The stack trace indicates the source of the error. |
| 104003 | FATAL | $self->Val(‘Tag’) . " is not an SDR resource" | Cause: A data replication action was attempted on a non data replication resource. Action: Check the logs for related errors and try to resolve the reported problem. |
| 104010 | ERROR | $self->{‘md’}: bitmap merge failed, $action | Cause: The bitmap merge operation has failed. Action: The target server may have the mirror and/or protected filesystem mounted, or the bitmap file may be missing on the target. Check the target server. |
| 104022 | ERROR | $argv1: mdadm failed ($ret | Cause: The "mdadm" command has failed to add a device into the mirror. Action: This is usually a temporary condition. |
| 104023 | ERROR | $_ | Cause: The message contains the output of the "mdadm" command. |
| 104025 | ERROR | failed to spawn monitor | Cause: The system failed to start the ‘mdadm -F’ monitor process. This should not happen under normal circumstances. Action: Reboot the system to ensure that any potential conflicts are resolved. |
| 104026 | ERROR | cannot create $md | Cause: The mirror device could not be created. Action: Ensure the device is not already in use and that all other parameters for the mirror creation are correct. |
| 104027 | ERROR | $_ | Cause: This message contains the "mdadm" command output. |
| 104035 | ERROR | Too many failures. Aborting resync of $md | Cause: The device was busy for an abnormally long period of time. Action: Reboot the system to be sure that the device is no longer busy. |
| 104036 | ERROR | Failed to start nbd-server on $target (error $port | Cause: The nbd-server process could not be started on the target server. Action: Ensure that the target disk device is available and that its Device ID has not changed. |
| 104037 | ERROR | Failed to start compression (error $port | Cause: The system was unable to start the ‘balance’ tunnel process or there was a network problem. Action: Ensure that the network is operating properly and that TCP ports in the range 10000-10512 are opened and unused. Ensure that the software is installed properly on all systems. |
| 104038 | ERROR | Failed to start nbd-client on $source (error $ret | Cause: The nbd-client process has failed to start on the source server. Action: Look up the reported errno value and try to resolve the problem reported. For example, an errno value of 110 means "Connection timed out", which may indicate a network or firewall problem. |
| 104039 | ERROR | Failed to add $nbd to $md on $source | Cause: This is usually a temporary condition. Action: If this error persists, reboot the system to resolve any potential conflicts. |
| 104045 | ERROR | failed to stop $self->{‘md’} | Cause: The mirror device could not be stopped. Action: Ensure that the device is not busy or mounted. Try running "mdadm —stop" manually to stop the device. |
| 104048 | WARN | failed to kill $proc, pid $pid | Cause: The process could not be signalled. This may indicate that the process has already died. Action: Ensure that the process in question is no longer running. If it is, then reboot the system to clear up the unkillable process. |
| 104050 | ERROR | Setting $name on $dest failed: $ret. Please try again. | Cause: The system failed to set a ‘mirrorinfo’ file setting. Action: Check the network and systems and retry the mirror setting operation. |
| 104052 | FATAL | Specified existing mount point "%s" is not mounted | Cause: The mount point became unmounted. Action: Ensure that the mount point is mounted and retry the operation. |
| 104055 | ERROR | Failed to set up temporary $type access to data for $self->{‘tag’}. Error: $ret | Cause: The filesystem or device was not available on the target server. The mirrored data will not be available on the target server until the mirror is paused and resumed again. Action: Reboot the target server to resolve any potential conflicts. |
| 104057 | ERROR | Failed to undo temporary access for $self->{‘tag’} on $self->{‘sys’}. Error: $ret. Please verify that $fsid is not mounted on server $self->{‘sys’}. | Cause: The filesystem could not be unmounted on the target server. Action: Ensure that the filesystem and device are not busy on the target server. Reboot the target server to resolve any potential conflicts. |
| 104066 | FATAL | Cannot get the hardware ID of device "%s" | Cause: A unique ID could not be found for the target disk device. Action: Ensure that the appropriate storage recovery kits are installed on the target server. Ensure that the Device ID of the target disk has not changed. |
| 104067 | FATAL | Asynchronous writes cannot be enabled without a bitmap file | Cause: An attempt was made to create a mirror with invalid parameters. Action: A bitmap file parameter must be specified or synchronous writes must be specified. |
| 104070 | FATAL | Unable to extend the mirror "%s" to system "%s" | Cause: The hierarchy extend operation failed. Action: Check the logs for related errors and try to resolve the reported problem. |
| 104081 | FATAL | Cannot make the %s filesystem on "%s" (%d) | Cause: The "mkfs" command failed. Action: Ensure that the disk device is writable and free of errors and that the filesystem tools for the selected filesystem are installed. |
| 104082 | FATAL | %s | Cause: This message contains the output of the "mkfs" command. |
| 104083 | FATAL | Cannot create filesys hierarchy "%s" | Cause: The resource creation failed. Action: Check the logs for related errors and try to resolve the reported problem. |
| 104086 | ERROR | The "%s_data_corrupt" flag is set in "%s/subsys/scsi/resources/netraid/" on system "%s". To avoid data corruption, LifeKeeper will not restore the resource. | Cause: The data corrupt flag file has been set as a precaution to prevent accidental data corruption. The mirror cannot be restored on this server until the file is removed. Action: If you are sure that the data is valid on the server in question, you can either: 1) remove the file and restore the mirror, or 2) force the mirror online using the LifeKeeper GUI or ‘mirror_action force’ command. |
| 104099 | ERROR | Unable to unextend the mirror for resource "%s" from system "%s" | Cause: The hierarchy unextend operation failed. Action: Reboot the target server to resolve any potential conflicts and retry the operation. |
| 104106 | ERROR | remote ‘bitmap -m’ command failed on $target->{‘sys’}: $ranges | Cause: The bitmap merge command failed on the target server. This may be caused by one of two things: 1) The bitmap file may be missing or corrupted, or 2) the mirror (md) device may be active on the target. Action: Make sure that the mirror and protected filesystem are not active on the target. If the target’s bitmap file is missing, pause and resume the mirror to recreate the bitmap file. |
| 104107 | ERROR | Asynchronous writes cannot be enabled without a bitmap file | Cause: Invalid parameters were specified for the mirror create operation. |
| 104108 | ERROR | Local Partition not available | Cause: Invalid parameters were specified for the mirror create operation. |
| 104109 | ERROR | Cannot get the hardware ID of device "%s" | Cause: A unique ID could not be determined for the disk device. Action: Ensure that the appropriate storage recovery kits are installed on the server. Ensure that the Device ID of the disk has not changed. |
| 104111 | FATAL | Insufficient input parameters for "%s" creation | Cause: Invalid parameters were specified for the mirror create operation. |
| 104112 | FATAL | Insufficient input parameters for "%s" creation | Cause: Invalid parameters were specified for the mirror create operation. |
| 104113 | FATAL | Insufficient input parameters for "%s" creation | Cause: Invalid parameters were specified for the mirror create operation. |
| 104115 | FATAL | Insufficient input parameters for "%s" creation | Cause: Invalid parameters were specified for the mirror create operation. |
| 104117 | FATAL | Insufficient input parameters for "%s" creation | Cause: Invalid parameters were specified for the mirror create operation. |
| 104118 | FATAL | Cannot unmount existing Mount Point "%s" | Cause: The mount point is busy. Action: Make sure the filesystem is not busy. Stop any processes or applications that may be accessing the filesystem. |
| 104119 | FATAL | Invalid data replication resource type requested ("%s" | Cause: An invalid parameter was specified for the mirror create operation. |
| 104124 | EMERG | WARNING: A temporary communication failure has occurred between systems %s and %s. In order to avoid data corruption, data resynchronization will not occur. MANUAL INTERVENTION IS REQUIRED. In order to initiate data resynchronization, you should take one of the following resources out of service: %s on %s or %s on %s. The resource that is taken out of service will become the mirror target. | Cause: A temporary communication failure (split-brain scenario) has occurred between the source and target servers. Action: Perform the steps listed in the message text. |
| 104125 | ERROR | failed to start ‘$cmd $_2 $user_args’ on ‘$_3‘ | Cause: The specified command failed. Action: Check the logs for related errors and try to resolve the reported problem. |
| 104126 | ERROR | $_ | Cause: This message contains the output of the command that was reported as failing in message 104125. |
| 104128 | FATAL | comm path/server not specified | Cause: The netraid.down script was called without specifying the communication path or the server name. This script is called internally so should always have the proper parameters. Action: Report this error to SIOS support. |
| 104129 | WARN | Cause: The replication connection for the mirror is down. Action: Check the network. |
|
| 104130 | ERROR | Mirror resize failed on %s (%s). You must successfully complete this operation before using the mirror. Please try again. | Cause: The mirror resize operation has failed to update the mirror metadata on the listed system. Action: You must successfully complete the resize before using the mirror. Re-run mirror_resize (possibly using -f to force the operation if necessary). |
| 104132 | ERROR | The partition "%s" has an odd number of sectors and system "%s" is running kernel >= 4.12. Mirrors with this configuration will not work correctly with DataKeeper. Please see the SIOS product documentation for information on how to resize the mirror. | Cause: The partition or disk chosen for mirror creation has an odd number of disk sectors and will have to be resized to be used with DataKeeper. Action: Resize the partition using the ‘parted’ command or resize the disk (is possible) using platform (VMware, AWS) tools. Caution: data may be lost if this is not done carefully. |
| 104143 | ERROR | Mirror resume was unsuccessful ($ret | Cause: The mirror could not be established. Action: Check the logs for related errors and try to resolve the reported problems. |
| 104144 | ERROR | Unable to stop the mirror access for $self->{‘md’} on system $self->{‘sys’}. Error: $ret. Use the \"mdadm —stop $self->{‘md’}\" command to manually stop the mirror. | Cause: The mirror device created on the target node when the mirror was paused could not be stopped. Action: Ensure that the device is not busy or mounted. Try running "mdadm —stop" manually to stop the device. |
| 104145 | WARN | Unable to dirty full bitmap. Setting fullsync flag. | Cause: A full resync could not be done by dirtying the full bitmap. The fullsync flag will be used instead. This is a non-fatal error as a full synchronization will still be done. Action: None |
| 104146 | EMERG | WARNING: The target system %s for mirror %s has the target mirror %s currently active. In order to avoid data corruption, data resynchronization will not occur. MANUAL INTERVENTION IS REQUIRED. In order to initiate data resynchronization, you should reboot system %s. | Cause: The mirror is configured on the target system. Action: The target system should be rebooted. DataKeeper should then be able to resync the mirror. |
| 104147 | EMERG | WARNING: The target system %s for mirror %s has the target disk %s currently mounted. In order to avoid data corruption, data resynchronization will not occur. MANUAL INTERVENTION IS REQUIRED. In order to initiate data resynchronization, you should unmount %s on %s. A full resync will occur. | Cause: The mirror disk is mounted on the target system. Action: The mirror disk should be unmounted on the target system, in order to initiate a full mirror resync. A full resync is required because untracked changes have occurred on the disk. |
| 104148 | EMERG | The storage configuration for mirror "%s (%s)" does not have a unique identifier and may have potential for data corruption in some environments in certain circumstances. Please refer to the SIOS Product Documentation for details on DataKeeper storage configuration options. | Cause: The disk chosen for mirroring does not provide a UUID to the operating system. DataKeeper cannot mirror a disk without a UUID. Action: You may be able to create a GPT partition table on the disk to provide a UUID for the disk partitions. |
| 104149 | ERROR | snmptrap returned $err for Trap 142 | Cause: The SNMP trap 142 to notify when DataKeeper has paused the mirror and mounted the target disk failed. The details of the error will be displayed following this message. |
| 104150 | ERROR | COMMAND OUTPUT: cat /tmp/err$$ | Cause: The SNMP trap 142 to notify when DataKeeper has paused the mirror and mounted the target disk failed. The details of the error is displayed in this message. |
| 104152 | ERROR | [$SUBJECT event] mail returned $err | Cause: The email to notify when DataKeeper has paused the mirror and mounted the target disk failed. The details of the error will be displayed following this message. |
| 104153 | ERROR | COMMAND OUTPUT: cat /tmp/err$$ | Cause: The email to notify when DataKeeper has paused the mirror and mounted the target disk failed. The details of the error will be displayed in this message. |
| 104155 | EMERG | The mirror %s cannot be forced online at this time. The underlying disk %s is mounted, indicating possible data corruption. MANUAL INTERVENTION IS REQUIRED. You must unmount %s on %s and restore the mirror to the last known mirror source system. A full resync will need to be performed from the source system to %s. | Cause: You have mounted the underlying mirrored disk on the target system. Action: You must unmount the disk immediately in order to avoid data corruption. |
| 104156 | WARN | Resynchronization of "%s" is in PENDING state. Current sync_action is: "%s" | Cause: The resynchronization of the md device is detected in PENDING state. Action: LifeKeeper will try to fix the issue by forcing a resynchronization. Check the logs for related errors. When successful assure that the PENDING state has been cleared in /proc/mdstat and the resynchronization is in progress or has been completed for the datarep resource. |
| 104158 | EMERG | WARNING: The local disk partition $self->{‘part’} for data replication device\n$self->{‘md’} has failed. MANUAL INTERVENTION IS REQUIRED. | Cause: The local device for a mirror failed. The recovery action has been set to "nothing" in LKDR_FAILURE requiring manual intervention to recover. Action: Check system logs and LifeKeeper logs for errors related to the local disk. |
| 104163 | WARN | The "%s_data_corrupt" flag is set in "%s/subsys/scsi/resources/netraid/" on system "%s". The mirror is being forced online. | Cause: The mirror is being forced online, overriding the data_corrupt flag. The data on the specified system will be treated as the latest data. If this is not correct then this can lead to data corruption or data loss. Action: None |
| 104164 | ERROR | The "%s_data_corrupt" flag for related mirror resource "%s" is set in "%s/subsys/scsi/resources/netraid/" on system "%s". To avoid data corruption, LifeKeeper will not restore this mirror or any related mirrors in the hierarchy. | Cause: The data_corrupt flag exists for one or more mirrors in the hierarchy. To avoid corrupting additional data none of the mirrors are brought in-service until all of the data_corrupt flags are resolved. Action: Check the LifeKeeper logs to determine where each mirror was last in-service, aka where the latest data for each mirror resides. The mirrors should be brought in-service on the "previous source" where the full hierarchy was in-service and allow the mirrors to synchronize with all targets. |
| 104165 | ERROR | The "%s_data_corrupt" flag for related mirror resource "%s" is set in "%s/subsys/scsi/resources/netraid/" on system "%s". The mirror resource "%s" is being forced online. | Cause: The mirror is being forced online, overriding the data_corrupt flag. The data on the specified system will be treated as the correct data to be synchronized with all targets. This can lead to data corruption or data loss if this is not the latest data. Action: None |
| 104171 | ERROR | Failed to create \"source\" flag file on %s to track mirror source. Target %s will not be added to mirror. | Cause: The ‘source’ flag file was not created on the specified system to track the mirror source. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104172 | ERROR | The \"source\" flag file on %s does not contain a valid target (%s). Full resync to remaining targets is required. | Cause: The ‘source’ flag file should contain the system name of a previous source but the name listed was not found in the list of systems configured. Action: Report this problem to SIOS support. |
| 104173 | ERROR | Failed to create \"source\" flag file on %s to track mirror source. | Cause: The ‘source’ flag file was not created on the specified system to track the mirror source Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104174 | ERROR | Failed to create \"previous_source\" flag file to track time waiting on source. Will not be able to timeout. | Cause: The ‘previous_source’ flag file was not created on the mirror source to track the mirror’s previous source. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104175 | ERROR | Failed to create "data_corrupt" flag file on target "%s". | Cause: The ‘data_corrupt’ flag file was not created on the target listed. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104176 | ERROR | The \"source\" flag file on %s to track mirror source does not exist. Full resync is required. | Cause: The ‘source’ flag file should exist on the system and without it the consistency of the mirror can not be verified. A full resync is required to assure data reliability. Action: Check the LKROOT (/opt/LifeKeeper) file system for error or that it is full. |
| 104177 | ERROR | Failed to determine amount of time waiting on %s. | Cause: The amount of time waiting for the previous source could not be determined. Targets will be added with a full resync if the previous source is not found. Action: none |
| 104178 | ERROR | Failed to update "source" flag file on target "%s", previous source must be merged first. | Cause: The source flag file on the target is updated when it is in-sync and stopped so the the next in-service does not require the previous source. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104180 | ERROR | Internal Error: \"previous_source\" has the local system name (%s). | Cause: The local system name should not be in the previous_source flag file. Action: Report this error to SIOS support. |
| 104181 | ERROR | Internal Error: There are no targets waiting on %s to be merged. | Cause: There are no targets waiting for a previous source to merge. Action: Report this error to SIOS support. |
| 104182 | ERROR | Failed to create \"source\" flag file on %s to track mirror source. This may result in a full resync. | Cause: The ‘source’ flag file was not created on the target listed. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104186 | ERROR | Failed to create \"last_owner\" flag file on %s to track mirror source. This may allow in-service of mirror on old data. | Cause: The ‘last_owner’ flag file was not created on the source. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104187 | WARN | $REM_MACH has ${REM_TAG}_last_owner file, create flag ${FLAGTAG}_data_corrupt. | Cause: The system listed had the mirror in-service last. Action: The system listed has the last_owner file that indicates it has the most recent data and is most likely the best system to in-service the mirror to avoid losing data. |
| 104188 | WARN | $REM_MACH is not alive, create flag ${FLAGTAG}_data_corrupt. | Cause: The system listed is not alive. Action: Since the system listed is not alive, it cannot be determined whether that system was a more recent mirror source than the local system. Therefore the local system should not automatically be allowed to bring the mirror in-service. |
| 104190 | ERROR | [$SUBJECT event] mail returned $err | Cause: The email to notify when DataKeeper resynchronization is complete failed. The details of the error will be displayed following this message. |
| 104191 | ERROR | COMMAND OUTPUT: cat /tmp/err$$ | Cause: The email to notify when DataKeeper resynchronization is complete failed. The details of the error is displayed in this message. |
| 104193 | ERROR | snmptrap returned $err for Trap 143 | Cause: SNMP trap 143 to notify when DataKeeper resynchronization is complete failed. The details of the error will be displayed following this message. |
| 104194 | ERROR | COMMAND OUTPUT: cat /tmp/err$$ | Cause: SNMP trap 143 to notify when DataKeeper resynchronization is complete failed. The details of the error are given in this message. |
| 104196 | ERROR | $msg | Cause: The kernel does not support async replication. The message will provide more details on the failure. Action: Do not configure asynchronous replication while using this kernel per the details in the message. |
| 104197 | WARN | $msg | Cause: The is_async_supported returned a warning message specifying some conditions to be aware when replicating asynchronously. Action: Verify that the condition of the warning does not apply to this configuration. Synchronous replication may be necessary. |
| 104200 | EMERG | Continue to wait for %s to merge bitmap and do partial resyncs to all targets, no timeout set. | Cause: In a multi-target configuration targets will not be configured until the previous source is available to merge its bitmap so that all targets will be able to partially resynchronize. The LKDR_WAIT_ON_PREVIOUS_SOURCE_TIMEOUT entry in /etc/defaults/LifeKeeper is set to “-1” to wait indefinitely. Action: Check on the status of the previous source listed in the message and resolve any issues that are preventing it from rejoining the cluster. |
| 104201 | EMERG | To stop waiting for the previous source (forcing a full resync to remaining waiting targets) run: \"%s/bin/mirror_action %s fullresync %s %s\" on %s. | Cause: In a multi-target configuration targets are not being configured, waiting on the previous source to rejoin the cluster. Action: Run the command listed in the message to force an immediate full resynchronization to this target and any remaining targets waiting to be resynchronized. |
| 104202 | EMERG | Continue to wait for %s to merge bitmap and do partial resyncs to all targets. Continue to wait %d more seconds. | Cause: In a multi-target configuration targets will not be configured until the previous source is available to merge its bitmap so that all targets will be able to partially resynchronize. The LKDR_WAIT_ON_PREVIOUS_SOURCE_TIMEOUT entry in /etc/defaults/LifeKeeper is set to the number of seconds to wait. If the previous source does not join the cluster in that time then targets will be added with a full resynchronization. Action: Check on the status of the previous source listed in the message and resolve any issues that are preventing it from rejoining the cluster. |
| 104203 | EMERG | To stop waiting for the previous source (forcing a full resync to remaining waiting targets) run: \"%s/bin/mirror_action %s fullresync %s %s\" on %s. | Cause: In a multi-target configuration targets are not being configured, waiting on the previous source to rejoin the cluster. Action: Run the command listed in the message to force an immediate full resynchronization to this target and any remaining targets waiting to be resynchronized. |
| 104207 | ERROR | Failed to create "data_corrupt" flag file on "%s". | Cause: The ‘data_corrupt’ flag file was not created on the source listed. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104208 | ERROR | Failed to create "data_corrupt" flag file on target "%s". | Cause: The ‘data_corrupt’ flag file was not created on the target listed. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104209 | ERROR | Failed to create "data_corrupt" flag file on "%s". | Cause: The ‘data_corrupt’ flag file was not created on the source listed. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104210 | ERROR | Failed to create "data_corrupt" flag file on target "%s". | Cause: The ‘data_corrupt’ flag file was not created on the target listed. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104211 | ERROR | Failed to create "data_corrupt" flag file on target "%s". | Cause: The ‘data_corrupt’ flag file was not created on the target listed. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104212 | ERROR | The \"source\" flag file on %s to track mirror source does not exist. Full resync to remaining targets is required. | Cause: The ‘source’ flag file should exist on the system and without it the consistency of the mirror can not be verified. A full resync is required to assure data reliability. All targets not already being mirrored will require a full resync. Action: Check the LKROOT (/opt/LifeKeeper) file system for error or that it is full. |
| 104214 | ERROR | Failed to create \"source\" flag file on %s to track mirror source. | Cause: The ‘source’ flag file was not created on the specified system to track the mirror source. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104216 | ERROR | Failed to create "data_corrupt" flag file on target "%s". | Cause: The ‘data_corrupt’ flag file was not created on the target listed. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104218 | ERROR | Failed to create "data_corrupt" flag file on target "%s". | Cause: The ‘data_corrupt’ flag file was not created on the target listed. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full |
| 104221 | ERROR | Failed to create \"last_owner\" flag file on %s to track mirror source. This may allow in-service of mirror on old data. | Cause: The ‘last_owner’ flag file was not created on the target listed. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104222 | ERROR | Failed to create "last_owner" flag file to track mirror source". This may allow in-service of mirror on old data. | Cause: The ‘last_owner’’ flag file is used to know where the mirror was last in-service. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104223 | ERROR | Failed to create "last_owner" flag file to track mirror source". This may allow in-service of mirror on old data. | Cause: The ‘last_owner’’ flag file is used to know where the mirror was last in-service. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104224 | ERROR | Failed to create \"previous_source\" flag file. | Cause: The ‘previous_source’ flag file was not created. This is needed to merge the previous source bitmap to avoid a full resync. Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full. |
| 104227 | ERROR | Failed to set %s to %s. | Cause: This message indicates a failure to set a sysfs parameter for the nbd driver (/sys/block/nbdX). Action: It may be necessary to adjust one or more of: NBD_NR_REQUESTS in /etc/default/LifeKeeper to avoid this error. |
| 104232 | ERROR | Mirror resize failed on %s (%s). Could not set size to %d. | Cause: The mirror resize operation failed. |
| 104233 | ERROR | Mirror resize failed on %s (%s). Could not set bitmap to %s and bitmap-chunk to %d. | Cause: The mirror resize operation failed. |
| 104234 | ERROR | The mirror %s failed to resize. You must successfully complete this operation before using the mirror. Please try again. | Cause: The mirror resize operation failed. |
| 104235 | ERROR | mirror_resize of mirror %s failed due to signal "%s". | Cause: The mirror resize operation failed. |
| 104236 | EMERG | Resource "%s" is "OSF". The mirror "%s" will wait to replicate data until all resources in the hierarchy%s are in-service. This may indicate inconsistent data. Verify the data is correct before replicating data; replication will continue when all resources in the hierarchy%s are in-service. A full resync may be necessary (see "LKDR_WAIT_TO_RESYNC" in /etc/default/LifeKeeper). | Cause: The specified resource is OSF. This prevents replication until this resource is repaired. The LKDR_WAIT_TO_RESYNC setting in /etc/default/LifeKeeper determines what resources must be in-service before replication is allowed. Action: Determine the cause of the corruption and repair. This may involve bringing the resource in-service on another node. A full resync is most likely required once the data is repaired. |
| 104237 | WARN | Resource "%s" is "OSU". The mirror "%s" will wait to replicate data until all resources in the hierarchy%s are in-service. To replicate data immediately run: "%s/bin/mirror_action %s resume" on "%s" (see "LKDR_WAIT_TO_RESYNC" in /etc/default/LifeKeeper). | Cause: The specified resource is not in-service and is required before replication is resumed during a restore operation. Action: Bring the required resources in-service to resume replication. Replication can also resume using the GUI command to resume or using the mirror_action command. |
| 104238 | ERROR | Unable to read $nbd_taint_file. Assuming that the SIOS ‘nbd’ kernel module is not loaded. | Cause: The /sys/module/nbd/taint file could not be opened for reading. Action: Verify that the /sys/module/nbd/taint file exists and is read-enabled. |
| 104239 | EMERG | $failure_msg | Cause: At least one kernel module required by SIOS DataKeeper failed to load. Action: Verify that the current running kernel is supported by this version of SIOS Protection Suite for Linux. If the kernel was recently updated, re-run the SIOS Protection Suite for Linux setup script located on the SIOS installation media to install kernel modules that are compatible with the current running kernel. |
| 104242 | ERROR | Unable to read /proc/modules. Assuming that the SIOS ‘$module’ kernel module is not loaded. | Cause: Unable to read /proc/modules. Action: Verify that the /proc/modules file exists and is read-enabled. |
| 104243 | ERROR | Internal script or routine $caller was called for unsupported kernel module ‘$module’. Supported kernel modules for this script or routine are: $module_list. | Cause: The given script or routine was called for an unsupported kernel module. Action: This is an internal error. Please contact SIOS Customer Support. |
| 104244 | ERROR | Output from ‘modprobe $module’ command: $pretty_modprobe_out | Cause: Failed to load the given kernel module using the modprobe command. Action: Inspect the output provided in the log message from the failed modprobe attempt and resolve any issues found there. |
| 104251 | ERROR | There is no LifeKeeper protected resource with tag $tag on system $me. | Cause: The given tag does not correspond to a LifeKeeper protected resource on the given system. Action: Verify that the resource tag and system name are correct. |
| 104252 | ERROR | Resource $tag is not a $app/$typ resource. Please use the $ins_app/$ins_typ resource-specific canfailover script instead. | Cause: The scsi/netraid-specific canfailover script was called for a non-scsi/netraid resource. Action: Use the canfailover script, if it exists, corresponding to the appropriate app and type of the given resource. |
Cause: The scsi/netraid-specific canfailover script was called for a non-scsi/netraid resource.
Action: Use the canfailover script, if it exists, corresponding to the appropriate app and type of the given resource.
Post your comment on this topic.