When you migrate volumes or cancel migration through CCI, you might identify the cause of the error by referring to the log displayed on the CCI window or in the CCI operation log file.
The CCI operation log file is stored in: /HORCM/log*/curlog/horcmlog_HOST/horcm.log
Where:
- * is the instance number.
- HOST is the host name.
The following figure shows an example of error log message in the CCI window.
The following table show the cause of errors and the solutions for SSB2 error codes when SSB1 codes are 2E31, B9A0, B9A2, B9AE, B9AF.
|
Error Code (SSB2) |
Cause of Errors |
Solutions |
|---|---|---|
|
0C96 |
The data reduction shared volume (DRS-VOL) specified for the migration source volume cannot be used. |
The volume cannot be migrated. Delete and re-create the DRS-VOL. |
|
0C97 |
The data reduction shared volume (DRS-VOL) specified for the migration target volume cannot be used. |
The volume cannot be migrated. Delete and re-create the DRS-VOL. |
|
2008 |
The setting of the T10 PI attribute does not match between the migration source volume and the migration target volume. |
The volume cannot be migrated. Check the configuration definition file. |
|
2027 |
The cache mode does not match between the migration source volume and the migration target volume. |
The volume cannot be migrated. Check the configuration definition file. |
|
202B |
Multiple GAD pairs have been created by using the migration source volume. |
Delete one or more GAD pairs for the specified volume, and then try the operation again. |
|
2039 |
The migration source volume is the Quorum disk. |
The volume cannot be migrated. Check the configuration definition file. |
|
203A |
The migration target volume is the Quorum disk. |
The volume cannot be migrated. Check the configuration definition file. |
|
203E |
In the migration source volume, the serial number and the model of the virtual storage machine or the virtual LDEV ID has been changed. |
After the configuration change has finished, try again. |
|
203F |
In the migration target volume, the serial number and the model of the virtual storage machine or the virtual LDEV ID has been changed. |
After the configuration change has finished, try again. |
|
204A |
The current firmware version does not support the capacity of the migration source volume. |
Specify a volume whose capacity is supported. |
|
204B |
The current firmware version does not support the capacity of the migration target volume. |
Specify a volume whose capacity is supported. |
|
204C |
The migration source volume corresponds to either of the following causes:
|
Of the following actions, perform the one that corresponds to the actual cause:
|
|
204D |
The migration target volume corresponds to either of the following causes:
|
The volume cannot be migrated. Check the configuration definition file. |
|
2050 |
The migration target volume is being used with Volume Retention Manager. |
Release the volume from Volume Retention Manager, and then migrate the volume. |
|
2051 |
The migration target volume is being used with Data Retention Utility. |
Release the volume from Data Retention Utility, and then migrate the volume. |
|
2055 |
The migration target volume is being used with Universal Replicator. |
Release the volume from Universal Replicator, and then migrate the volume. |
|
2056 |
The migration source volume is being used with Universal Replicator. |
Release the volume from Universal Replicator, and then migrate the volume. |
|
2058 |
The migration target volume and the migration source volume belong to the same parity group. |
The volume cannot be migrated. Check the configuration definition file. |
|
205C |
The migration target volume is being used with Universal Replicator. |
Release the volume from Universal Replicator, and then migrate the volume. |
|
206B |
The migration source volume is the Deduplication System Data Volume (fingerprint). |
The volume cannot be migrated. Check the configuration definition file. |
|
206C |
The migration target volume is the Deduplication System Data Volume (fingerprint). |
The volume cannot be migrated. Check the configuration definition file. |
|
206E |
The source volume is being used as a GAD volume and as a ShadowImage primary volume of a pair that is undergoing a Quick Restore. |
After the Quick Restore is complete, migrate the volume. |
|
2070 |
The source volume is being used as a GAD volume and that pair is undergoing an initial copy or a resync. |
Place the GAD pair in the suspended status, and then migrate the volume. |
|
2074 |
The migration source volume is being used as a GAD volume, and the volume attribute (VOL_ATTR displayed by the raidcom get ldev command) does not match between the GAD secondary volume of the pair and the specified migration target volume. |
Specify the same volume attribute (VOL_ATTR displayed by the raidcom get ldev command) to the migration target volume as the one of the the secondary volume of the GAD pair. |
|
2075 |
The migration source volume is the secondary volume of the Thin Image pair. |
Release the Thin Image pair, and then migrate the volume. |
|
2076 |
The migration target volume is primary or secondary volume of the Thin Image pair. |
Release the Thin Image pair, and then migrate the volume. |
|
2089 |
The migration source volume is undergoing quick formatting. |
Wait for the quick formatting to complete and then migrate the volume. |
|
208A |
The migration target volume is undergoing quick formatting. |
Wait for the quick formatting to complete and then migrate the volume. |
|
2090 |
The migration target volume is a DP-VOL which is not associated with a pool. |
Associate a DP-VOL with a pool, and then migrate the volume. |
|
2091 |
The migration source volume is a DP-VOL which is not associated with a pool. |
Associate a DP-VOL with a pool, and then migrate the volume. |
|
2093 |
The migration source volume is primary volume of the Thin Image pair. |
The volume cannot be migrated. Check the configuration definition file. |
|
2095 |
The migration target volume and the migration source volume are DP-VOLs that are associated with the same pool. |
The volume cannot be migrated. Check the configuration definition file. |
|
2096 |
The migration source volume is used by TrueCopy or Universal Replicator. The migration target volume is a DP-VOL. |
Release the pair containing the migration source volume, and then migrate the volume. |
|
20A5 |
The migration source volume is a DP-VOL whose capacity is increasing. |
Wait until the capacity increase is completed. Then, you must specify a target volume which has the same capacity as the volume whose capacity is increased and migrate the volume. |
|
20A6 |
The migration target volume is a DP-VOL whose capacity is increasing. |
Wait until the capacity increase is completed. Then, you must specify a source volume which has the same capacity as the volume whose capacity is increased and migrate the volume. |
|
20AC |
The command ended abnormally because you specified for the migration source volume a volume that can be used only for a pool volume. This error occurs when you specify either of the following volumes for the migration source volume:
|
The volume cannot be migrated. Check the configuration definition file. |
|
20AD |
The migration source volume is a DP-VOL. The volume is processing the Unmap command issued when the system option mode 905 is on. |
Please retry the pair creation after a while. If the problem persists despite retrying, turn off the system option mode 905, and then retry the pair creation. |
|
20AE |
The migration target volume is a DP-VOL. The volume is processing the Unmap command issued when the system option mode 905 is on. |
Please retry the pair creation after a while. If the problem persists despite retrying, turn off the system option mode 905, and then retry the pair creation. |
|
20AF |
The command ended abnormally because you specified for the migration target volume a volume that can be used only for a pool volume. This error occurs when you specify either of the following volumes for the migration target volume:
|
The volume cannot be migrated. Check the configuration definition file. |
|
20BA |
No LU path or no namespace of an NVM subsystem (to which an NVM subsystem port was added in the NVMe-oF connection environment) is set for the migration source volume. |
Set an LU path to the volume or a namespace of an NVM subsystem (to which an NVM subsystem port was added in the NVMe-oF connection environment) for the volume, and then migrate the volume. |
|
20BB |
No LU path or no namespace of an NVM subsystem (to which an NVM subsystem port was added in the NVMe-oF connection environment) is set for the migration target volume. |
Set an LU path to the volume or a namespace of an NVM subsystem (to which an NVM subsystem port was added in the NVMe-oF connection environment) for the volume, and then migrate the volume. |
|
20C5 |
The power supply is switched off. |
Perform the operation again after the power supply turning on. |
|
20D3 |
The migration source volume is a DP-VOL whose DP pool is being initialized. |
Perform the operation again after the initialization of the DP pool has finished. |
|
20D4 |
The migration target volume is a DP-VOL whose DP pool is being initialized. |
Perform the operation again after the initialization of the DP pool has finished. |
|
20F2 |
If the serial number of the virtual storage machine is set to the primary and secondary volume, the serial number set in the primary volume matches the serial number set in the secondary volume. However, the serial numbers of the physical storage systems and the virtual storage machines do not match. |
The volume cannot be migrated. Check the configuration definition file. |
| 20FA | The migration target volume is an external volume mapped for nondisruptive migration. | The volume cannot be migrated. Check the configuration definition file. |
| 20FB | Volume Migration is not installed on the storage system. | Install Volume Migration, and then migrate the volume. |
|
2301 |
Volume Migration is not installed on the storage system. |
Install Volume Migration, and then migrate the volume. |
|
2306 |
The LBA size does not match between the migration target volume and the migration source volume. |
The volume cannot be migrated. Check the configuration definition file. |
|
2309 |
The maximum number of pairs which can be set in the storage system is exceeded. |
Reduce the number of pairs set in the storage system, and then migrate the volume. |
|
2316 |
Soft Fence is set on the migration source volume. |
Release the setting of Soft Fence, and then migrate the volume. |
|
2317 |
Soft Fence is set on the migration target volume. |
Release the setting of Soft Fence, and then migrate the volume. |
|
231C |
The combination of the pool IDs and CU numbers associated with the specified migration source and target volumes is a mixture of even and odd numbers. |
Specify the CU numbers and pool IDs that are all even numbers or odd numbers. |
|
231D |
Volumes with and without Extent Space Efficient (ESE) attribute are mixed in the specified migration source and target volumes. |
Use volumes with ESE attribute only, or volumes without ESE attribute only. |
|
2322 |
The migration source volume is set as the leaf volume of ShadowImage |
Release the ShadowImage pair, and then migrate the volume. |
|
2328 |
The migration target volume is set as the secondary volume of ShadowImage. |
Release the ShadowImage pair, and then migrate the volume. |
|
232B |
The volume that meets both of the following conditions is specified to the migration source volume or the migration target volume.
|
Perform eather of the following actions:
|
|
232F |
The migration source volume is already specified as the target volume of Volume Migration. |
Release the volume from Volume Migration, and then migrate the volume. |
|
2331 |
The number of slots does not match between the migration target volume and the migration source volume. |
The volume cannot be migrated. Check the configuration definition file. |
|
2332 |
You cannot add pair settings any more to the volume specified as the migration source. |
Reduce the number of pair settings of the specified volume, and then migrate the volume. |
|
2333 |
The volume specified by the migration cancellation is not a migration source volume |
None. The specified volume is not a source volume. |
|
2337 |
The migration source volume is a leaf volume of ShadowImage. |
Release the ShadowImage pair, and then migrate the volume. |
|
233B |
The migration target volume is a primary volume of ShadowImage. |
Release the ShadowImage pair, and then migrate the volume. |
|
233C |
The migration target volume is a secondary volume of ShadowImage. |
Release the ShadowImage pair, and then migrate the volume. |
|
2342 |
The migration target volume is already specified as the target volume of Volume Migration. |
Release the volume from Volume Migration, and then migrate the volume. |
|
2343 |
The migration target volume is set as the primary volume of ShadowImage. |
Release the ShadowImage pair, and then migrate the volume. |
|
2344 |
The volume specified by the migration cancellation is not a migration target volume |
None. The specified volume is not a target volume. |
|
2346 |
The migration target volume is a primary volume of TrueCopy. |
Release the TrueCopy pair, and then migrate the volume. |
|
2347 |
The migration target volume is a secondary volume of TrueCopy. |
Release the TrueCopy pair, and then migrate the volume. |
|
234B |
The migration target volume is already specified as the source volume of Volume Migration. |
Release the volume from Volume Migration, and then migrate the volume. |
|
234E |
The migration source volume is the deduplication system data volume (data store). |
The volume cannot be migrated. Check the configuration definition file. |
|
234F |
The migration target volume is the deduplication system data volume (data store). |
The volume cannot be migrated. Check the configuration definition file. |
|
2350 |
The migration source volume is not paired with the migration target volume. |
Deleting the pair or canceling migration is not available. Check the configuration definition file. |
|
2351 |
The migration source volume and the migration target volume are set to the same volume. |
The following operations are not available:
Check the configuration definition file. |
|
2355 |
The setting of Virtual LUN is different between the migration target volume and the migration source volume. |
The volume cannot be migrated. Check the configuration definition file. |
|
2368 |
The volume specified as the migration source volume is being used as the primary volume of the TrueCopy pair. The pair is in the COPY status. |
Change the TrueCopy pair status from COPY to PAIR or PSUS, or delete the TrueCopy pair, and then migrate the volume. |
|
2369 |
The volume specified as the migration source volume is being used as the secondary volume of the TrueCopy pair. The pair is in the COPY status. |
Change the TrueCopy pair status from COPY to PAIR or PSUS, or delete the TrueCopy pair, and then migrate the volume. |
|
236A |
The migration source volume is the primary volume of a ShadowImage pair which is in the COPY(SP) or PSUS(SP) status. |
Migrate the volume after the ShadowImage pair is changed to PSUS status. |
|
236B |
The migration source volume is the secondary volume of a ShadowImage pair which is in the COPY(SP) or PSUS(SP) status. |
Migrate the volume after the ShadowImage pair is changed to PSUS status. |
|
2370 |
The migration source volume is not installed. |
The volume cannot be migrated. Check the configuration definition file. |
|
2371 |
The migration source volume is blocked. Alternatively, the pool to which the migration source volume belongs contains a pool volume that is not in the normal status. |
|
|
2372 |
The migration source volume is being formatted or being shredded. |
Migrate the volume after formatting or shredding is completed. |
|
2373 |
The migration source volume is a command device. |
The volume cannot be migrated. Check the configuration definition file. |
|
237C |
The migration source volume is an external volume specified as a primary volume of TrueCopy. |
Release the TrueCopy pair, and then migrate the volume. |
|
2380 |
The migration target volume is not installed. |
The volume cannot be migrated. Check the configuration definition file. |
|
2381 |
The migration target volume is blocked. Alternatively, the pool to which the migration target volume belongs contains a pool volume that is not in the normal status. |
|
|
2382 |
The migration target volume is being formatted or being shredded. |
Migrate the volume after formatting or shredding is completed. |
|
2383 |
The migration target volume is a command device. |
The volume cannot be migrated. Check the configuration definition file. |
|
2392 |
The migration source volume is the DP-VOL of the capacity saving status which is in the Deleting Volume, Deleting Volume (nn%) or Failed. |
The volume cannot be migrated. Change the capacity saving status so that the volume can be migrated, or review the configuration definition file. |
|
2393 |
The migration target volume is the DP-VOL of the capacity saving status which is in the Deleting Volume, Deleting Volume (nn%) or Failed. |
The volume cannot be migrated. Change the capacity saving status so that the volume can be migrated, or review the configuration definition file. |
|
B911 |
The pair operation command was rejected because the specified volume is not implemented. |
Make sure that the specified volume is implemented. |
|
B912 |
The pair operation command was rejected because the specified secondary volume is not implemented. |
Make sure that the specified secondary volume is implemented. |
|
B913 |
The pair operation command was rejected because the mirror ID is invalid. |
Specify the mirror ID from 0 to 2. |