Use Control F to search for a specific error code.
| 1 | Info | The SteelEye DataKeeper driver version 7.0 has started successfully. | ||
| 2 | Error | The SIOS DataKeeper driver could not be started since the system is running an unsupported version of the operating system. Required OS Version: %t%2.%3 Build %4 Current OS Version: %t%5.%6 Build %7 |
||
| 16 | Warning | The mirrored state of a Source volume has been changed. | Unable to write data to the Target | Can’t successfully send the data packet to the target and receive a reply. |
| 16 | Warning | The mirrored state of a Source volume has been changed. | Source was unable to complete volume write | Temporarily cannot add a write request to the Async Queue. Temporarily out of Non Paged Memory |
| 16 | Warning | The mirrored state of a Source volume has been changed. | The High Water mark has been reached in the Async Write Queue | The number of writes in the Async Queue has reached the High Water Mark. Mirror must Pause and the Resync to catch up. Typically occurs during periods of peak write activity on the source volume. |
| 16 | Warning | The mirrored state of a Source volume has been changed. | Mirror Deleted. | Mirror was deleted |
| 16 | Warning | The mirrored state of a Source volume has been changed. | Mirror in Mirror state on boot | Normal message when a Source system boots up |
| 16 | Warning | The mirrored state of a Source volume has been changed. | Mirror in Resync Pending state on boot. | Typically occurs when the original Source system fails. The original Target system becomes the new Source of the mirror while the original source is down. When the original Source system comes back up, it sees that the original Target system is now the Source. The orginal Source system becomes the new Target. A partial resync will be performed. |
| 16 | Warning | The mirrored state of a Source volume has been changed. | The Low Water mark has been reached in the Async Write Queue | If the mirror pauses due to hitting the high water mark or because of running out of non paged memory, when all entries in the Async queue have been freed, the mirror state transitions from the Paused state into the Resync state and a partial resync begins. |
| 16 | Warning | The mirrored state of a Source volume has been changed. | Resync after re-connecting with the Target. | Normal message when Source and Target reconect after they have been disconnected. |
| 16 | Warning | The mirrored state of a Source volume has been changed. | Automatic Partial Resync Initiated | |
| 16 | Warning | The mirrored state of a Source volume has been changed. | Mirror Resynchronization. | |
| 16 | Warning | The mirrored state of a Source volume has been changed. | Merge of target bitmap failed | |
| 16 | Warning | The mirrored state of a Source volume has been changed. | Resync Failure | |
| 16 | Warning | The mirrored state of a Source volume has been changed. | Unable to send packet request to the Target. | Problem sending write requests to the Target volume. |
| 16 | Warning | The mirrored state of a Source volume has been changed. | Resync after re-connecting with the Target. | |
| 16 | Warning | The mirrored state of a Source volume has been changed. | Cannot start target thread – mirror is in Source mode. | |
| 16 | Warning | The mirrored state of a Source volume has been changed. | Mirror Resynchronization. | |
| 17 | Error | An invalid attempt was made to change the state of a Source volume. The volume will remain in state %3. | ||
| 18 | Error | A partition that is currently involved in a mirror has been modified. As a result, the mirror will be broken. Volume Device: %t%1 Volume Letter: %t%2 Current State: %t%3 In the future, please break all mirrors on a physical disk before re-partitioning that disk in order to ensure the integrity of data on the mirrored volumes. |
||
| 19 | Warning | The driver has determined that the file system is invalid. | ||
| 20 | Warning | The mirrored state of a Target volume has been changed. | Mirror Resynchronization. | |
| 20 | Warning | The mirrored state of a Target volume has been changed. | Mirror Resynchronization. | |
| 20 | Warning | The mirrored state of a Target volume has been changed. | Mirror Deleted. No targets remain. | |
| 20 | Warning | The mirrored state of a Target volume has been changed. | Mirror Resynchronization. | |
| 20 | Warning | The mirrored state of a Target volume has been changed. | Mirror Resynchronization. | |
| 21 | Warning | The mirror role of the volume has been changed. | Mirror Resynchronization. | |
| 22 | Warning | Unable to connect to the target machine for this volume. | Mirror Resynchronization. | |
| 23 | Warning | The mirror role of the volume has been changed. | Mirror Created. | System has become the Source of the mirror as a result of a Create Mirror command. |
| 23 | Warning | The mirror role of the volume has been changed. | Mirror Created. | System has become the Source of the mirror as a result of a Create Mirror command. |
| 23 | Warning | The mirror role of the volume has been changed. | Mirror Deleted. No targets remain. | System is no longer the Source of the mirror as a result of a Delete Mirror command. |
| 23 | Warning | The mirror role of the volume has been changed. | Mirror Created. | System has become the Target of the mirror as a result of a Create Mirror command. |
| 23 | Warning | The mirror role of the volume has been changed. | Mirror Deleted. No targets remain. | System is no longer the Target of the mirror as a result of a Delete Mirror command. |
| 33 | Error | Unable to connect to the target machine for this volume. | Related to Event 167 – Cannot lock Target Volume (Check Distributed Link Tracking service, Firewall) | |
| 34 | Error | An error occurred while writing a connection header to the target. The will be broken. The error code above is a driver status value. |
||
| 35 | Warning | Writes to this volume will no longer be mirrored to the target. The mirror will be broken. | ||
| 37 | Error | A write to the local (source) disk has failed. | ||
| 38 | Error | A write to the local (source) disk has been cancelled. Cancelling of writes is not supported for mirrored drives. |
||
| 39 | Error | The DataKeeper driver failed to queue a volume write. | ||
| 40 | Error | Cannot create a mirror on the drive where persistent bitmap files are stored. Mirror creation has been terminated. To create a mirror on this volume, change the BitmapBaseDir value in the ExtMirr driver Parameters registry key to use a different drive, and reboot. |
||
| 48 | Warning | The mirror has been deleted. | ||
| 49 | Warning | The mirror has been deleted. However, since the delete was performed during a mirror resynchronization, or before a previously-interrupted resynchronizaion was ever completed, the contents of the volume may be corrupted. | The source and target volumes are not in sync. | If a mirror is deleted during a RESYNC, the data on the target volume may not be in a sound state. Reformat target volume. |
| 50 | Warning | The mirror has been commanded to failover. | ||
| 58 | Error | An error occurred while writing a keep-alive packet over the network. | Error Code 0×102 | Temorary Network interruption to Target system – Info only – no action required |
| 59 | Error | An error occurred while writing a keep-alive packet over the network. The mirror will be BROKEN. |
||
| 64 | Error | An error occurred while writing a keep-alive packet over the network. The mirror will be PAUSED. |
||
| 65 | Error | An error occurred while writing data to the target over the network. The mirror will be BROKEN. |
||
| 66 | Error | An error occurred while writing data to the target over the network. The mirror will be PAUSED. |
||
| 67 | Error | An error occurred while attempting to read the response from the target machine over the network. The mirror will be broken. |
||
| 68 | Error | The target machine has reported an error in writing the sent data to its disk. The mirror will be broken. |
||
| 69 | Warning | A network error occured while transmitting data to the target machine. An attempt will be made to reconnect with the target system without losing any mirrored write. The mirror will not be broken at this time. |
||
| 70 | Error | There was an error after attempting to reconnect to the target system. The mirror will be broken. |
||
| 71 | Info | Successfully recovered from a network failure. | ||
| 72 | Error | Error creating a volume named pipe. | ||
| 73 | Error | Error connecting to the existing volume named pipe, although the Target Control Thread is alive. The EM service will attempt to restart the volume pipe. |
||
| 96 | Info | A mirror resynchronization has begun. | ||
| 97 | Info | The mirror resynchronization has completed successfully. | ||
| 98 | Warning | During Resynchronization, a large number of passes to update the mirror has been made due to incoming writes. In order to ensure that the resynchronization will complete soon, please stop all write access to the volume. | This can occur if there is a process constantly writing to the Source volume. Even if it is only writing a small amount, as soon DK makes one pass through the bitmap file, more bits are marked dirty and another pass is required. | |
| 99 | Info | The mirror resynchronization has failed. | ||
| 100 | Error | The mirror resynchronization has been aborted due to a mirror state change. |
||
| 101 | Error | The mirror resynchronization has been aborted due to an error reading a block from the source volume. |
||
| 128 | Warning | This volume was not shutdown cleanly. As a result, the mirror could not be continued. An automatic mirror resynchronization will be performed to ensure that the source and target are in sync. |
||
| 129 | Warning | The mirror on this volume could not be continued as the volume was not in None state at the time of a system shutdown. An automatic mirror resynchronization will be performed to ensure that the source and target are in sync. |
||
| 130 | Warning | A continue of the mirror on this volume could not be performed as the volume was not in None state. This could be due to writes received during boot before a connection could be made to the target machine. An automatic mirror resynchronization will be performed to ensure that the source and target are in sync. |
||
| 131 | Warning | SIOS DataKeeper was told to continue a mirror on this volume during a system boot, but the registry value ““AutoResyncOnBoot”“ was set to 2. This indicates that the volume should always be resynchronized in the event of a system reboot. As a result, an automatic mirror resynchronization will be performed to ensure that the source and target are in sync. |
||
| 132 | Warning | SIOS Datakeeper was told to continue a mirror on this volume, but the registry value ““AutoResyncOnContinue”“ was set to 2. This indicates that the volume should always be resynchronized when continued. As a result, an automatic mirror resynchronization will be performed to ensure that the source and target are in sync. |
||
| 133 | Info | The mirroring of this volume will be continued. | ||
| 134 | Info | The mirroring of this volume will be continued. | ||
| 135 | Info | A mirror will be created for this volume. | ||
| 136 | Warning | A continue of the mirror could not be performed because the target drive was out of sync with the source. An automatic mirror resynchronization will be performed to ensure that the source and target are in sync. Volume Device: %t%1 |
||
| 137 | Error | The target side of the mirror creation has failed. | There was an error creating the thread to handle the mirroring activities. Error Code: 0xC0000055 |
Target volume is locked or corrupt. See if the volume is calling for a chkdsk or if a process has an open handle to the volume. (Check for Anti Virus sw) |
| 144 | Warning | The volume could not be locked as requested. | There was an error locking the volume. Error Code: 0xC0000055 |
Target volume is locked or may be corrupt. See if the volume is calling for a CHKDSK in the event log or if a process has an open handle to the volume. (e.g. Check for Anti-virus software) |
| 145 | Error | The volume could not be opened to lock it. | There was an error opening the volume 0xC000022 or 0xC000000D | 0xC000000D – Verify sector size of volume is 512 bytes |
| 146 | Info | The volume has been locked as requested | There was no error locking the volume. | Standard message when locking a target volume (mirror create, lock volume command) |
| 147 | Warning | The volume has been unlocked as requested | There was no error unlocking the volume | Standard message when unlocking a target volume (mirror delete, unlock target command) |
| 148 | Warning | The volume has not been unlocked as requested | There was an error opening the volume. The error code above is a driver status value. Error Code : 0xC000026E |
|
| 149 | Info | Open handles have been detected on this volume while trying to lock it. | The EM driver will attempt to get an exclusive lock on this volume. Applications with open handles to this volume might report file corruption. | Initial attempt to lock the volume so it can become the target – Information only |
| 150 | Error | An invalid attempt to establish a mirror occurred. Both systems were found to be Source. This may have been due to all of LifeKeeper’s Comm Paths being disconnected, the reconnected later, or by bringing the mirror into service on each of the systems individually without being able to contact the other system. | The mirror has been paused, or left in its current non-mirroring state. To re-establish the mirror, reboot the system which should become target and manually continue the mirror from the source while the other is booting. Otherwise, delete the mirror on both systems and manually recreate it. | This is a SPLIT-BRAIN scenario where both systems believe they are the SOURCE of the mirror. Resolve using the DK GUI or the LK GUI |
| 15 1 | The target volume could not be accessed/locked during mirror creation. This could be because other processes have open handles on this volume, or the filesystem is corrupted. |
|||
| 152 | Info | During the process of locking the target volume the driver has responded to IOCTL_DISK_IS_WRITABLE with a status code STATUS_MEDIA_WRITE_PROTECTED. | The media is now write protected. | Normal message for a Target volume during bootup |
| 153 | Warning | The user has deleted the drive letter assignment from a volume that is part of a mirror. Unless the drive letter mapping is re-established, this mirror will not be in a usable state. | Current Role: Target | The volume letter currently defined in a DataKeeper mirror has been deleted from the OS. The mirror can no longer function. |
| 154 | The DataKeeper driver could not open the registry key. | |||
| 155 | Error | The DataKeeper driver could not query the registry value. | Volume Device: Registry Value: MirrorRole Error Code: 0xC0000034 |
|
| 156 | Info | Unable to get filesystem info (FSCTL_GET_NTFS_VOLUME_DATA). | ||
| 160 | Info | BEFORE %t%1 | ||
| 161 | Info | AFTER %t%1 | ||
| 162 | Warning | Unable to allocate storage for RemoteTargetInfo structure. | ||
| 163 | Error | The source system for this mirror has been changed. | Previous Source: 192.168.3.90 New Source: 192.168.3.91 |
|
| 164 | Error | Unable to allocate storage during mirror creation. | ||
| 165 | Info | Cannot unlock target volume during resync, or until a previously-interrupted resync has been completed. | User attempted to unlock the target volume during a resync operation. This is not allowed as the data on the target volume is potentially unusable. Allow the resync to complete. | |
| 166 | Warning | The remote system reports that a different machine is now the source for its mirror. The local mirror will be paused. To re-establish the mirror with this system as source, delete the current active mirror to the remote system, and continue the mirror from this system. |
||
| 167 | Error | Unable to connect to the volume port | 0xC0000055 | In DK prior to v7.1.2, there was a TDI disconnect issue where we often saw this problem. In that scenario, DK was deadlocked waiting for the target to respond. However, the target already resonpended to the source in a 0 byte reply which the source system doesn’t recognize. Reboot target system. |
| 167 | Error | Unable to connect to the volume port | Failed Operation = Connect 0xC0000120 – Port 10011 0xC0000236 – Port 0 0xC000023C – Port 10011 0xC000023D – Port 10011 |
This could be Port 0 or Port 100xx. If port 0, then problem on dispatch port (9999 by default). Verify SRC and TRG are communicating via same dispatch port. Verify no port 9999 conflict on Target. Also check to see if there is a leftover piece of the mirror still configured via GETMIRRORVOLINFO (seen during Switchover when mirror is recreating): Use SOLUTION 465 to troubleshoot |
| 167 | Error | Unable to connect to the volume port | Failed Operation = Read 0xC0000120 – Port 10011 0xC000020D – Port 10011 |
|
| 167 | Error | Unable to connect to the volume port | Failed Operation = Targ Err Port 0 Port 10004 |
This could be Port 0 or Port 100xx. If port 0, then problem on dispatch port (9999 by default). Verify SRC and TRG are communicating via same dispatch port. Verify no port 9999 conflict on Target. Also check to see if there is a leftover piece of the mirror still configured via GETMIRRORVOLINFO (seen during Switchover when mirror is recreating): Use SOLUTION 465 to troubleshoot |
| 168 | Error | Unable to initialize mirror on the target machine. | Failed Operation: Dispatch Port Connect: Error Code: 0xC0000120 Error Code: 0xC0000236 |
Dispatch Port = 9999 by default. Reboot Target, verify no port conflict on 9999 on Target – for 0xC0000236, check for ClearSwitchover event id 200 on TARGET |
| 168 | Error | Unable to initialize mirror on the target machine. | Failed Operation: Target reports error Error Code: 0xC0000236 ErrorCode: 0xC0000055 ErrorCode: 0xC000100x |
0055 is a semaphore timeout and DK is usually locked… saw that with TDI disconnect issues (TDI disconnect issues were resolved in DK v7.1.2) |
| 168 | Error | Unable to initialize mirror on the target machine. | Failed Operation: Named Pipe Connect Error Code: 0xC00000BE |
|
| 168 | Error | Unable to initialize mirror on the target machine. | Failed operation: Read Response Error Code: 0xC0000120 |
|
| 168 | Error | Unable to initialize mirror on the target machine. | Failed operation: Named Pipe Connect | look for Event ID 200 on Target side to see if CLEARSWITCHOVER FLAG is set |
| 169 | Warning | Unable to create bitmap to track writes on the target volume. This volume will not be able to be unlocked in read-write mode until a successful bitmap creation occurs, following a full or partial resync with the source, or following a reboot. | ||
| 176 | Error | Unable to allocate memory for bitmap – mirror creation has failed | ||
| 177 | Error | Unable to create persistent file for bitmap. The persistent bitmap for this mirror will be marked Invalid. | Error Code 0xC0000022 Error Code: 0xC000007F Error Code: 0xC0000034 |
|
| 178 | Warning | Unable to delete persistent bitmap file. | ||
| 179 | Error | Unable to create BitmapWrite thread. The persistent bitmap for this mirror will be marked Invalid. | ||
| 180 | Error | The BitmapBaseDir value is not found in the ExtMirr\Parameters registry key, or the value found is not a valid path. Persistent Bitmap file creation will be disabled. The BitmapBaseDir value should be a REG_SZ value that contains the full path to the directory where persistent bitmaps should be created – normally the Bitmaps directory in the DataKeeper install directory. |
||
| 181 | Error | Unable to set the BitmapFileEnabled flag. | ||
| 182 | Error | Unable to set the BitmapFileValid flag. | ||
| 183 | Error | Unable to read data from the persistent bitmap file. | ||
| 184 | Error | Unable to write data to the persistent bitmap file. | ||
| 185 | Error | Unable to allocate memory to report target dirty bitmap. Mirror will be paused on the source system. | ||
| 186 | Error | Unable to receive target’s dirty bitmap list. | Error Code: 0×102 (Status timeout) Error Code: 0xC0000240 |
During initialization of resync, there was a communication error retrieving the list of dirty blocks from the target system. Usually due to bad network. C00000240 is STATUS_REQUEST_ABORTED – this just comes from the TCP driver. |
| 187 | Error | Unable to allocate memory to read bitmap file. The persistent bitmap for this mirror has been marked invalid. | ||
| 188 | Error | Unable to determine sector size or filesystem cluster size for disk where bitmap files are stored. The persistent bitmap for this device cannot be created. Please verify that the BitmapBaseDir registry value in the ExtMirr driver Parameters key is set to the correct path. BitmapBaseDir is currently set to >. | Occurs during CREATE MIRROR | Check to make sure user is logged in with domain admin privileges. Saw this where customer was a Domain User with Local Admin rights. Bitmap file never got created until we logged in with Domain Admin privs. Sequence is Event 188, 177, 210 |
| 189 | Error | Failover was detected on this volume. The Persistent Bitmap file was not in a valid state when the system went down, so a full resync will be performed. | ||
| 192 | Error | ending disk write tracking during switchover of volume %2. Remaining mirror creation will require full resync. | ||
| 196 | Warning | An attempt to merge the bitmap from a writable target was made, but the bitmap bitmap file for one or more targets was not valid. Bits cannot be saved – a full resync to all targets is required after switchover. |
||
| 197 | Warning | An attempt to merge the bitmap from a writable target was made, but the target was not successfully queried for its bitmap file report, possibly due to a network failure. A full resync to all targets will be required after switchover. |
||
| 198 | Warning | The drive letter (2:) was unassigned from the volume containing DataKeeper bitmap files. | ||
| 199 | Error | Mirror creation failed due to an error creating the persistent bitmap file. | ||
| 200 | Error | Target-side mirror creation failed due to the switchover flag being set for this volume (G:). Use the CLEARSWITCHOVER option in EmCmd to clear this flag. | Use the CLEARSWITCHOVER option in EmCmd to clear this flag. | |
| 201 | Info | |||
| 202 | Info | The DataKeeper driver has detected that networking is now available. | ||
| 203 | Error | Mirror switchover failed due to the error below. | Reason: Unable to lock volume Reason: Unable to delete mirrors |
|
| 204 | Error | Target Dispatch thread detected a conflict on port 000000000100300001000000CC00A0CD000000000000000000000000000000000000000000000000. This port may be in use by some other service or application. | Reboot system or see if there is a port conflict on Dispatch Port (9999 by default) | |
| 205 | Info | Creating bitmap file in default location for volume P:\ for target 192.168.1.206 | Info only – no action required | |
| 206 | Info | Creating bitmap file on shared volume I:\ for target 80.80.90.135. | Info only – no action required | |
| 207 | Error | Unable to determine sector size or filesystem cluster size for shared disk. The persistent bitmap for this volume to the target machine listed below cannot be created. | ||
| 208 | Error | Unable to allocate memory during persistent bitmap file creation. The persistent bitmap for this volume to the target machine listed below cannot be created. | ||
| 209 | Error | The persistent bitmap file for this mirror is invalid, but there was an error creating the shared invalid file. All writes to this volume will be failed until the system is rebooted. | ||
| 210 | Error | There was an error writing to or reading from the persistent bitmap file for this mirror. The persistent bitmap file will not be used. | ||
| 211 | Error | The shared volume is now being used by another system. This system will block access to the volume, and any mirrors that were in place will be deleted. | ||
| 212 | Info | Successfully created new bitmap file for volume I:\ for target 80.80.90.135. | ||
| 213 | Info | Pending multi-target switchover to source for volume I: complete. | ||
| 214 | Error | Ending disk write tracking during switchover of volume %2. Remaining mirror creation will require full resync. | ||
| 215 | Error | Write tracking is off during switchover of volume %2. Creating mirror to target %3 with full resync. | ||
| 216 | Info | Conditional mirror create fails for volume Q due to incorrect role. | ||
| 217 | Info | Correct role for conditional mirror create on volume S | ||
| 218 | Cannot restore mirror for volume %2 on shared target. | |||
| 219 | Warning | A full resync of volume I to target IP 80.80.90.135 is needed. | FULL RESYNC | |
| 220 | Info | Resync of volume to target IP 80.80.90.135 starting with 524288 bytes to resync. | PARTIAL RESYNC | Info only – no action required |
| 222 | Error | Volume ? is being removed from the system while still part of a mirror | ||
| 223 | Warning | Mirror was Paused due to system shutdown; reverting state to Mirroring to avoid split brain |
||
| 225 | Error | Target volume size is smaller than source. | ||
| 226 | Error | Global bitmap volume %2 has not been detected yet. Mirror source threads may hang if this volume does not exist. Check to make sure that the BitmapBaseDir registry entry specifies a valid volume for storage of bitmaps. | ||
| 227 | Error | Snapshot %3 operation for volume %2 failed with status %4. Disabling snapshot and locking volume. | ||
| 228 | Info | Snapshot successfully enabled for volume %2 | ||
| 229 | Info | Snapshot for volume %2 disabled. | ||
| 230 | Warning | Request to initiate snapshot on target %2 volume %3 failed. Mirror was not in the mirroring state at the time of the request. | ||
| 231 | Warning | “Request to initiate snapshot on target %2 volume %3 failed with status %4. | ||
| 232 | Warning | Unable to read Snapshot Device from registry for volume %2. | ||
| 233 | Warning | Invalid Snapshot Device registry value for volume %2. Line %3. | ||
| 234 | Warning | Cannot enable snapshot for volume %2 – volume size is 0. | ||
| 235 | Warning | Cannot enable snapshot for volume %2 – bitmap allocation failed – out of memory. | ||
| 236 | Warning | Cannot enable snapshot for volume %2 – snapshot thread creation failed with status %3. | ||
| 237 | Warning | While disabling snapshot for volume %2, unable to lock volume (status %3). | ||
| 238 | Error | Volume %2: Mirror role is Source, but no targets found in the registry. Changing role to None and forcing full resync. | ||
| 239 | Info | Wrote the following string to SharedOwner file on volume %2: | ||
| 240 | Info | Read the following string from SharedOwner file on volume %2: | ||
| 241 | Warning | Data read from the shared owner file on volume %2 was unexpected – does not appear to be a string. | ||
| 242 | Warning | Data to be written to the shared owner file on volume %2 was unexpected – does not appear to be a string. | ||
| 243 | Error | Cannot claim ownership of shared volume %2 – Unable to start the Shared Owner watch thread, status %3. | ||
| 244 | Error | Cannot claim ownership of shared volume %2 – unable to create Shared Owner file, status %3. | ||
| 245 | Error | Cannot claim ownership of shared volume %2 – unable to get our ComputerName, status %3. | ||
| 246 | Error | Cannot claim ownership of shared volume %2 – unable to allocate buffer for shared file I/O, status %3. | ||
| 247 | Error | Failed to read or write Shared Owner file for shared volume %2. Status %3. | ||
| 248 | Error | During volume lock of shared volume %2, failed to initiate thread to modify Shared Owner file, status %3. | ||
| 249 | Error | Unable to unlock shared volume %2, failed to claim shared owner file, status %3. | ||
| 250 | Warning | Unable to allocate target sequence tracking array. This is not a major error but may result in a full resync in the event of a failover. | ||
| 251 | Info | Successfully allocated target sequence tracking array. | ||
| 252 | Warning | Unable to allocate target sequence tracking list entry. This is not a major error but may result in a full resync to some targets in the event of a failover. | ||
| 253 | Error | An invalid packet payload of type %2 was encountered. | ||
| 254 | Error | A received packet payload goes over the end of the total packet size. | ||
| 255 | Error | The data received in the packet payload was not in the expected form. | ||
| 256 | Warning | Received a duplicate packet payload of type %2. | ||
| 257 | Warning | Unable to allocate a flush header – this may indicate a memory shortage. It is not a critical DataKeeper error. | ||
| 258 | Warning | DataKeeper sequence number tracking encountered a condition that could lead to a full resync. | ||
| 259 | Warning | DataKeeper sequence number tracking encountered a condition that could lead to a full resync to the given target. | ||
| 260 | Warning | DataKeeper sequence number tracking encountered a condition that requires a full resync. | ||
| 261 | Warning | DataKeeper sequence number tracking encountered a condition that requires a full resync to the given target. | ||
| 262 | Error | An invalid response packet was received from the target system. A display of the relevant sequence numbers is given below. | ||
| 263 | Error | Unable to set the value for the mirror. | ||
| 264 | Error | The state of this mirror changed to a Non-Mirroring state, but the cluster was not notified within the specified timeout. All pending writes to this volume will be failed, and the volume will be locked. | ||
| 265 | Error | The state of this mirror changed to a Non-Mirroring state, but the attempt to notify the cluster failed. All pending writes to this volume will be failed, and the volume will be locked. | ||
| 266 | Warning | An invalid attempt to establish a mirror occurred. The volume on the remote system is now a Target for a different Source system. | ||
| 267 | Warning | Mirror create fails for shared volume %2 – ineligible to become a target. | ||
| 268 | Warning | Unable to allocate storage for SavedBitmapInfo structure during switchover. | ||
| 269 | Warning | Unable to allocate an MDL packet in the current chaining loop (#%2). This may indicate a memory shortage. It is not a critical DataKeeper error. | ||
| 270 | Error | Unable to initialize RemoteTargetInfo structure. | ||
| 271 | Error | Unexpected device removal during mirror initialization – aborting mirror creation. | ||
| 272 | Error | An invalid attempt to establish a mirror occurred. Both systems were found to be Source. | ||
| 273 | Error | Source and target volume sector sizes don’t match. | ||
| 274 | Error | Unexpected device removal – driver was not previously notified to clean up. | ||
| 275 | Info | Initiate switchover to source for volume %2. | ||
| 276 | Error | Switchover to source for volume %2 failed – %3. | ||
| 277 | Error | An invalid attempt to establish a mirror occurred. Both systems were found to be Source. | ||
| 278 | Error | At the last reboot, there were writes on volume %2 which were not tracked in a persistent bitmap. A full resync of this volume is required. | ||
| 279 | Info | Incoming writes are being temporarily blocked in order to allow mirror resync to complete. | ||
| 280 | Info | Resync complete – unblocking writes. | ||
| 281 | Error | The resync unblock timer expired – unblocking writes and terminating resync. |
Post your comment on this topic.