Top
ETERNUS SF Express V15.3/ Storage Cruiser V15.3/ AdvancedCopy Manager V15.3 Messages
ETERNUS

A.4 Detail error messages of ETERNUS Disk storage system

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.

Table A.1 Detail error messages of ETERNUS Disk storage system

Error
Code

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 ETERNUS SF 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.
(The number of extents is invalid (STXGetVolmuInfo))

Ask a Fujitsu system engineer to collect the information required for troubleshooting. (*1)

4

invalid source BoxID.

An internal conflict occurred.
(The copy source box identifier was invalid.)

5

invalid destination BoxID.

An internal conflict occurred.
(The copy destination box identifier was invalid.)

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.

11

invalid source extent size.

An internal conflict occurred.
(Not entire volume copy but copy size is 0.)

Ask a Fujitsu system engineer 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.

Check the device connection status and then retry.
If you still have a problem, contact a Fujitsu customer engineer.

25

SCSI condition met.

A SCSI error (Condition met) was detected.

26

SCSI command busy.

One of the following has occurred.

  • In the case of the cascade copy, it is either the following:

    • The combination of copy types is not supported by the storage device.

    • The copied data size at each session of the cascade copy is the different.

    The above cascade copy indicates the following.

    • Add a copy for the copy destination volume which a copy has been set.

    • Add a copy for the copy source volume which a copy has been set.

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

  • The specified OPC/EC copy target device is already being used for another OPC/EC copy target.

  • The maximum number of OPC/EC that can run concurrently in the disk array has already been reached.

  • BUSY was detected in the SCSI path.

  • The copy that is not managed by AdvancedCopy Manager is done.

  • The maximum number of copy sessions that can be set to identical logical unit or identical partition/slice is exceeded.

  • An XCOPY session has already been performed for the specified logical volume.

Take the applicable action as follows:

  • In the case of the cascade copy, ensure the following:

    • The combination of copy types is supported by the storage device.

    • The copied data size at each session of the cascade copy is the same.

  • 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.
    (For example, when performing replication by QuickOPC operation, do it without specifying -T for the command option during restore.)

  • Ensure that the OPC/EC copy source is not used for another copy source.

  • Wait until the OPC/EC of the device specified by the backup execution status display command ends, and then re-execute processing.

  • Wait for about five seconds and then re-execute processing.

  • Confirm the status of the copy by using ETERNUS Web GUI.

  • Operate so that the maximum number of copy sessions is not exceeded.

    In QuickOPC / SnapOPC / SnapOPC+ operation, copy session exists even after copy completion. This may cause the maximum number of copy session that can be set to identical logical unit or identical partition/slice to be exceeded when a new copy is done in backup or restore operation.
    For the maximum number of Advanced Copy sessions, check with the manual for ETERNUS Disk storage system you will use.

  • Try again after confirming that the specified logical volume XCOPY session is complete with the Web Console. If the above action fails to eliminate the cause of the error, refer to "Use in combination with XCOPY (Extended Copy)" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for Windows).

For other cases, contact a Fujitsu customer engineer.

27

SCSI command conflict.

A SCSI error (a command conflict) was detected.

Check the device connection status and then retry.
If you still have a problem, contact a Fujitsu customer engineer.

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.

Copying was directed toward a different device. The definition information is different from the real device. The reason can fall under either of the following cases:

  • The definition information for AdvancedCopy Manager on a certain server was copied to another server.

  • The disk storage system was replaced without deleting the definition information for AdvancedCopy Manager.

Reset the environment configuration for AdvancedCopy Manager.

  • If the backup or replication function of AdvancedCopy Manager is used:

    Refer to the following manual to reset the environment configuration for AdvancedCopy Manager.
    "Changing the device configuration" in the ETERNUS SF AdvancedCopy Manager Operation Guide

  • If AdvancedCopy Manager Copy Control Module is used:

    Delete the registration of the copy group and the ETERNUS Disk storage system in which the error occurred and then re-register the ETERNUS Disk storage system and re-create the copy group.

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.
(The operation specification flag is invalid.)

