Message ID |
Message |
|---|---|
KARS16000-E |
Operation did not succeed. [Cause] Required parameters are not specified. [Solution] Check the parameters. |
KARS16001-E |
Processing did not succeed. [Cause] Memory is insufficient. [Solution] If you are a system administrator, see the event logs, confirm that no job is running, and then retry the operation. If the error persists, collect the logs, and then contact customer support. If you are a VPS administrator, wait for a while, and then retry the operation. If the error persists, report the message contents to the system administrator. |
KARS16002-E |
Processing did not succeed. [Cause] Access is concentrated on configuration information, or configuration information operations are not working properly. [Solution] If you are a system administrator, see the event logs, confirm that no job is running, and then retry the operation. If the error persists, collect the logs, and then contact customer support. If you are a VPS administrator, wait for a while, and then retry the operation. If the same error occurs, report the message contents to the system administrator. |
KARS16003-E |
Processing did not succeed. [Cause] The operations that cannot be executed at the same time are executing. [Solution] Wait a while, and then retry the operation. |
KARS16004-E |
Operation did not succeed. [Cause] The specified parameters is greater than the maximum allowable value. [Solution] Check the parameters. |
KARS16005-E |
Operation did not succeed. [Cause] The specified parameters is less than the minimum required value. [Solution] Check the parameters. |
KARS16006-E |
Operation did not succeed. [Cause] The specified parameters of characters exceeds the maximum allowable number of characters. [Solution] Check the parameters. |
KARS16007-E |
Operation did not succeed. [Cause] The specified parameters of characters is less than the minimum number of required characters. [Solution] Check the parameters. |
KARS16008-E |
Processing did not succeed. [Cause] An unexpected error occurred. [Solution] If you are a system administrator, collect the logs, and then contact customer support. If you are a VPS administrator, report the message contents to the system administrator. |
KARS16009-E |
Processing did not succeed. [Cause] An unexpected error occurred. [Solution] If you are a system administrator, collect the logs, and then contact customer support. If you are a VPS administrator, report the message contents to the system administrator. |
KARS16010-E |
The volume could not be created. [Cause] The maximum logical capacity of volumes that can be created on the storage controller has been reached. [Solution] If you are a system administrator, see the VSP One SDS Block System Administrator Operation Guide, and review the logical capacity of the volume to be created. Or, delete unnecessary volumes or add storage nodes to secure the necessary capacity. If you are a VPS administrator, report the message contents to the system administrator. |
KARS16011-E |
Operation did not succeed. [Cause] An error occurred in the internode network communication. [Solution] If you are a system administrator, verify the internode network configuration, and then retry the operation. If you are a VPS administrator, report the message contents to the system administrator. |
KARS16012-E |
Processing did not succeed. [Cause] The specified resource cannot be found. [Solution] Verify that the specification of the resource is correct. When you operate resources in a virtual private storage, verify that the ID of the operation-target VPS is correct. |
KARS16013-E |
Operation did not succeed. [Cause] The specified component cannot be created. [Solution] Delete unnecessary components, and then retry the operation. |
KARS16014-E |
Operation did not succeed. [Cause] Snapshot volume cannot be deleted. [Solution] To delete a P-VOL, delete all S-VOLs created by the target P-VOL first, and then delete the P-VOL. To delete an S-VOL, deleted the S-VOL. To delete a P/S-VOL, delete all S-VOLs created by the target P/S-VOL first, and then delete the target P/S-VOL. |
KARS16015-E |
Operation did not succeed. [Cause] The fullAllocated settings cannot be updated for volumes for snapshots. [Solution] Check the parameters. |
KARS16016-E |
The volume could not be created. [Cause] The capacity of the storage pool is insufficient. [Solution] If you are a system administrator, see the VSP One SDS Block System Administrator Operation Guide, and then expand the storage pool. If you are a VPS administrator, report the message contents to the system administrator. |
KARS16017-I |
Adding capacity to the storage controller succeeded. (Storage controller ID = xxx) [Event Name] Storage pool expansion success [Category] StoragePool |
KARS16018-W |
Adding capacity to the storage controller did not succeed. Now retrying. (Storage controller ID = xxx) [Event Name] Storage pool expansion warning [Category] StoragePool [Solution] See the job list, and if there are any jobs running, wait until the jobs have completed. If there are blocked storage nodes, recover them. See the rebuild status, and if rebuildStatus is not Stopped, wait for the Rebuild operation to complete. Then, wait for a while. If the storage controller described in this event log is not displayed in the event log (either KARS16017-I, KARS16020-I, KARS16022-I, or KARS16081-I) indicating that storage pool capacity expansion was successful, collect the logs, and then contact customer support. |
KARS16019-E |
Adding capacity to the storage controller did not succeed. (Storage controller ID = xxx) [Event Name] Storage pool expansion error [Category] StoragePool [Solution] Collect the logs, and then contact customer support. |
KARS16020-I |
Capacity allocation processing (initial expansion) of the storage controller is complete. (Storage controller ID = xxx) [Event Name] Initial expansion of the storage controller complete [Category] StoragePool |
KARS16021-I |
Capacity allocation processing of the storage controller is started. (Storage controller ID = xxx) [Event Name] Capacity allocation processing of the storage controller start [Category] StoragePool |
KARS16022-I |
Capacity allocation processing of the storage controller is complete. (Storage controller ID = xxx) [Event Name] Capacity allocation processing of the storage controller complete [Category] StoragePool |
KARS16023-W |
Free capacity of the storage controller is decreasing. (Storage controller ID = xxx) [Event Name] Storage controller capacity management detect capacity exhaustion [Category] StoragePool [Solution] Delete unnecessary snapshots or volumes, or expand the capacity of the storage pool. When deleting snapshots, delete all the snapshots created in the snapshot tree. |
KARS16024-W |
Free capacity of the storage pool is decreasing. (Storage pool ID = xxx) [Event Name] Storage pool capacity management detect free capacity is decreasing [Category] StoragePool [Solution] Delete unnecessary snapshots or volumes, or expand the capacity of the storage pool. When deleting snapshots, delete all the snapshots created in the snapshot tree. |
KARS16025-E |
The capacity of the storage pool is exhausted. (Storage pool ID = xxx) [Event Name] Storage pool capacity management detect capacity exhaustion [Category] StoragePool [Solution] Delete unnecessary snapshots or volumes, or expand the capacity of the storage pool. When deleting snapshots, delete all the snapshots created in the snapshot tree. |
KARS16026-E |
The storage controller in which the volume is to be located could not be changed. [Cause] The specified storage controller does not have sufficient free capacity. [Solution] Delete unnecessary snapshots or volumes in the specified storage controller, or expand the capacity of the storage pool. When deleting snapshots, delete all the snapshots created in the snapshot tree. |
KARS16027-E |
Volume migration was canceled. [Cause] Volume migration was canceled because a failure or volume status change was detected. [Solution] See the event log, and if an error event log is displayed, correct the failure. Then, verify that the specified volume is placed in the migration-destination storage controller. If the volume has not been migrated, retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS16028-I |
The Capacity balance in the storage pool is started. [Event Name] Storage pool capacity balance start [Category] StoragePool |
KARS16029-I |
The Capacity balance in the storage pool is complete. [Event Name] Storage pool capacity balance complete [Category] StoragePool |
KARS16030-E |
Volume operation could not be executed. [Cause] The request to the storage controller did not succeed. [Solution] If you are a system administrator, . If you are a VPS administrator, report the message contents to the system administrator. |
KARS16031-E |
Volume migration was canceled. [Cause] Volume migration was canceled to allow for a high-priority operation or by a volume migration cancellation request. [Solution] After the high-priority operation or volume migration cancellation processing is completed, verify that the specified volume is placed in the migration-destination storage controller. If the volume has not been migrated, retry the operation. |
KARS16032-E |
The capacity of storage controller could not be expanded. [Cause] The target storage node status is not normal. [Solution] See the event logs, confirm that no job is running, and then retry the operation. |
KARS16033-E |
The volume could not be deleted. [Cause] The specified volume cannot be deleted because it contains created snapshots. [Solution] Delete all the snapshots created in the snapshot tree of the specified volume, and then retry the operation. |
KARS16034-E |
The volume could not be deleted. [Cause] This operation cannot delete volumes for snapshots. [Solution] Perform the operation for deleting volumes for snapshots. |
KARS16035-E |
The volume could not be created. [Cause] No more volumes can be created because the number of volumes has reached the maximum. [Solution] If you are a system administrator, delete unnecessary snapshots or volumes. If you are a VPS administrator, report the message contents to the system administrator. |
KARS16036-E |
The volume could not be deleted. [Cause] A volume whose type is MigrationDestination cannot be deleted. [Solution] Review the target volume. |
KARS16037-E |
The volume setting could not be updated. [Cause] The settings for a volume whose type is MigrationDestination cannot be updated. [Solution] Review the target volume. |
KARS16038-E |
The volume could not be expanded. [Cause] The volume cannot be expanded if the volume status is other than Normal or ExpansionFailed, or volume type is other than Normal. [Solution] Expand a volume whose status is Normal or ExpansionFailed and volume type is Normal. |
KARS16039-E |
The volume could not be deleted. [Cause] A volume whose volume type is ExternalMigrationOrigin cannot be deleted. [Solution] |
KARS16040-E |
The volume could not be updated. [Cause] A volume whose volume type is ExternalMigrationOrigin cannot be updated. [Solution] Review the target volume. |
KARS16041-E |
The volume could not be relocated. [Cause] A volume whose volume type is ExternalMigrationOrigin cannot be relocated. [Solution] Check the parameters. |
KARS16043-E |
The volume could not be expanded. [Cause] A capacity to be added cannot be specified when expanding a volume whose status is ExpansionFailed. [Solution] Retry the operation without specifying a capacity to be added. |
KARS16044-E |
The volume setting could not be updated. [Cause] The settings for a volume whose status is neither Normal nor UpdateFailed cannot be updated. [Solution] |
KARS16045-E |
Volume operation could not be executed. [Cause] Free capacity of the storage controller has become depleted. (Storage controller ID = xxx) [Solution] If you are a system administrator, delete unnecessary snapshots or volumes, or expand the capacity of the storage pool. When deleting snapshots, delete all the snapshots created in the snapshot tree. If you are a VPS administrator, report the message contents to the system administrator. |
KARS16046-I |
Capacity was added to the storage pool but the logical capacity was not expanded. (Storage pool ID = xxx) [Event Name] Logical capacity is not changed [Category] StoragePool [Solution] To expand the logical capacity, add drives to the storage node that has insufficient capacity and expand the storage pool according to the VSP One SDS Block System Administrator Operation Guide. |
KARS16047-E |
The volume could not be expanded. [Cause] The maximum logical capacity of volumes that can be created on the storage controller has been reached. (Storage controller ID = xxx) [Solution] If you are a system administrator, see the VSP One SDS Block System Administrator Operation Guide, and review the logical capacity of the volume to be expanded. Or, delete unnecessary volumes on the storage controller to secure the necessary capacity. If you are a VPS administrator, report the message contents to the system administrator. |
KARS16048-E |
The volume could not be created. [Cause] There is no storage controller that can create a volume. [Solution] If you are a system administrator, verify the configuration and status of the storage controller. If you are a VPS administrator, report the message contents to the system administrator. |
KARS16049-E |
The volume could not be created. [Cause] The maximum volume that can be created has been reached. [Solution] If you are a system administrator, delete unnecessary snapshots or volumes. If you are a VPS administrator, report the message contents to the system administrator. |
KARS16050-E |
The volume could not be created. [Cause] The maximum number of volumes that can be created in the storage cluster or specified storage controller has been reached. [Solution] Delete unnecessary snapshots or volumes in the specified storage controller, or specify another storage controller. If the maximum number of volumes that can be created in the storage cluster has been reached, delete unnecessary snapshots or volumes in another storage controller. |
KARS16051-E |
The volume could not be created. [Cause] The maximum logical capacity of volumes that can be created on the specified storage controller has been reached. [Solution] See the VSP One SDS Block System Administrator Operation Guide to review the logical capacity of the volume to be created. Or, delete unnecessary volumes in the specified storage controller to secure the necessary capacity or specify another storage controller having sufficient logical capacity to be allocated. |
KARS16052-E |
The volume could not be created. [Cause] The specified storage controller does not exist. [Solution] Check the parameters. |
KARS16053-E |
The volume could not be created. [Cause] The specified storage controller redundancy is invalid. [Solution] Collect the logs, and then contact customer support. |
KARS16054-E |
The volume could not be created. [Cause] Removal of the storage node on which the specified storage controller is operating has not been completed. [Solution] After storage node removal is completed, retry the operation. Or, specify a storage controller running on a storage node that is not being removed. |
KARS16055-E |
Processing did not succeed. [Cause] The specified xxx cannot be found. (ID = xxx) [Solution] Verify that the specification of the resource is correct. |
KARS16056-E |
Operation did not succeed. [Cause] Neither Nickname nor Name can be changed with other parameters at the same time. [Solution] Check the parameters. |
KARS16057-E |
Operation did not succeed. [Cause] The specified xxx cannot be created because the creation limit has been reached. [Solution] Delete unnecessary resources, and then retry the operation. |
KARS16058-E |
Operation did not succeed. [Cause] Required parameters are not specified. (Parameter name = xxx) [Solution] Check the parameters. |
KARS16059-E |
Operation did not succeed. [Cause] The specified parameter is greater than the maximum allowable value. (Parameter name = xxx) [Solution] Check the parameters. |
KARS16060-E |
Operation did not succeed. [Cause] The specified parameter is less than the minimum required value. (Parameter name = xxx) [Solution] Check the parameters. |
KARS16061-E |
Operation did not succeed. [Cause] The specified parameter of characters exceeds the maximum allowable number of characters. (Parameter name = xxx) [Solution] Check the parameters. |
KARS16062-E |
Operation did not succeed. [Cause] The specified parameter of characters is less than the minimum number of required characters. (Parameter name = xxx) [Solution] Check the parameters. |
KARS16063-E |
Operation did not succeed. [Cause] The specified parameter is invalid. (Parameter name = xxx) [Solution] Check the parameters. |
KARS16064-E |
The specified storage node cannot be removed because some storage pools have not been expanded (storage pool capacity is insufficient). (Job ID = xxx) [Event Name] Storage node removal pre-check (Insufficient storage pool capacity) [Category] StorageNode [Solution] Expand the storage pools that have not been expanded according to the VSP One SDS Block System Administrator Operation Guide. |
KARS16065-E |
Operation did not succeed. [Cause] Conditions for operating the Data reduction function are not met. [Solution] If you are a system administrator, see the VSP One SDS Block System Administrator Operation Guide to confirm the conditions for using the Data reduction function. If you are a VPS administrator, report the message contents to the system administrator. |
KARS16066-E |
Operation did not succeed. [Cause] The Data reduction function cannot be set for an S-VOL and P/S-VOL of snapshots. [Solution] Check the parameters. |
KARS16067-E |
Operation did not succeed. [Cause] savingMode cannot be set for an S-VOL and P/S-VOL of snapshots. [Solution] Check the parameters. |
KARS16068-I |
Shrinkage of the storage controller capacity is started. (Storage controller ID = xxx) [Event Name] Start of storage controller capacity shrinkage [Category] StoragePool |
KARS16069-I |
Shrinkage of the storage controller capacity is completed. (Storage controller ID = xxx) [Event Name] Completion of storage controller capacity shrinkage [Category] StoragePool |
KARS16070-I |
Total progress of shrinkage of capacity in the storage controller. (Progress = xxx %) [Event Name] Progress of storage controller capacity shrinkage [Category] StoragePool |
KARS16071-I |
Shrinkage of the storage controller capacity is stopped. (Storage controller ID = xxx) [Event Name] Stop of storage controller capacity shrinkage [Category] StoragePool |
KARS16072-E |
Volume deletion was stopped. [Cause] Volume deletion was aborted to allow for a high-priority operation. After the high-priority operation is completed, the deletion process will continue in the background. [Solution] See the volume information and wait until the deletion process is completed. When the volume deletion process is completed, the target volume disappears from the volume information. If the volume status changes from Deleting to DeletionFailed, . |
KARS16073-E |
Updating the volume settings was stopped. [Cause] Volume setting was aborted to allow for a high-priority operation. After the high-priority operation is completed, the setting process will continue in the background. [Solution] See the volume information and wait until the setting update process is completed. When the volume setting update process is completed, the volume status changes from Updating to Normal. If the volume status changes from Updating to UpdateFailed, . |
KARS16074-I |
Shrinkage of the storage controller capacity is stopped. [Cause] Operations that cannot be executed at the same time are executing. [Solution] See the event logs, confirm that no job is running, and then retry the operation. |
KARS16075-E |
Expansion of the storage controller capacity did not succeed. [Cause] Shrinkage of the storage controller capacity cannot be stopped in time. [Solution] Retry the operation. |
KARS16076-I |
Shrinkage of the storage controller capacity is not necessary. [Cause] The free space necessary for drive data rebuilding is sufficient. |
KARS16077-I |
Shrinkage of the storage controller capacity succeeded. (Storage controller ID = xxx) [Event Name] Success of storage controller capacity shrinkage [Category] StoragePool |
KARS16078-W |
Shrinkage of the storage controller capacity did not succeed. (Storage controller ID = xxx) [Event Name] Failure of storage controller capacity shrinkage (warning) [Category] StoragePool [Solution] See the event logs and confirm that no job is running. If the storage controller described in this event log is not displayed in the event log for successful shrinkage of the pool capacity (KARS16077-I), collect the logs, and then contact customer support. |
KARS16079-E |
Shrinkage of the storage controller capacity did not succeed. (Storage controller ID = xxx) [Event Name] Failure of storage controller capacity shrinkage (error) [Category] StoragePool [Solution] Collect the logs, and then contact customer support. |
KARS16081-I |
Capacity allocation processing (full expansion) of the storage controller is complete. (Storage controller ID = xxx) [Event Name] Full expansion of the storage controller complete [Category] StoragePool |
KARS16083-E |
Volume operation could not be executed. [Cause] Shrinkage of the storage controller capacity is executing. [Solution] See the event logs, confirm that shrinkage of the storage controller capacity is not running, and then retry the operation. |
KARS16084-E |
Operation did not succeed. [Cause] Full allocation settings and Data reduction function settings cannot be enabled at the same time. [Solution] Check the parameters. |
KARS16085-E |
The volume could not be created. [Cause] A volume with full allocation settings enabled could not be created because there is insufficient allocatable logical capacity. [Solution] See the VSP One SDS Block System Administrator Operation Guide, and review the logical capacity of the volume to be created. Or, delete unnecessary volumes or expand the capacity of the storage pool to secure the necessary capacity. |
KARS16086-E |
Operation did not succeed. [Cause] The Data reduction function cannot be set for volumes with the Full Allocation setting enabled. [Solution] Check the parameters. |
KARS16087-E |
Operation did not succeed. [Cause] The Full Allocation setting cannot be set for volumes with data reduction enabled. [Solution] Check the parameters. |
KARS16088-E |
The volume could not be expanded. [Cause] The volume with full allocation settings enabled could not be expanded because there is insufficient allocatable logical capacity on the storage controller. (Storage controller ID = xxx) [Solution] See the VSP One SDS Block System Administrator Operation Guide, and review the logical capacity of the volume to be expanded. Or, delete unnecessary volumes or expand the capacity of the storage pool to secure the necessary capacity. |
KARS16092-E |
The volume could not be created. [Cause] A volume for which the full allocation setting is enabled could not be created because capacity could not be added to the storage controller. [Solution] Verify the event logs. If a warning event log (KARS16018-W) is displayed, wait for a while, verify that an event log (either KARS16017-I, KARS16020-I, KARS16022-I, or KARS16081-I) is also displayed, and then retry the operation. If a failure event log (KARS16019-E) is displayed, collect the logs, and then contact customer support. If an event log (KARS05001-E) is displayed, verify that an event log (KARS07001-I) is also displayed, and then retry the operation. If other event logs are displayed, correct the failures, and then retry the operation. |
KARS16093-E |
The volume could not be expanded. [Cause] A volume for which the full allocation setting is enabled could not be expanded because capacity could not be added to the storage controller. [Solution] Verify the event logs. If a warning event log (KARS16018-W) is displayed, wait for a while, verify that an event log (either KARS16017-I, KARS16020-I, KARS16022-I, or KARS16081-I) is also displayed, and then retry the operation. If a failure event log (KARS16019-E) is displayed, collect the logs, and then contact customer support. If an event log (KARS05001-E) is displayed, verify that an event log (KARS07001-I) is also displayed, and then retry the operation. If other event logs are displayed, correct the failures, and then retry the operation. |
KARS16094-E |
The volume could not be created. [Cause] Since the area reserved for the Rebuild must be used, a volume with full allocation settings cannot be created. [Solution] Make settings so that a volume is created using the area reserved for the Rebuild. |
KARS16095-E |
The volume could not be expanded. [Cause] Since the area reserved for the Rebuild must be used, a volume with full allocation settings cannot be expanded. [Solution] Make settings so that a volume is expanded using the area reserved for the Rebuild. |
KARS16096-I |
The volume could be recreated. (Volume ID = xxx) [Event Name] Volume recreation successful [Category] Volume |
KARS16097-E |
The volume could not be recreated. (Volume ID = xxx) [Event Name] Volume recreation unsuccessful [Category] Volume [Solution] Collect the logs, and then contact customer support. |
KARS16099-E |
The volume could not be expanded. [Cause] The volume in full allocation setting cannot be expanded because capacity information is being updated. [Solution] Wait for about 5 minutes, and then retry the operation. |
KARS16101-E |
The volume could not be created. [Cause] If the parameter savingSetting is Disabled, savingMode cannot be set. [Solution] Check the parameters. |
KARS16102-E |
The volume could not be created. [Cause] If the parameter savingSetting is omitted, savingMode cannot be set. [Solution] Check the parameters. |
KARS16103-E |
The volume setting could not be updated. [Cause] If savingSetting of volume is Disabled, savingMode cannot be set. [Solution] Check the parameters. |
KARS16107-E |
Operation did not succeed. [Cause] The specified Name is already in use. [Solution] Check the parameters. |
KARS16108-E |
Operation did not succeed. [Cause] Nickname or Name is not specified. [Solution] Check the parameters. |
KARS16109-E |
Capacity management of the storage controller cannot be performed during Storage node removal. (Storage controller ID = xxx) [Solution] Stop the Storage node removal. |
KARS16110-E |
Capacity management of the storage controller cannot be performed during software update. (Storage controller ID = xxx) [Solution] Stop the software update. |
KARS16111-E |
The volume could not be deleted. [Cause] Volumes with the ExpansionFailed status cannot be deleted. [Solution] |
KARS16112-E |
Operation did not succeed. [Cause] A drive whose status is other than Offline has been specified. [Solution] Verify that the status of the specified drive is Offline. |
KARS16113-E |
Operation did not succeed. [Cause] Duplicated drive IDs have been specified. (Drive ID = xxx) [Solution] Check the parameters. |
KARS16114-W |
Volume creation was aborted. [Cause] Volume creation was aborted to allow for a high-priority operation. [Solution] If you are a system administrator, see the volume list after the high-priority operation completes, and then retry creation of the volumes that were not created. If you are a VPS administrator, report the message contents to the system administrator. |
KARS16115-W |
Expansion of the storage pool was aborted. [Cause] Expansion of the storage pool was aborted to allow for a high-priority operation. [Solution] After the high-priority operation is completed, see the drive list, and then retry expansion of the storage pool for drives that were not added to the storage pool. |
KARS16116-I |
Capacity addition of the storage controller was aborted to allow for a high-priority operation. After the high-priority operation is completed, capacity addition of the storage controller will be resumed in the background. (Storage controller ID = xxx) [Event Name] Capacity addition of the storage controller aborted [Category] StoragePool |
KARS16117-E |
The storage controller in which the volume is to be located could not be changed. [Cause] Volumes cannot be relocated because sufficient capacity is not allocated to the specified storage controller. [Solution] See the VSP One SDS Block System Administrator Operation Guide to expand the storage pool capacity. |
KARS16118-E |
The storage controller in which the volume is to be located could not be changed. [Cause] Volumes cannot be relocated because doing so would exceed the capacity available for the Full Allocation setting. [Solution] Delete unnecessary volumes in the relocation destination or expand the storage pool capacity according to the manual to secure the required capacity. |
KARS16119-E |
Storage controller capacity usage has reached the depletion threshold of the storage controller. (Storage controller ID = xxx) [Event Name] Storage controller capacity usage reached the depletion threshold of the storage controller [Category] StoragePool [Solution] Delete unnecessary snapshots or volumes, or expand the capacity of the storage pool. When deleting snapshots, delete all the snapshots created in the snapshot tree. |
KARS16120-W |
Capacity allocation processing of the storage controller did not succeed. (Storage controller ID = xxx) [Event Name] Capacity allocation processing of the storage controller failed [Category] StoragePool [Solution] If an event log indicating another error is output, take action referring to the event log. If the error persists, collect the logs, and then contact customer support. |
KARS16121-C |
The storage controller in which the volume is to be located could not be changed. [Cause] The status of the storage controller is invalid. [Solution] Collect the logs, and then contact customer support. |
KARS16122-E |
The storage controller in which the volume is to be located could not be changed. [Cause] Removal of the storage node on which the storage controller is operating has not been completed. [Solution] After removal of the storage node is completed, retry the operation. |
KARS16123-E |
The storage controller in which the volume is to be located could not be changed. [Cause] Volume relocation is being performed for the specified volume. [Solution] Wait until volume relocation is completed, and then retry the operation. |
KARS16124-E |
The storage controller in which the volume is to be located could not be changed. [Cause] The volume type is not Normal. [Solution] Review the volume to be moved. |
KARS16125-E |
The storage controller in which the volume is to be located could not be changed. [Cause] The volume status is not Normal or the volume data reduction status is Failed. [Solution] Review the volume to be moved. |
KARS16126-E |
The storage controller in which the volume is to be located could not be changed. [Cause] The operation cannot be performed due to software update in progress. [Solution] Wait until the software update is completed, and then retry the operation. |
KARS16127-E |
The storage controller in which the volume is to be located could not be changed. [Cause] The operation cannot be performed due to Rebuild operation in progress. [Solution] Wait until the Rebuild operation is completed, and then retry the operation. |
KARS16128-E |
The storage controller in which the volume is to be located could not be changed. [Cause] The specified volume does not exist. [Solution] Review the parameters. |
KARS16129-E |
The storage controller in which the volume is to be located could not be changed. [Cause] The specified storage controller does not exist. [Solution] Review the parameters. |
KARS16130-E |
The storage controller in which the volume is to be located could not be changed. [Cause] The volume is already located in the specified storage controller. [Solution] Review the parameters. |
KARS16131-E |
The storage controller in which the volume is to be located could not be changed. [Cause] The maximum number of volumes that can be created in the specified storage controller has been reached. [Solution] Delete unnecessary snapshots or volumes in the specified storage controller. |
KARS16132-E |
The storage controller in which the volume is to be located could not be changed. [Cause] The maximum logical capacity that can be allocated to the specified storage controller has been exceeded. [Solution] Delete unnecessary volumes in the specified storage controller. |
KARS16133-E |
The volume could not be deleted. [Cause] Volumes with the MetaDataConsistencyError status cannot be deleted. [Solution] If you are a system administrator, . If you are a VPS administrator, report the message contents to the system administrator. |
KARS16134-E |
Operation did not succeed. [Cause] The data reduction status is such that volume operation cannot be performed. [Solution] If you are a system administrator, collect the logs, and then contact customer support. If you are a VPS administrator, report the message contents to the system administrator. |
KARS16135-E |
Capacity allocation processing of the storage controller cannot be performed due to insufficient capacity. (Storage controller ID = xxx) [Event Name] Capacity allocation processing of the storage controller failed [Category] StoragePool [Solution] If the drive is blocked, replace it with one that has a capacity equal to or more than that of the blocked drive. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS16136-E |
The volume could not be created. [Cause] Volumes cannot be created because sufficient capacity is not allocated to the specified storage controller. [Solution] Specify another storage controller with sufficient free capacity, or expand the storage pool according to the VSP One SDS Block System Administrator Operation Guide. |
KARS16137-E |
The volume could not be created. [Cause] The specified storage controller does not have sufficient free capacity. [Solution] Delete unnecessary snapshots or volumes in the specified storage controller, or expand the storage pool according to the VSP One SDS Block System Administrator Operation Guide. When deleting snapshots, delete all the snapshots created in the snapshot tree. Or, specify another storage controller having sufficient free space. |
KARS16138-E |
Operation did not succeed. [Cause] The combination of the specified parameters is invalid. [Solution] Review the parameter combination and re-execute. |
KARS16139-E |
Operation did not succeed. [Cause] The specified storage pool cannot be updated because the storage pool redundancy is reduced. (Storage pool ID = xxx) [Solution] |
KARS16140-E |
Operation did not succeed. [Cause] The specified value for NumberOfTolerableDriveFailures is too large. (Maximum value that can be allowed = xxx) [Solution] Check the parameters. |
KARS16141-W |
The rebuild capacity policy was changed, but sufficient capacity is not secured. (Storage pool ID = xxx) [Cause] The capacity of the storage pool is insufficient. [Solution] To secure rebuild capacity, add drives to the storage nodes with insufficient capacity by following the VSP One SDS Block System Administrator Operation Guide. |
KARS16142-I |
The number of times Rebuild can be performed for a storage pool was reduced. (Storage pool ID = xxx) [Event Name] The number of times Rebuild can be performed for a storage pool was reduced [Category] StoragePool [Solution] To secure rebuild capacity, add drives to the storage nodes with insufficient capacity by following the VSP One SDS Block System Administrator Operation Guide. |
KARS16143-W |
The number of times Rebuild can be performed for a storage pool has become 0. (Storage pool ID = xxx) [Event Name] Rebuild can no longer be performed for a storage pool [Category] StoragePool [Solution] To secure rebuild capacity, add drives to the storage nodes with insufficient capacity by following the VSP One SDS Block System Administrator Operation Guide. |
KARS16144-E |
The volume could not be created. [Cause] A volume with full allocation settings enabled could not be created because there is insufficient allocatable logical capacity in the specified storage controller. [Solution] See the VSP One SDS Block System Administrator Operation Guide to review the logical capacity of the volume to be created. Or, delete unnecessary volumes in the specified storage controller or expand the storage pool to secure the necessary capacity, or specify another storage controller that has sufficient free space. |
KARS16145-E |
The volume could not be created. [Cause] The specified storage controller is not in a status in which volumes can be created. [Solution] Review the configuration or status of the specified storage controller. If there is no problem, delete unnecessary snapshots or volumes in the specified storage controller, or expand the capacity of the storage pool. When deleting snapshots, delete all the snapshots created in the snapshot tree. |
KARS16146-E |
The volume could not be created. [Cause] No more volumes can be created because the number of volumes that can be created in the specified storage controller has reached the maximum. [Solution] Delete unnecessary snapshots or volumes in the specified storage controller. |
KARS16147-W |
The rebuild capacity policy was changed, but sufficient capacity is not secured. (Storage pool ID = xxx) [Event Name] Insufficient rebuild capacity [Category] StoragePool [Solution] To secure rebuild capacity, add drives to the storage nodes with insufficient capacity by following the VSP One SDS Block System Administrator Operation Guide. |
KARS16148-E |
Operation did not succeed. [Cause] The maximum number of volumes that can be created on the virtual private storage has been exceeded. [Solution] See the virtual private storage and delete unnecessary snapshots or volumes until you have enough space for the number of volumes you want to create. |
KARS16149-E |
Operation did not succeed. [Cause] The specified volume capacity exceeds the maximum single volume capacity that can be created on the virtual private storage. [Solution] See the virtual private storage and change the volume capacity specification so that the specified capacity becomes equal to or less than the maximum single volume capacity. |
KARS16150-E |
Operation did not succeed. [Cause] The maximum total volume capacity that can be created on the virtual private storage has been exceeded. [Solution] See the virtual private storage and delete unnecessary snapshots or volumes until you have enough space for the capacity of volumes you want to create. |
KARS16151-E |
Operation did not succeed. [Cause] The range of the QoS setting that can be set for volumes on the virtual private storage has been exceeded. [Solution] See the virtual private storage to change the QoS setting for volumes so that the setting becomes within the available range. |
KARS16152-E |
Operation did not succeed. [Cause] Some parameters exceed the range of values that can be set for the virtual private storage. [Solution] See the VSP One SDS Block System Administrator Operation Guide to review the parameters. |
KARS16153-E |
Operation did not succeed. [Cause] The specified virtual private storage name is already in use. [Solution] Review the parameters. |
KARS16154-E |
Operation did not succeed. [Cause] The specified limit is lower than the number of resources and capacity that have been created on the virtual private storage. [Solution] See the virtual private storage or the list of information about volumes in the virtual private storage to verify the created resources that exceed the specified upper limit. Then, delete resources so that the number of resources is below the specified upper limit, and retry the operation. |
KARS16155-W |
Some of the totals of the resource limit set for the virtual private storage exceed the system limit. [Event Name] Virtual private storage setting value warning [Category] VirtualPrivateStorage [Solution] If the setting exceeding the system limit is not intentional, see the VSP One SDS Block System Administrator Operation Guide to confirm the system limit. Then, review the resource limit set for each virtual private storage. |
KARS16156-E |
Operation did not succeed. [Cause] The virtual private storage to be deleted contains created resources. [Solution] See the virtual private storage to be deleted to verify the created resources. Then, delete all the resources and retry the operation. |
KARS16157-E |
Operation did not succeed. [Cause] Values cannot be specified for the parameters when editing settings of the volumes with UpdateFailed status. [Solution] Retry the operation without values specified. |
KARS16158-W |
Logical capacity was not expanded for the storage node to be added. [Event Name] No logical capacity expansion for storage node addition required [Category] StoragePool [Solution] See the event logs, and if an error event log is displayed, correct the failure. Then, see the VSP One SDS Block System Administrator Operation Guide to confirm the capacity required for the added storage node, and then add drives if the capacity is insufficient. |
KARS16159-W |
Logical capacity expansion could not be verified due to configuration information reference failure. [Event Name] Verification of logical capacity expansion for storage node addition unsuccessful [Category] StoragePool [Solution] See the event logs, and if an error event log is displayed, correct the failure. Then, see the storage controller information to verify whether a storage controller whose allocatableCapacity 0 exists. If such a storage controller exists, see the VSP One SDS Block System Administrator Operation Guide to confirm the capacity required for the storage node, and then add drives for any insufficient capacity. |
KARS16160-E |
A volume could not be created. [Cause] The specified fault domain does not exist. [Solution] Review the parameters. |
KARS16161-E |
A volume could not be created. [Cause] A volume cannot be created in the specified fault domain. [Solution] |
KARS16162-E |
A volume could not be created. [Cause] The maximum number of volumes that can be created in the storage cluster or specified fault domain has been reached. [Solution] Delete unnecessary snapshots or volumes in the specified fault domain, or specify another fault domain. If the maximum number of volumes that can be created in the storage cluster has been reached, delete unnecessary snapshots or volumes from another fault domain. |
KARS16163-E |
A volume could not be created. [Cause] The maximum logical capacity of volumes that can be created in the specified fault domain has been reached. [Solution] See the VSP One SDS Block System Administrator Operation Guide to review the logical capacity of the volume to be created. Or, delete unnecessary volumes in the specified fault domain to secure the necessary capacity or specify another fault domain that has sufficient logical capacity for allocation. |
KARS16164-E |
A volume could not be created. [Cause] The specified fault domain does not have sufficient free capacity. [Solution] Delete unnecessary snapshots or volumes in the specified fault domain, or see the VSP One SDS Block System Administrator Operation Guide to expand the storage pool. When deleting snapshots, delete all the snapshots created in the snapshot tree. Or, specify another fault domain that has free capacity. |
KARS16165-E |
Operation did not succeed. [Cause] No more journals can be created because the maximum number of journals that can be created in the storage cluster has been reached. [Solution] If you are a system administrator, delete unnecessary journals created in the storage controller in which you want to create a journal, and then retry the operation. If you are a VPS administrator, report the message contents to a system administrator. |
KARS16166-E |
Operation did not succeed. [Cause] Journal operation is not possible because the specified volume type is not normal. [Solution] Verify whether the correct volume is specified. If the correct volume is specified, specify a volume whose volume type is normal as a target of journal operation. If the specified volume is incorrect, specify a correct volume. |
KARS16167-E |
Operation did not succeed. [Cause] The journal number exceeds the specifiable range. [Solution] Specify a correct journal number, and then retry the operation. |
KARS16168-E |
Operation did not succeed. [Cause] Journal operation is not possible because the pair status of Universal Replicator is other than unpaired(SMPL) and suspending(PSUS/SSUS) status. [Solution] Change the pair status of Universal Replicator to suspending(PSUS/SSUS) status, or delete the pair to change the pair status to unpaired(SMPL) status, and then retry the operation. |
KARS16169-E |
Operation did not succeed. [Cause] An unexpected error occurred. [Solution] If you are a system administrator, collect the logs, and then contact customer support. If you are a VPS administrator, report the message contents to a system administrator. |
KARS16170-E |
Operation did not succeed. [Cause] The specified volume has already been used as a journal volume. [Solution] Verify whether the correct volume is specified. If the correct volume is specified, specify a volume whose volume type is normal as a target of journal operation. If the specified volume is incorrect, specify a correct volume. |
KARS16171-E |
Operation did not succeed. [Cause] Journal volumes cannot be deleted from a journal because no reserve journal volume is set. [Solution] Verify whether the correct journal is specified. If the correct journal is specified, add a reserve journal volume to the journal, and then retry the operation. If the specified journal is incorrect, specify a correct journal. |
KARS16172-E |
Operation did not succeed. [Cause] The specified journal cannot be deleted because Universal Replicator has a data volume. [Solution] Delete all the pairs that the specified journal has, wait for a while, and then retry the operation. |
KARS16173-E |
Operation did not succeed. [Cause] No more volumes can be added to the journal because the number of volumes that can be registered to the journal has reached the maximum. [Solution] Delete unnecessary journal volumes from the journal by performing journal shrink. Then, reperform journal expansion. |
KARS16174-E |
Operation did not succeed. [Cause] To specify the muNumber parameter, all the parameters for a mirror unit cannot be omitted. If you omit the muNumber parameter, no parameters for a mirror unit can be specified. [Solution] To specify the muNumber parameter, specify the parameters for a mirror unit. If you omit the muNumber parameter, no parameters for a mirror unit can be specified. |
KARS16175-E |
Operation did not succeed. [Cause] A volume of a storage controller other than the storage controller of a journal was specified. [Solution] Specify a volume that belongs to the same storage controller as the storage controller of a journal volume, and then retry the operation. |
KARS16176-E |
Operation did not succeed. [Cause] An unexpected error occurred. [Solution] Wait for a while, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS16177-E |
Operation did not succeed. [Cause] Journal operation is not possible because the specified volume has a connected volume path. (Volume ID = xxx) [Solution] Verify whether the correct volume is specified. If the correct volume is specified, specify a volume whose volume path is disconnected and that no longer has a connected volume path as a target of journal operation. If the specified volume is incorrect, specify a correct volume. |
KARS16178-E |
Operation did not succeed. [Cause] A journal cannot be created because a journal with the specified journal number already exists. [Solution] If you are a system administrator, specify a journal number that is not duplicated, and then retry the operation. If you are a VPS administrator, report the message contents to a system administrator. |
KARS16179-E |
Operation did not succeed. [Cause] A journal that has the specified ID could not be found. [Solution] Verify the specified journal ID, and then retry the operation. |
KARS16180-E |
Operation did not succeed. [Cause] The capacity of the specified volume is less than the minimum capacity that can be used as a journal volume. [Solution] See the VSP One SDS Block Universal Replicator Guide to verify the minimum volume capacity that can be used as a journal volume. Specify a volume that has a capacity equal to or more than the minimum capacity, and then retry the operation. |
KARS16181-E |
Operation did not succeed. [Cause] Operation might be unsuccessful due to storage node failure. [Solution] If you are a system administrator and an event log indicating another problem is issued, correct the problem. Then, take action to handle the unsuccessful operation according to the VSP One SDS Block Universal Replicator Guide. If the problem persists, collect the logs, and then contact customer support. If you are a VPS administrator, report the message contents to a system administrator. |
KARS16182-E |
Operation did not succeed. [Cause] This operation cannot be performed because the journal is in unsuccessful operation status. [Solution] Verify the journal status, and then take appropriate action depending on the status following the VSP One SDS Block Universal Replicator Guide. |
KARS16183-E |
Operation did not succeed. [Cause] An error occurred in the internode network communication. [Solution] Verify the internode network configuration, and then retry the operation. |
KARS16184-E |
Operation did not succeed. [Cause] The storage controller temporarily stops accepting requests. [Solution] Retry the operation after a while. |
KARS16185-E |
Operation did not succeed. [Cause] A temporary remote path failure occurred. [Solution] Recover the remote path failure according to the VSP One SDS Block Universal Replicator Guide, and then retry the operation. |
KARS16186-E |
Operation did not succeed. [Cause] This operation cannot be performed for a data volume of Universal Replicator. [Solution] Verify whether the correct volume is specified. If the correct volume is specified, delete the pair of the data volume of Universal Replicator, and then retry the operation. If the specified volume is incorrect, specify a correct volume. |
KARS16187-E |
Operation did not succeed. [Cause] A volume being used as a journal volume cannot be deleted. [Solution] Verify whether the correct volume is specified. If the specified volume is correct, delete the journal in which the specified volume is registered, and then retry the operation. If the specified volume is incorrect, specify a correct volume. |
KARS16188-E |
Operation did not succeed. [Cause] This operation cannot be performed for a data volume of Universal Replicator. [Solution] Verify whether the correct volume is specified. If the correct volume is specified, delete the pair of the data volume of Universal Replicator, and then retry the operation. If the specified volume is incorrect, specify a correct volume. |
KARS16189-E |
Operation did not succeed. [Cause] Volume relocation is being performed. [Solution] Wait until volume relocation is completed, and then retry the operation. |
KARS16190-E |
A volume could not be created. [Cause] A necessary parameter is not specified. [Solution] Specify a fault domain or storage controller in which a volume is to be created. |
KARS16192-E |
Operation did not succeed. [Cause] The status of the specified volume is not normal. [Solution] Verify whether the correct volume is specified. If the specified volume is incorrect, specify a volume whose volume status is normal as a target of journal operation. If the specified volume is incorrect, specify a correct volume. |
KARS16193-E |
Operation did not succeed. [Cause] Journal operation is not possible because a volume with data reduction enabled is specified. (Volume ID = xxx) [Solution] Verify whether the correct volume is specified. If the correct volume is specified, specify a volume with data reduction disabled as a target of journal operation. If the specified volume is incorrect, specify a correct volume. |
KARS16194-E |
Operation did not succeed. [Cause] Journal operation is not possible because a data volume of Universal Replicator is specified. [Solution] Verify whether the correct volume is specified. If the specified volume is correct, specify a non-Universal Replicator data volume whose UniversalReplicatorAttribute is not a P-VOL, P/S-VOL, or S-VOL for the journal operation. If the specified volume is incorrect, specify a correct volume. |
KARS16195-E |
Operation did not succeed. [Cause] A volume whose isRemoteCopySupported is False and that was created before Universal Replicator was supported is specified. [Solution] Verify whether the correct volume is specified. If the correct volume is specified, specify a volume whose isRemoteCopySupported is True as a target of journal operation. If the specified volume is incorrect, specify a correct volume. |
KARS16196-E |
Operation did not succeed. [Cause] Journal volumes cannot be deleted from a journal because the pair status of the data volume of Universal Replicator (that belongs to the specified journal) is other than unpaired(SMPL) and suspending(PSUS/SSUS) status. [Solution] Verify whether the correct journal is specified. If the correct volume is specified, change the pair status of Universal Replicator that belongs to the specified journal to suspending(PSUS/SSUS) status, or delete the pair to change the pair status to unpaired(SMPL) status, and then retry the operation. If the specified journal is incorrect, specify a correct journal. |
KARS16197-E |
Operation did not succeed. [Cause] The specified volume does not exist in the journal. [Solution] Verify that the specified journal to be deleted is correct. |
KARS16198-E |
Operation did not succeed. [Cause] An internal error occurred. [Solution] Wait for a while, and then retry the operation. If the same error occurs after retry, collect the logs, and then contact customer support. |
KARS16199-E |
Operation did not succeed. [Cause] The storage controller to which the journal volume belongs differs from the storage controller to which the reserve journal volume belongs. [Solution] Specify a volume that belongs to the same storage controller as the storage controller of a journal volume, and then retry the operation. |
KARS16200-E |
Operation did not succeed. [Cause] Journal operation is not possible because the specified volume is being used as a snapshot volume. [Solution] Verify whether the correct volume is specified. If the correct volume is specified, specify a volume whose volume type is normal as a target of journal operation. If the specified volume is incorrect, specify a correct volume. |
KARS16201-E |
Operation did not succeed. [Cause] A parameter for inflow control cannot be changed because the specified journal is not a master journal. [Solution] If the specified journal is correct, journal volume inflow control of a restore journal cannot be set. If the specified journal is incorrect, specify a master journal. |
KARS16202-E |
Processing did not succeed. [Cause] A failure occurred on the cluster master node (primary). [Solution] See the event log, and if an error event log is displayed, correct the failure. Then, retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS16203-E |
Operation did not succeed. [Cause] The operation is not permitted. [Solution] See the VSP One SDS Block System Administrator Operation Guide to review the operation. |
KARS16205-E |
Operation did not succeed. [Cause] The rebuild capacity policy cannot be changed to "Variable" with the base license type currently applied to the storage cluster. [Solution] See the VSP One SDS Block System Administrator Operation Guide to review the parameters. |
KARS16206-E |
Operation did not succeed. [Cause] The operation cannot be performed because the conditions for performing the operation are not met, or the network environment has a problem. [Solution] See all the event logs, and if an event log (KARS11114-E or KARS11115-E) is output, take the required action according to the event log. |
KARS16208-E |
Operation did not succeed. [Cause] A journal cannot be created because the journal volume and reserve journal volume are the same. [Solution] Specify a different volume respectively for the journal volume and reserve journal volume, and then retry the operation. |
KARS16209-W |
Volume configuration information could not be updated. Retrying. (Storage node ID = xxx) [Event Name] Volume configuration information update failure [Category] Volume [Solution] If event log KARS16211-I is output after this event log, no action is required. If any job is in progress, verify that event log KARS16211-I is output after the job completes. Also, as an exception, if the event log is not output after the storage cluster is restarted or the storage node is blocked or recovered, you do not need to take action. If the event log is not output when the preceding exception applies, collect the logs, and then contact customer support. |
KARS16210-E |
Volume configuration information could not be updated. (Storage node ID = xxx) [Event Name] Volume configuration information update failure [Category] Volume [Solution] Collect the logs, and then contact customer support. |
KARS16211-I |
Volume configuration information could be updated. (Storage node ID = xxx) [Event Name] Volume configuration information update successful [Category] Volume |
KARS16212-W |
Journal configuration information could not be updated. Retrying. (Storage node ID = xxx) [Event Name] Journal configuration information update failure [Category] Journal [Solution] If event log KARS16214-I is output after this event log, no action is required. If any job is in progress, verify that event log KARS16214-I is output after the job completes. Also, as an exception, if the event log is not output after the storage cluster is restarted or the storage node is blocked or recovered, you do not need to take action. If the event log is not output when the preceding exception applies, collect the logs, and then contact customer support. |
KARS16213-E |
Journal configuration information could not be updated. (Storage node ID = xxx) [Event Name] Journal configuration information update failure [Category] Journal [Solution] Collect the logs, and then contact customer support. |
KARS16214-I |
Journal configuration information could be updated. (Storage node ID = xxx) [Event Name] Journal configuration information update successful [Category] Journal |
KARS16215-E |
The operation did not succeed. [Cause] Parameters for data overflow watch time or inflow control cannot be changed for a master journal when the pair status is other than unpaired and suspending status. These parameters cannot be changed for a restore journal irrespective of the pair status. The parameter for the cache mode cannot be changed when the pair status is other than unpaired and suspending status. [Solution] Change the journal status to an appropriate status or select an appropriate journal, and then retry the operation. If the journal status is UpdateFailed, delete the pair, and then retry the operation. |
KARS16216-E |
The operation did not succeed. [Cause] The parameter for copy pace cannot be changed for a master journal when the pair status is other than unpaired and suspending status. The parameter for copy pace cannot be changed for a restore journal irrespective of the pair status. [Solution] Change the journal status to an appropriate status or select an appropriate journal, and then retry the operation. If the journal status is UpdateFailed, delete the pair, and then retry the operation. |
KARS16217-E |
The operation did not succeed. [Cause] A journal cannot be created because the write back mode with cache protection is not enabled. [Solution] If the system state is such that the write back mode with cache protection can be enabled, enable the mode, and then retry the operation. |
KARS16219-E |
Operation did not succeed. [Cause] No more journals can be created because the maximum number of journals that can be created in the storage controller has been reached. (Storage controller ID = xxx) [Solution] If you are a system administrator, delete unnecessary journals created in the storage controller in which you want to create a journal, and then retry the operation. Or, retry the operation in another storage controller. If you are a VPS administrator, report the message contents to a system administrator. |
KARS16230-E |
Operation did not succeed. [Cause] The operation is not supported. [Solution] Update the storage software to the supported version, and then retry the operation. If software update is incomplete, complete the software update, and then retry the operation. |