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. |
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. |
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. |
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. |
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. |
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 |
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) |
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. |
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 |
KARS16065-E |
Operation did not succeed. [Cause] Conditions for operating the Data reduction function are not met. |
KARS16066-E |
Operation did not succeed. [Cause] The Data reduction function cannot be set for S-VOLs and P/S-VOLs. [Solution] Check the parameters. |
KARS16067-E |
Operation did not succeed. [Cause] The savingMode cannot be set for S-VOL and P/S-VOL. [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. |
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. |
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. |
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) |
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. |
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. |
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. |
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. |
KARS16137-E |
The volume could not be created. [Cause] The specified storage controller does not have sufficient free capacity. |
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) |
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. |
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 |
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 |
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. |
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 |
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. |
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 |
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 |
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 |