Ask a Fujitsu system engineer to collect the information required for troubleshooting. (*1)

38

invalid SynfinityDISK environment.

SynfinityDISK resource is not supported.

Specify a resource other than SynfinityDISK.

39

out of sequence.

One of the following has occurred:

  • The status does not allow execution of this command.

  • Invalid state or invalid phase detected for the SCSI access.

  • Replication cancellation was executed to a SnapOPC+ generation other than the oldest generation.

  • Using AdvancedCopy Manager Copy Control Module, the volume protection function-set volume was specified for backup destination and backup was performed.

Take one of the following actions:

  • Check the processing status, and then try again.

  • Check the session status, and then try again.

  • Check the Snap generation number, and then try again.

  • Check whether the volume protection function is set to the backup 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.
    (Refer to "Setting copy volume protection" in the ETERNUS SF Operation Guide for Copy Control Module for information on the volume protection function.)

If you still have a problem, contact a Fujitsu system engineer.

48

invalid OLU.

The specified copy source or destination device is invalid because:

  • The same device is specified for the copy source or copy destination in "Copy all volumes".

  • The specified device cannot be used.

  • Consistency mode was specified for the RAID consolidation volume.

  • A non-existent OLU was specified when the volume status was displayed.

Check the device that is the copy source or the device partition information of the copy destination, and retry the function.
If you still have a problem, collect the information required for troubleshooting and contact a Fujitsu system engineer. (*1)

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.
If you still have a problem, contact a Fujitsu customer engineer.

58

invalid role.

The specified remote copy direction is invalid.

59

setup is inadequate

The copy settings are not sufficient for normal operation. One of the following has occurred:

  • The license has not been set with the AdvancedCopy option.

  • There are not enough device resources (e.g., "table size not set", "table size not enough", "REC buffer size not set").

  • If the table size is short:

    Check whether the table size of the ETERNUS Disk storage system is properly set.

  • If REC operation is used:

    The resolution of copy table size should be the same between cabinets. Check whether the resolution of bitmap is the same between cabinets.

The settings required for provided Advanced Copy functions vary depending on every ETERNUS Disk storage system. Check the manual for the ETERNUS Disk storage system to be used to do settings according to its directions.

In the case other than mentioned above, contact a Fujitsu customer engineer and system engineer.

60

bit map resolution disagree.

The bitmap resolution between boxes is inconsistent.

Contact a Fujitsu customer engineer and system engineer.

61

communication interrupted.

An error occurred in communication between cases.

Check the connection state between the boxes, and retry processing.
If you still have a problem, contact a Fujitsu customer engineer.

62

another partner is not supported.

The version of firmware of one box is not supported.

Contact a Fujitsu customer engineer.

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 then retry.
If you still have a problem, contact a Fujitsu customer engineer and system engineer.

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:

  • It tried to execute SnapOPC to the storage device that does not support SnapOPC.

  • An error has occurred accessing a Snap Data volume.

  • Reverse copy was implemented when there was not a SnapOPC session.

Check whether the target storage device supports SnapOPC. If the target storage device supports SnapOPC, take one of the following actions:

  • Check the partition information for the copy destination disk, and then rerun the command.

  • Check the SnapOPC session status, and then rerun the command.

If you still have a problem, contact a Fujitsu customer engineer and system engineer.

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 then rerun the command.
If you still have a problem, contact a Fujitsu customer engineer and system engineer.

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 then 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.
If you still have a problem, contact a Fujitsu system engineer.

68

invalid Snap Data volume.

A Snap Data volume specification error has been detected.

  • SnapOPC/SnapOPC+ has been specified but the copy destination is not a Snap Data volume.

  • SnapOPC/SnapOPC+ has been specified but the copy source is a Snap Data volume.

  • OPC/QuickOPC or EC/REC was specified but either the copy source or the copy destination is a Snap Data volume.

A volume other than a Snap Data volume was specified for Snap Data volume initialization.

