This appendix describes the error code and detailed error messages output by the ETERNUS Disk storage system, which were inserted into the messages.
If an error message not shown in this table appears, a hardware failure may have occurred. In such an event, contact a Fujitsu customer engineer.
Error | Error Message | Explanation | Action Plan |
|---|---|---|---|
2 | invalid logical volume name. | The specified copy source or destination device is not found. | This message may be displayed when a Logical Unit (disk)-to-Logical Unit (disk) copy is done between different operating systems. If so, the operation design should be reviewed. Refer to "Notes on Executing Copy Between Different Operating Systems" in "Notes on Operations" in the AdvancedCopy Manager Operation Guide for details. In the case other than mentioned above, check that the slice information exists on the copy source or destination device. |
3 | invalid extent number. | An internal conflict occurred. | Ask Fujitsu Technical Support to collect the information required for troubleshooting. (*1) |
4 | invalid source BoxID. | An internal conflict occurred. | |
5 | invalid destination BoxID. | An internal conflict occurred. | |
6 | invalid source OLU. | The specified copy source or destination device is not found. | Check the partition information for the copy source device. |
7 | invalid destination OLU. | The specified copy source or destination device is not found. | Check the partition information for the copy destination device. |
8 | invalid extent. | The copy source or destination device does not exist. | Check the slice information on the copy source or destination device. |
A copy restart operation was executed for the session in which Reverse/Mode Change terminated abnormally due to a path error between the boxes and caused an error related to the ETERNUS Disk storage system of the copy source or the copy destination device. | After recovering the path between the boxes, perform the following steps:
Refer to "Command References" in the AdvancedCopy Manager Operation Guide for information on the commands. | ||
11 | invalid source extent size. | An internal conflict occurred. | Ask Fujitsu Technical Support to collect the information required for troubleshooting. (*1) |
12 | invalid copy interval. | The specified copy interval is invalid. | |
17 | Not support. | The specified copy function is not supported. | Contact a Fujitsu customer engineer. |
22 | not STX. | The copy source or destination device does not exist. | Check the slice information on the copy source or destination device. Check that the backup management function is not being used on Windows guest OS in Linux KVM environment. The only replication management function can be used on Windows guest OS. |
24 | hardware error requiring CE-CALL. | A SCSI error (CheckCondition) was detected. | After checking the status of the copy session and the connection status of the device, try again. |
25 | SCSI condition met. | A SCSI error (Condition met) was detected. | |
26 | SCSI command busy. | One of the following events has occurred. Check the corresponding event, and take appropriate action. | |
In the case of the cascade copy, any of the following may occur:
The above cascade copy indicates the following:
| Ensure the following:
For details about cascade copy, check the manual of the ETERNUS Disk storage system in use. | ||
In the case of the restoration after executing the backup or replication by OPC/QuickOPC/SnapOPC/SnapOPC+, the restoration by OPC is not being performed. | In the case of the restoration after executing the backup or replication by OPC/QuickOPC/SnapOPC/SnapOPC+, ensure that the restoration by OPC is being performed. | ||
The specified copy target device is already being used for another copy target. | After specifying a device that is not used for other copies as the copy destination device, re-execute the operation. | ||
For the specified logical volume, a copy operation of another type is already running. | Review the specified logical volume and the specified session. | ||
A session was started during the Snap Data Volume initialization. | After the Snap Data Volume initialization is completed, re-execute the operation. | ||
The maximum number of copy sessions that can run concurrently in the storage device has already been reached. | After waiting until the copy of the device specified by the backup execution status display command ends, re-execute the operation. | ||
BUSY was detected in the SCSI path. | After waiting for about five seconds, re-execute the operation. | ||
The copy that is not managed by AdvancedCopy Manager is done. | Confirm the status of the copy by using ETERNUS Web GUI. After specifying a device that is not used elsewhere, re-execute the copy. | ||
A copy start operation was performed, which specify the volume during a data migration using Online Storage Migration for a copy destination volume. | Review the specified copy destination volume and re-execute the operation. | ||
The number of concurrently operable copy sessions that can be set for the same logical unit or the same partition/slice is exceeded. | Operate so that the number of concurrently operable copy sessions is not exceeded. In the QuickOPC / SnapOPC / SnapOPC+ operation, copy session exists even after copy completion. This may cause the number of concurrently operable copy sessions that can be set for the identical logical unit or identical partition/slice to be exceeded when a new copy is done. | ||
An XCOPY session has already been performed for the specified logical volume. | After confirming that the specified logical volume XCOPY session is complete with Web Console, try again. If the above action fails to eliminate the cause of the error, refer to "Use in Combination with XCOPY (Extended Copy)" in the AdvancedCopy Manager Operation Guide (for Windows). | ||
A copy operation was executed to start a session in the reverse direction for the session in the error suspend state. | Refer to the following sections in the AdvancedCopy Manager Operation Guide to check the hardware status and remove the cause of the error, and re-execute the operation:
If you still have a problem, ask Fujitsu Technical Support to collect the information required for troubleshooting. (*1) | ||
A copy operation of multi-copy was executed in the REC Consistency mode for the same box. | Check whether the multi-copy configuration is supported by the storage device. | ||
Restore OPC was executed for a logical volume of a copy pair where a SnapOPC+ session that was being stopped exists. | Check the status of the SnapOPC+ session and try again. | ||
27 | SCSI command conflict. | A SCSI error (a command conflict) was detected. | After checking the status of the copy session and the connection status of the device, try again. |
28 | SCSI queue full. | A SCSI error (queue full) was detected. | |
29 | unexpected SCSI error. | A SCSI error (abnormal state) was detected. | |
33 | different STX. | The definition information is different from the real device. The reason can fall under either of the following cases:
| Reset the environment configuration for AdvancedCopy Manager.
|
35 | invalid MPHD environment. | An MPHD path name was specified for the logical volume name when MPHD was not installed. | Check whether MPHD is installed. |
36 | memory allocation error. | Dynamic memory allocation failed. | Allocate sufficient memory or a swap area, or terminate any other programs that are being executed. |
37 | invalid option flag. | An internal conflict occurred. | Ask Fujitsu Technical Support to collect the information required for troubleshooting. (*1) |
38 | invalid SynfinityDISK environment. | PRIMECLUSTER GD resource is not supported. | Specify a resource other than PRIMECLUSTER GD. |
39 | out of sequence. | One of the following events has occurred. Check the corresponding event, and take appropriate action. | |
The status does not allow execution of this command. | After checking the processing status, try again. | ||
Invalid state or invalid phase detected for the SCSI access. | After checking the session status, try again. | ||
Using AdvancedCopy Manager Copy Control Module, the volume protection function-set volume was specified for the copy destination and the copy operation was executed. | Check whether the volume protection function is set to the copy destination volume and if it is set, unset volume protection settings or retry the settings to a volume to which the volume protection function is not set. | ||
An initialization was executed for the Snap Data Volume currently being operated by the SnapOPC+ session. | After stopping the SnapOPC/SnapOPC+ session, re-execute the operation. | ||
A volume whose type is different from the existing SnapOPC+ generations was specified for the copy destination volume to start the SnapOPC+ copy. | After reviewing the specified copy destination logical volume or stopping the copy session of the existing generation, re-execute the operation. | ||
In the storage device that does not support copying using a Dedup volume as the copy destination of SnapOPC+, a start operation of the SnapOPC+ copy was executed by specifying the Dedup volume as the copy destination. | After reviewing the specified logical volume, re-execute the operation. | ||
A stop operation was executed for the SnapOPC+ session of the current Restore OPC. | After the Restore OPC is completed, re-execute the operation. | ||
The Concurrent OPC function cannot be used because a session currently processing Concurrent OPC exists. | After checking the status of the session, re-execute the operation. | ||
The copy direction was reversed in a state where the data that is not transferred remains in the REC buffer. | Use the concurrent suspend function or after all the transfers to the copy destination are completed, re-execute the operation. | ||
A timeout occurred because the data that is not transferred remains in the REC buffer. | Re-execute the operation when the I/O load is low in the copy source. | ||
No REC session exists in the remote box. | After stopping the REC session of the relevant box, re-execute the operation. | ||
A bad sector exists in the copy source logical volume. | Refer to the following sections in the AdvancedCopy Manager Operation Guide to check the hardware status and remove the cause of the error, and re-execute the operation:
If you still have a problem, ask Fujitsu Technical Support to collect the information required for troubleshooting. (*1) | ||
The copy source logical volume or the copy destination logical volume is in the RAID close state. | Refer to the ETERNUS Disk storage system manuals to remove the cause of the error, and re-execute the operation. | ||
A stop operation was executed for the session in the Error Suspend state or the Halt state. | Refer to the following sections in the AdvancedCopy Manager Operation Guide to check the hardware status and remove the cause of the error, and re-execute the operation:
| ||
A copy stop operation was executed for a SnapOPC+ session of the snap generation that was not allowed to be deleted. | Check the specified snap generation and try again. If the correct snap generation is being specified, stop all the SnapOPC+ sessions from the oldest snap generation up to the one to be deleted. | ||
48 | invalid OLU. | The specified copy source or destination device is invalid because:
| Check the device that is the copy source or the device partition information of the copy destination, and retry the function. |
For the performed operation, the type of the specified copy source device or the copy destination device cannot be used. | After checking the type of the supported volumes and reviewing the specified copy source device or the copy destination device, re-execute the operation. | ||
A volume whose data is being migrated with Non-disruptive Storage Migration is specified for the copy source or copy destination and starting the copy is performed. | Try again after the data migration with Non-disruptive Storage Migration is completed. | ||
56 | invalid GDHD environment. | A GDHD path name was specified for the logical volume name when GDHD was not installed. | Check whether GDHD is installed. |
57 | invalid BoxID. | The specified remote box identifier is invalid. | Check the connection conditions between boxes, and retry. |
At all the RA ports of the paths between ETERNUS Disk storage systems, the Transfer mode to be used is disabled. | Modify the configuration of the RA ports of the paths between ETERNUS Disk storage systems or specify the Transfer mode that is enabled at any of the RA ports and try again. | ||
58 | invalid role. | The specified remote copy direction is invalid. | Check the connection conditions between boxes, and try again. |
59 | setup is inadequate | One of the following events has occurred. Check the corresponding event, and take appropriate action. | |
The Advanced Copy license is not set. | Register the Advanced Copy license. | ||
The copy table size is not set or insufficient. | Check whether the table size of the ETERNUS Disk storage system is properly set. If an REC operation is used, the resolution of the copy table size should be the same between cabinets. Check whether the resolution of the bitmap is the same between boxes. | ||
The REC buffer size is not set. | Check whether the REC buffer size of the ETERNUS Disk storage system is properly set. | ||
All the networks connecting the devices have been disconnected (when all copy routes are closed). | Check that there are no problems in the copy path of the inter-box copy. | ||
The REC buffer is being recovered. | Check the status of the REC buffer of the ETERNUS Disk storage system. After the REC buffer status becomes "Active", re-execute the operation. | ||
When starting the REC in Consistency mode, the load on the REC buffer caused a data transfer error. | New transfer data cannot be kept because of high loads on the REC buffer and the REC Disk buffer. Check the load status of the REC buffer with the "swsrprecbuffstat" command. If "100%" is displayed in the Rate column, the load state is high. When the copy session status is "halt", refer to "Error (halt) on Remote Copy Processing" in the AdvancedCopy Manager Operation Guide to recover the copy session. | ||
60 | bit map resolution disagree. | The bitmap resolution between boxes is inconsistent. | Check whether the magnification of the Advanced Copy table size matches between the ETERNUS Disk storage system containing a copy source device and the ETERNUS Disk storage system containing a copy destination device. |
61 | communication interrupted. | An error occurred in communication between cases. | Check the connection state between the boxes, and retry processing. |
62 | another partner is not supported. | One of the following events has occurred. Check the corresponding event, and take appropriate action. | |
The version of firmware of one box is not supported. | Check that the ETERNUS Disk storage system firmware version is the same between boxes. If this message is output when the concurrent suspend function is in use, check whether it falls under the conditions listed under "Concurrent Suspend Function" in the AdvancedCopy Manager Operation Guide. | ||
A copy operation was executed while the controller firmware was under maintenance. | After waiting until the controller firmware maintenance is completed, re-execute the operation. | ||
63 | the session mode was not changed. | An attempt to switch the session mode has failed. (However, the original status remains as is.) | Check the connection status between boxes, and retry. |
64 | the session mode crosses. | An attempt to switch the session mode has failed. (Information between boxes is inconsistent.) | |
65 | the operation of SnapOPC was failed. | One of the following has occurred:
| After reviewing the specification for the logical volume, try again.
|
66 | the operation of REC Buffer was failed. | An attempt to either display information or change the settings for the REC transfer buffer has failed. | Check the settings status of the REC transfer buffer, and rerun the command. |
67 | the operation of concurrent suspend was failed. | A concurrent suspend operation has failed. (However, the original status remains as is.) | Check the status of all sessions, and rerun the command. For HP-UX or AIX, check that the copy destination volume is the same size or larger than the copy source volume. |
68 | invalid Snap Data Volume. | A Snap Data volume specification error has been detected.
| Check the partition information for the copy source or copy destination device, and rerun the command. |
69 | not support in GR-API. | The specified volume is not supported. | Check that the size of the specified volume is less than 2 TB. |
70 | disk drive motor off. | The disk drive is in the stopped state due to the Eco-mode. | Rerun the command when the disk drive is being activated. |
79 | Unable to restore the copy session because the Concurrent OPC function is being used. | A restoration copy cannot be performed using the Concurrent OPC function. | Review the target copy session for which the Concurrent OPC function is to be used. |
80 | Unable to start the Concurrent OPC function. | The Concurrent OPC function is unable to start due to one of the following reasons:
| After removing the cause of the error, try again. |
81 | The copy source logical volume contains invalid data. | A bad sectors exist in the copy source logical volume. | Refer to the following sections in the AdvancedCopy Manager Operation Guide to check the hardware status and remove the cause of the error, and re-execute the operation:
|
82 | RAID Migration is currently being performed. | RAID Migration is in progress for the specified volume. | After RAID Migration is complete, try again. |
83 | Unable to start the Concurrent OPC function because of invalid parameter. | The Concurrent OPC function is unable to start due to one of the following reasons:
| After removing the cause of the error, try again. |
84 | The number of specified copy sessions exceeds the maximum. | The number of copy sessions specified with Concurrent Suspend and Concurrent OPC exceeds the maximum. | After deleting the target number of sessions, try again. |
85 | Failed to restore the copy session because the phase of the target session is readying. | The restoration copy failed due to one of the following reasons:
| Check the status of the target session for restoration copy. |
86 | Unable to start the Concurrent OPC function because the phase of the latest SnapOPC+ session is readying. | The Concurrent OPC function is unable to start due to the following reason:
| After checking the SnapOPC+ session status of the previous generation, try again. |
87 | Unable to start the Concurrent OPC function because a restoration copy session exists. | The Concurrent OPC function is unable to start due to the following reason:
| After the restoration copy is complete, try again. |
88 | ERROR The status of the cascade copy session is incorrect. | The status of the specified cascade copy source session is not stopped when Concurrent OPC is performed. | After checking the cascade copy source session status, try again. |
89 | ERROR The copy logical source volumes are made by multiple ETERNUS Disk storage systems. | One of the following events has occurred:
| After checking the target logical volume, try again. |
90 | ERROR The source volumes of cascade copy sessions are made by multiple ETERNUS Disk storage systems. | The cascade copy sources of the specified session are in multiple ETERNUS Disk storage systems when Concurrent OPC is performed. | Use appropriate target logical volumes for the Concurrent OPC or cascade sessions, and try again. |
91 | ERROR The transfer mode of the cascade copy session is incorrect. | The specified cascade session is not REC (Consistency or Synchronous) when Concurrent OPC is performed. | |
92 | ERROR The logical volume is already defined in an Offloaded Data Transfer session. | An ODX session has already been performed for the specified logical volume.
| After confirming that the specified logical volume ODX session is complete with Web Console, try again. If the above action fails to eliminate the cause of the error, refer to "Use in Combination with ODX (Offloaded Data Transfer)" in the AdvancedCopy Manager Operation Guide (for Windows). |
93 | The copy session is used by cascade copy session. | The copy session to be cascade-copied is running on the specified copy destination volume. | The following cases are assumed. Take corrective action that is described below for the corresponding case:
For details about cascade copy, check the manual of the ETERNUS Disk storage system in use. |
96 | A copy operation cannot be performed because the specified volumes are unavailable. | A copy operation cannot be executed because the volume such as the system control volume in the ETERNUS Disk storage system, that cannot be copied, is specified as the copy source or copy destination. | After reviewing the logical volume specified as the copy source or copy destination, re-execute the operation. |
99 | ERROR A transparent failover volume was specified. | A TFOV cannot be specified. | After checking whether the specified volume is correct, try again. |
100 | ERROR A transparent failover volume was specified for the copy operation. | A copy operation cannot be executed because the operation is not supported by the Storage Cluster function. One of the following events has occurred. Check the corresponding event, and take appropriate action. | |
When starting the REC copy, a TFOV has been specified as the copy source or copy destination. | After checking whether the specified volume is correct, try again. If the specified volume is correct, the logical volume of either the Primary Storage copy pair or the Secondary Storage copy pair has been changed. Review the configuration of Storage Cluster. Or after deleting the registration with the "swsrpdelvol" command, re-register with the "swsrpsetvol" command. Refer to "Command References" in the AdvancedCopy Manager Operation Guide for information on the commands. | ||
A TFOV has been specified as the copy source or copy destination. | |||
A copy source or copy destination was specified with a TFOV that was not synchronized between the Primary Storage and the Secondary Storage, and a copy operation other than Stop was executed. Or, a copy source or copy destination was specified with a TFOV that was not synchronized between the Primary Storage and the Secondary Storage, and the -T option was specified when stopping QuickOPC copy. | After synchronizing the TFOV, re-execute the operation. | ||
A TFOV in the ETERNUS Disk storage system with a firmware version that does not support the Storage Cluster Continuous Copy function was specified. | If the firmware version of the ETERNUS Disk storage system that is in use does not support the Storage Cluster Continuous Copy function, after applying a firmware version that supports the Storage Cluster Continuous Copy function, re-execute the operation. | ||
A copy operation that was using the Storage Cluster Continuous Copy function was executed while the bitmap ratio of the copy table sizes for the Primary Storage and the Secondary Storage was in a state that did not match. | When using the Storage Cluster Continuous Copy function, check the bitmap ratio of the copy table sizes for the Primary Storage and the Secondary Storage. If the copy table size varies per storage device, after matching the copy table sizes for both the storage devices, re-execute the operation. | ||
101 | ERROR Copy protection cannot be set for a transparent failover volume. | The copy protection cannot be set for a TFOV. | Specify a volume other than a TFOV, and try again. |
103 | ERROR A cascade copy cannot be performed because a transparent failover volume is included. | The cascade copy that includes a TFOV already has an existing copy session for the specified logical volume. Any of the following situations may be a possibility:
When using the Storage Cluster Continuous Copy function, one of the following causes is a possibility:
| Check the copy session that exists in the specified logical volume, and re-execute the operation after the session has stopped. If one of the following causes is a possibility, forcibly stop the copy by using the command or Web Console, and re-execute the operation:
When dealing with the command, specify the storage device where the TFO status is "Standby" for the -a option of the "accopy fcancel" command to execute the operation. Refer to "Command References" in the AdvancedCopy Manager Operation Guide for Copy Control Module for information on the command. |
104 | When a transparent failover volume is specified, Failover or failback has occurred. | An error occurred because Advanced Copy was executed by using the Storage Cluster Continuous Copy function during a failover or a failback. | Upon completion of the failover or the failback, check the status of Advanced Copy, and re-execute the command. |
105 | The wrong copy pair is specified. | In environments that use the Storage Cluster Continuous Copy function, Advance Copy was executed for an incorrect volume combination. One of the following causes is a possibility:
| Review the TRO group where the replication volumes belong, reconfigure the replication volume information. Refer to "When Changing Configurations/Settings" in "Storage Cluster Continuous Copy Function" in the AdvancedCopy Manager Operation Guide for information on the modification procedure. |
106 | Unsupported operation. | An unsupported operation was executed. | Any of the following operation/specification errors are a likely cause:
Make sure that the executed operation and the operation object are correct. |
65536 | undefined message. | An internal conflict occurred. | Ask Fujitsu Technical Support to collect the information required for troubleshooting. (*1) |
65538 | not support in virtual GR-API. | Execution of an unsupported Advanced Copy function was tried. | Check the supported functions and command format. |
65539 | invalid compatible device. | The device name of the specified SDX object is incorrect. | Specify the correct device name. |
65540 | not found sdx object in dom-U. | The specified SDX object does not exist. | Specify the correct SDX object. |
65543 | not found GDS Volume in dom-0. | The SDX object corresponding to the specified device is not found on the host OS of the communication destination. | Specify the correct SDX object. |
65544 | get ip or port error. | Information could not be obtained from the host information setting file. | Check whether the host information setting file is correctly located in a regulated directory path. |
65545 | client error. | Communication with the host OS has failed. | Check whether information described in the host information setting file is correct. |
65546 | server error. | The Advanced Copy operation failed to execute on the host OS. | For the Advanced Copy execution on the host OS, an error that cannot be continued occurs. |
65547 | server API error and no result. | ||
65548 | internal error. | An internal conflict occurred. | Ask Fujitsu Technical Support to collect the information required for troubleshooting. (*1) |
65550 | GDS command error in dom-U. | The PRIMECLUSTER GD volume information could not be obtained on the guest OS. | Check that the slice name of correct SDX object is specified. |
65551 | GDS command error in dom-0. | The PRIMECLUSTER GD volume information could not be obtained on the host OS. | Check that it is able to execute the "sdxinfo" command on the host OS. |
65552 | memory allocation error in dom-U. | Dynamic memory allocation failed on the guest OS. | Allocate sufficient memory or a swap area, or terminate any other programs that are being executed. |
65553 | memory allocation error in dom-0. | Dynamic memory allocation failed on the host OS. | |
65555 | XDR internal error. | An internal conflict occurred. | Ask Fujitsu Technical Support to collect the information required for troubleshooting. (*1) |
65557 | GDS Volume is not single in dom-0. | The host OS's SDX object corresponding to the specified device of the guest OS is not single configuration. | Allocate the SDX object of single configuration as virtual block device of guest OS. |
65559 | get domain name error. | Information could not be obtained from the guest information setting file. | Check whether the guest information setting file is correctly located in a regulated directory path. |
65561 | virtual GR-API internal error. | An internal conflict occurred. | Ask Fujitsu Technical Support to collect the information required for troubleshooting. (*1) |
65562 | specified physical device is not found. | The device corresponding to the specified device is not found on the host OS. | Specify the correct device. |
65563 | virsh dumpxml command error. | The guest OS domain information could not be obtained on the host OS. | Check whether information described in the host information setting file or the guest information setting file is correct. |
65564 | setupdi function error. | The device information could not be obtained from Windows operating system. | Ask Fujitsu Technical Support to collect the information required for troubleshooting. (*1) |
65565 | registry access error. | Accessing to the registry failed. | |
65566 | specified physical drive is not found. | The specified device is not found on the guest OS. | Specify the correct device. |
65567 | invalid virtual disk name is specified. | The specified device is invalid. | Specify the correct device. |
65568 | get partition info error. | The partition information could not be obtained. | Specify the correct device. |
65569 | udevadm command error. | The virtual disk information could not be obtained on the guest OS. | Specify the correct device. |
65570 | get slot number error. | The PCI information corresponding to a virtual disk could not be obtained. | Specify the correct device. |
65571 | invalid host ACM is requested. | AdvancedCopy Manager on the communication destination host did not accept a request. | Check whether information described in the host information setting file is correct. |
65572 | invalid logical volume name. | The specified device does not exist. | Check whether the specified device exists. |
65573 | invalid PCI information. | There is an inconsistency in disk information of the system. | Reboot the guest OS. |
*1: Refer to "Collecting Troubleshooting Information" in the AdvancedCopy Manager Operation Guide for information on how to collect the information required for troubleshooting.