Check the partition information for the copy source or copy destination device, and then rerun the command.
If you still have a problem, contact a Fujitsu customer engineer and system engineer.

69

not support in GR-API.

The specified volume is not supported.

Check that the size of the specified volume is less than 2TB.

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:

  • A session with a protected copy destination volume exists.

  • A volume with invalid data exists.

  • A session with an expired license exists.

  • A session undergoing Concurrent OPC exists.

Resolve the error and try again.

81

The copy source logical volume contains invalid data.

The copy source logical volume contains invalid data.

Check the data contents of the relevant copy source logical volume.

82

RAID Migration is currently being performed.

RAID Migration with capacity expansion is in progress for the specified volume.

Try again after RAID Migration is complete.

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:

  • There are deleted sessions.

  • The same session is specified multiple times.

Resolve the error and 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.

Delete the target number of sessions and 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:

  • The target session phase is in a session definition complete/copy not performed state (Readying).

  • The target session is a SnapOPC+ session and the latest generation phase is in a session definition complete/copy not performed state (Readying).

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:

  • When adding a new SnapOPC+ generation, the session phase of the previous generation is in a session definition complete/copy not performed state (Readying).

Check the SnapOPC+ session status of the previous generation, and 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:

  • When performing a QuickOPC differential copy, a restoration copy is in operation for the target session.

Try again after the restoration copy is complete.

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.

Check the cascade copy source session status and try again.
If the above action fails to eliminate the cause of the error, refer to "Notes on combining cascade copy and Concurrent OPC in operation" in "Notes on snapshot high-speed backup" in the ETERNUS SF AdvancedCopy Manager Operation Guide.

89

ERROR The copy logical source volumes are made by multiple ETERNUS Disk storage systems.

When the concurrent suspend is performed for REC and the path information for copy destination ETERNUS Disk storage system is registered, the copy sources of the specified session are in multiple ETERNUS Disk storage systems.

Check the target logical volume and 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.
If the above action fails to eliminate the cause of the error, refer to "Notes on combining cascade copy and Concurrent OPC in operation" in "Notes on snapshot high-speed backup" in the ETERNUS SF AdvancedCopy Manager Operation Guide.

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.

Try again after confirming that the specified logical volume ODX session is complete with the Web Console. If the above action fails to eliminate the cause of the error, refer to "Use in combination with ODX (Offloaded Data Transfer)" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for Windows).

65536

undefined message.

An internal conflict occurred.

Ask a Fujitsu system engineer to collect the information required for troubleshooting. (*1)

65538

not support in virtual GR-API.

It tried to execute the unsupported Advanced Copy function.

The function which is not supported with this function has operated. Check the supported range.

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.
Or, check whether information described in the host information setting file or the guest information setting file is correct.

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.

It failed to execute the Advanced Copy operation on the host OS.

For the Advanced Copy execution on the host OS, an error that cannot be continued occurs. Ask a Fujitsu system engineer to collect the information required for troubleshooting. (*1)

65547

server API error and no result.

65548

internal error.

An internal conflict occurred.

Ask a Fujitsu system engineer to collect the information required for troubleshooting. (*1)

65550

GDS command error in dom-U.

The GDS volume information could not be obtained on the guest OS.

Check that the slice name of correct SDX object is specified.
Or, check that it is able to execute the sdxinfo command on the guest OS.

65551

GDS command error in dom-0.

The GDS 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 a Fujitsu system engineer 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 a Fujitsu system engineer 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.
Or, check whether information described in the host information setting file or the guest information setting file is correct.

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.
Or, check that it is able to execute the virsh dumpxml info command on the host OS.

65564

setupdi function error.

The device information could not be obtained from Windows operating system.

Ask a Fujitsu system engineer to collect the information required for troubleshooting. (*1)

65565

registry access error.

It failed to access the registry.

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.
Or, check whether the specified device is a device that can specify on Linux guest.

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.
Or, check that it is able to execute the udevadm info command on the guest OS.

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 maintenance information" in the ETERNUS SF AdvancedCopy Manager Operation Guide for information on how to collect the information required for troubleshooting.