Message ID |
Message |
---|---|
KARS06001-W |
Available snapshot management resources become insufficient. (Storage controller ID = xxx) [Event Name] Snapshot depletion warning [Category] SnapShot [Solution] Delete the unnecessary snapshot volume or volume created on the storage controller shown in the detailed information. When deleting snapshots, delete all the snapshots created in the snapshot tree. Otherwise, you might not be able to create or use snapshots. |
KARS06002-E |
Snapshot management resources run out. (Storage controller ID = xxx) [Event Name] Snapshot depletion error [Category] SnapShot [Solution] Delete the unnecessary snapshot volume or volume created on the storage controller shown in the detailed information. When deleting snapshots, delete all the snapshots created in the snapshot tree. |
KARS06003-E |
The storage pool capacity controlled by the storage controller is depleted. (Storage controller ID = xxx) [Event Name] Storage pool capacity depletion(storage controller) [Category] StoragePool [Solution] Expand the storage pool controlled by the storage controller shown in the detailed information. Alternatively, delete the unnecessary snapshots or volumes created on the storage controller shown in the detailed information. When deleting snapshots, delete all the snapshots created in the snapshot tree. In addition, if the storage controller becomes depleted, volumes might not be recognized from the host. When volumes cannot be recognized even after the storage controller depletion is resolved, repeat the operation so that the volumes can be recognized. |
KARS06012-E |
The request could not be executed. [Cause] The available capacity of the storage pool managed by the storage controller is insufficient. (Storage controller ID = xxx) [Solution] Delete the unnecessary snapshot volume or volume created on the storage controller shown in the detailed information. When deleting snapshots, delete all the snapshots created in the snapshot tree. Alternatively, if you are a system administrator, add drives to expand the storage pool. If you are a VPS administrator, report the message contents to the system administrator. |
KARS06014-E |
The request could not be executed. [Cause] The specified volume cannot be deleted because it is connected to the compute node. [Solution] Disconnect the compute node from the specified volume, and then retry the operation. |
KARS06015-E |
The request could not be executed. [Cause] The storage controller temporarily stops accepting requests. [Solution] Wait a while, and then retry the operation. |
KARS06016-E |
The request could not be executed. [Cause] The specified volume does not exist on the storage controller. [Solution] Confirm volume status of the specified volume. If volume status is "CREATE_FAILED", create a new volume, and then retry the operation. Otherwise, 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. |
KARS06017-E |
The request could not be executed. [Cause] The specified volume is executing I/O requests from compute node. [Solution] Stop the I/O request from the Compute node to the specified volume, wait for a while and retry the operation. |
KARS06019-E |
The request could not be executed. [Cause] The specified volume is during deletion processing. [Solution] Check the specified volume. |
KARS06020-E |
The request could not be executed. [Cause] The specified volume is reserved. [Solution] Cancel the reserve of the specified volume. |
KARS06021-E |
The request could not be executed. [Cause] The volume for which thick provisioning is enabled cannot be created because the storage controller capacity is shrinking. [Solution] Wait until storage controller capacity shrinkage is completed, and then retry the operation. |
KARS06022-E |
The request could not be executed. [Cause] The volume path cannot be deleted because it is the last volume path used in the Universal Replicator pair. [Solution] Delete the volume pair state, and then retry the operation. |
KARS06031-E |
Updating software ends abnormally, because there is a problem in the storage controller. (Storage controller ID = xxx) [Event Name] Invalid update condition (Storage controller failure) [Category] StorageNode [Solution] Resolve the problem in the storage controller shown in the detailed information, and then update the software. |
KARS06050-E |
The request could not be executed. [Cause] Shrinkage of the storage controller capacity cannot be performed because the storage controller capacity has reached the lower limit. (Storage controller ID = xxx) [Solution] Review whether you need to reduce the storage controller capacity indicated as an error cause. |
KARS06051-E |
The request could not be executed. [Cause] Shrinkage of the storage controller capacity cannot be performed because the storage controller capacity usage after shrinkage exceeds the usage threshold. (Storage controller ID = xxx) [Solution] Reduce the storage controller capacity usage indicated as an error cause. |
KARS06101-E |
The request could not be executed. [Cause] The specified volume does not exist. [Solution] Revise the ID or name of the specified volume. |
KARS06102-E |
The request could not be executed. [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. |
KARS06103-E |
The request could not be executed. [Cause] There is a problem in the specified volume. [Solution] Resolve the problem, and then retry the request. |
KARS06104-E |
The request could not be executed. [Cause] No more Snapshot can be created, because the number of volumes and snapshots per storage controller has reached the maximum. (Storage controller ID = xxx) [Solution] Delete the unnecessary volume or snapshot volume created on the storage controller shown in the detailed information, and then retry the operation. |
KARS06105-E |
The request could not be executed. [Cause] The specified parameters are invalid. [Solution] Check the parameters. |
KARS06106-E |
The request could not be executed. [Cause] The snapshot operation cannot be performed on the specified volume. [Solution] Check the specified volume. |
KARS06107-E |
The request could not be executed. [Cause] The specified volume is not a snapshot. [Solution] Check the specified volume. |
KARS06108-E |
The request could not be executed. [Cause] Snapshot operations might conflict, or the snapshot status of the specified volume might be ERROR. [Solution] Check the snapshot status of the specified volume, and then retry the operation. If the snapshot status is ERROR, delete the snapshot. If the specified snapshot has been deleted, there is no problem. |
KARS06109-W |
The request could not be executed. [Cause] The operations that cannot be executed concurrently are being executed. [Solution] Wait a while, and then retry the operation. |
KARS06110-E |
The request could not be executed. [Cause] Accesses to the database are congested, or the database is not operating correctly. [Solution] Wait a while, and then retry the operation. |
KARS06111-W |
The request could not be executed. [Cause] An error occurred while storage systems are communicating each other. [Solution] If you are a system administrator, verify the network configuration, and then retry the operation. If you are a VPS administrator, report the message contents to the system administrator. |
KARS06112-E |
The request could not be executed. [Cause] There is a problem in the restore destination volume. [Solution] Resolve the problem in the restore target volume, and then retry the operation. |
KARS06113-E |
The request could not be executed. [Cause] An internal error occurred. [Solution] If the snapshot status is ERROR, delete the snapshot. If the snapshot status is other than ERROR and 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. |
KARS06114-E |
The request could not be executed. [Cause] An internal error occurred. [Solution] Delete the snapshot. When deleting snapshots, delete all the snapshots created in the snapshot tree. If you have backed-up data, use the data to restore the data in the volume to be restored. |
KARS06115-W |
The request could not be executed. [Cause] An internal error occurred. [Solution] Make sure that you have not performed another snapshot operation on the snapshot. If you have not performed the operation and you are a system administrator, collect the logs (including the dump log file of the storage controller), and then contact customer support. If you are a VPS administrator, report the message contents to the system administrator. |
KARS06116-E |
The request could not be executed. [Cause] The volume status of some snapshots are not in the normal status. [Solution] Resolve the problem in the snapshot volume, and then retry the operation. |
KARS06117-E |
The request could not be executed. [Cause] The snapshot cannot be created because the number of cascaded snapshot layers exceeded the maximum. (Storage controller ID = xxx) [Solution] Delete the unnecessary snapshots created on the storage controller shown in the detailed information. |
KARS06118-E |
The request could not be executed. [Cause] The snapshot cannot be created because the resources for snapshot management are depleted. (Storage controller ID = xxx) [Solution] Delete the unnecessary snapshots or volumes created on the storage controller shown in the detailed information. When deleting snapshots, delete all the snapshots created in the snapshot tree. |
KARS06119-E |
The request could not be executed. [Cause] Another operation is in progress in the specified volume. [Solution] Verify whether the correct volume is specified. If the specified volume is correct and you are a system administrator, wait until other operations are complete, and then retry the operation. If you are a VPS administrator, report the message contents to the system administrator. |
KARS06120-E |
The request could not be executed. [Cause] All snapshot statuses of the snapshots created from the specified volumes are ERROR. [Solution] Delete the snapshots whose status are ERROR, and then retry the operation. |
KARS06121-E |
The request could not be executed. [Cause] An internal error occurred. [Solution] Wait a while, and then retry the operation. If the same error occurs and 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. |
KARS06122-E |
The request could not be executed. [Cause] The snapshot cannot be deleted because other snapshots were created from the specified snapshot. [Solution] Delete the other snapshots created from the specified snapshot, and then retry the operation. |
KARS06123-E |
The request could not be executed. [Cause] The snapshot created from the specified volume is being processed or in an error state. [Solution] Check if the specified volume is correct. If any snapshots are in an error state, delete them. |
KARS06124-E |
The request could not be executed. [Cause] This operation cannot be performed on the specified volume. [Solution] Specify an S-VOL or P/S-VOL of snapshots for this operation. |
KARS06125-E |
The request could not be executed. [Cause] A snapshot cannot be created with the specified volume. [Solution] Specify a volume whose type is Normal or Snapshot. |
KARS06126-E |
The request could not be executed. [Cause] The specified volume is not a P-VOL of snapshots. [Solution] Check if the snapshotAttribute of the specified volume is P-VOL. |
KARS06127-E |
The request could not be executed. [Cause] The snapshot cannot be created because the storage pool capacity controlled by the storage controller exceeded the threshold of snapshot creation. (Storage controller ID = xxx) [Solution] Delete unnecessary snapshots or volumes created on the storage controller shown in the detailed information. When deleting snapshots, delete all the snapshots created in the snapshot tree. |
KARS06128-E |
The request could not be executed. [Cause] Volume management resources ran out. (Storage controller ID = xxx) [Solution] Delete unnecessary snapshots or volumes created on the storage controller shown in the detailed information. When deleting snapshots, delete all the snapshots created in the snapshot tree. |
KARS06129-E |
The request could not be executed. [Cause] The storage cluster is in a state where snapshot operation is not possible. [Solution] Make the storage cluster state ready for snapshot operation, and then retry the operation. |
KARS06130-E |
The request could not be executed. [Cause] The specified volume cannot be deleted or restored because the volume type is not Snapshot. [Solution] Specify a volume whose type is Snapshot. |
KARS06131-E |
The request could not be executed. [Cause] The snapshot cannot be created because the specified volume name already exists. [Solution] Specify a unique name, and then try again. |
KARS06132-C |
Invalid snapshots were detected. (Storage controller ID = xxx) [Event Name] Invalid snapshots were detected [Category] SnapShot [Solution] Delete all the S-VOLs and P/S-VOLs (managed by the storage controller in this message) whose snapshotStatus is Error. |
KARS06133-I |
All snapshots in an invalid status have been deleted. (Storage controller ID = xxx) [Event Name] Deleting invalid snapshots is completed [Category] SnapShot |
KARS06134-E |
Any snapshot operations other than the snapshot deletion are suppressed. (Storage controller ID = xxx) [Cause] Any snapshot operations other than the snapshot deletion are suppressed because the snapshot is in an invalid state. [Solution] If you are a system administrator, delete the snapshot volumes. If event log KARS06132-C was not output, delete the snapshot volumes by using the controller ID indicated in this message. If you are a VPS administrator, report the message contents to the system administrator. |
KARS06135-E |
None or only some of the snapshots created from the specified volume could be deleted forcibly. [Cause] None or only some of snapshots created from the specified volume could be deleted forcibly although retry was performed until the limit. [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. |
KARS06136-E |
The request could not be executed. [Cause] This operation might not be performed depending on the snapshot status associated with the specified volume. If the snapshot status is Error, delete the snapshot. [Solution] After verifying the snapshot status associated with the specified volume, see the VSP One SDS Block System Administrator Operation Guide and review the operation details. |
KARS06137-E |
The request could not be executed. [Cause] Inconsistent status of the specified volume with data reduction enabled was detected. It might take some time for the status of the volume to be reflected. [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. |
KARS06138-E |
The request could not be executed. [Cause] Inconsistent status of the restore-destination volume with data reduction enabled was detected. It might take some time for the status of the volume to be reflected. [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. |
KARS06140-E |
The request could not be executed. [Cause] The database is not operating correctly. [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. |
KARS06141-E |
The request could not be executed. [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. |
KARS06142-I |
Snapshot restoration was canceled. (Volume ID = xxx) [Cause] Snapshot restoration was canceled to allow for a high-priority operation. Restoration will be resumed in the background after the high-priority operation. [Solution] See the volume information to verify that snapshot restoration is completed. Completing restoration changes the snapshot status from Restoring to Prepared. If snapshotStatus changes from Restoring to Error, refer to the VSP One SDS Block System Administrator Operation Guide, and select the snapshot volume displayed in the detailed information and the volume to be restored. Please delete it. |
KARS06143-E |
Snapshots could not be restored. [Cause] The number of snapshot restore jobs in progress is too many. [Solution] Verify that at least one snapshot restoration job is completed by referring to the volume information, and then retry the operation. Completing snapshot restoration changes the snapshot status from Restoring to Prepared. |
KARS06144-I |
Snapshot deletion was canceled. (Volume ID = xxx) [Cause] Snapshot deletion was canceled to allow for a high-priority operation. [Solution] If a snapshot volume remains, delete it. |
KARS06145-W |
The operation failed because it cannot be executed state at the same time to perform the operation for preparing to take a snapshot and the operation for taking a snapshot. [Cause] The operation fails because the snapshot status of the volume specified when performing to sequentially perform the operation for preparing to take a snapshot and the operation for taking a snapshot is Preparing. [Solution] Set the snapshot status of the specified volume to Normal before executing the operation. |
KARS06146-W |
The operation failed because it cannot be executed state at the same time to perform the operation for preparing to take a snapshot and the operation for taking a snapshot. [Cause] The operation fails because the snapshot status of the volume specified when performing to sequentially perform the operation for preparing to take a snapshot and the operation for taking a snapshot is Prepared. [Solution] Set the snapshot status of the specified volume to Normal before executing the operation and re-execute the operation. If operate the specified volume with the snapshot status as Prepared, execute the operation for taking a snapshot. |
KARS06147-E |
Snapshots could not be deleted. [Cause] The number of snapshot deletion jobs in progress is too many. [Solution] Wait for approximately 5 minutes, and then retry the operation. |
KARS06148-E |
The request could not be executed. [Cause] Snapshot operation for the specified volume is not possible. [Solution] Verify whether the correct volume is specified. When you perform snapshot operation for a volume in a virtual private storage, specify the ID of the VPS in which the volume exists. |
KARS06149-E |
The request could not be executed. [Cause] Snapshot restoration was unsuccessful because the volume was being used as a P-VOL or S-VOL of Universal Replicator and writing to the volume was prohibited. [Solution] Release the data volume pair of Universal Replicator with writing to the volume enabled. |
KARS06150-E |
One or more invalid snapshots were detected. (Storage controller ID = xxx) [Event Name] Invalid snapshots were detected [Category] SnapShot [Solution] See the event logs indicating other errors, if any, and then take action. Then, review the list of the snapshot volumes managed by the storage controller indicated in this message, and then delete the snapshots whose snapshot status is ERROR. After the deletion is completed, create snapshots again as required. |
KARS06151-E |
The request could not be executed. [Cause] Snapshot creation was unsuccessful because the Universal Replicator data volume was in COPY status. [Solution] Wait until the Universal Replicator data volume becomes PAIR status, or split the pair to retry the operation. |
KARS06152-E |
The request could not be executed. [Cause] Restore is not possible because the pair status of Universal Replicator is other than unpaired and suspending status. [Solution] Change the pair status of Universal Replicator to suspending status, or delete the pair to change the pair status to unpaired status, and then retry the operation. |
KARS06153-E |
The request could not be executed. [Cause] Restore to an S-VOL of Universal Replicator cannot be performed. [Solution] Verify whether the correct volume is specified. If the correct volume is specified, switch a P-VOL and S-VOL of Universal Replicator, change the pair status to suspending status, and then retry the operation. Or, delete the Universal Replicator pair to change the pair status to unpaired status, and then retry the operation. |
KARS06160-I |
The snapshot restore execution has been paused due to an increased utilization of internal resources on the storage node. If the internal resource utilization of the storage node is degraded, the snapshot restore is automatically restarted. (Storage controller ID = xxx) [Event Name] High load of internal resources for storage nodes [Category] SnapShot [Solution] Reduce usage of internal resources managed by the storage controller indicated in this message (for example, by reducing I/O load). |
KARS06170-C |
Since it was detected that the volume was in an invalid state when the storage cluster was started, I / O processing will not be accepted. (Volume ID = xxx) [Event Name] Invalid P-VOL were detected [Category] SnapShot [Solution] Refer to the VSP One SDS Block System Administrator Operation Guide, and delete all the volumes displayed in the detailed information and the snapshots (S-VOL, P/S-VOL) under them. Until the volume deletion displayed in the detailed information is completed, the reduction of the storage node containing the volume and the snapshot operation (other than deletion) that specifies the volume will fail. |
KARS06201-E |
Volume deletion processing ended abnormally. (Storage controller ID = xxx) [Event Name] Volume deletion processing error [Category] DataReduction [Solution] Collect the logs, and then contact customer support. |
KARS06209-E |
The request could not be executed. [Cause] Volume operation timed out. [Solution] Verify whether there is a volume that could not be deleted. If such a volume exists, retry the operation. If any storage nodes are blocked, recover them before you retry the operation. If no storage node is blocked and volume operation timed out with host I/O operation running, reduce the I/O load, and then retry the operation. |
KARS06212-I |
Inflow restriction (I/O suppression) for the volume with data reduction enabled was canceled because the insufficient capacity of the storage pool managed by the storage controller was resolved. (Storage controller ID = xxx) |
KARS06213-W |
Inflow restriction (I/O suppression) for the volume with data reduction enabled was started because the capacity of the storage pool managed by the storage controller was insufficient. (Storage controller ID = xxx) |
KARS06214-E |
The storage cluster could not be started because the minimum memory capacity is less than 234 GiB when volumes with data reduction enabled exist. (Protection domain ID = xxx) [Event Name] Storage cluster starting stopped due to insufficient memory capacity [Category] DataReduction [Solution] See the VSP One SDS Block System Administrator Operation Guide to stop all the storage nodes forcibly. After that, allocate memory of 234 GiB to all the storage nodes, and then restart the storage cluster. |
KARS06215-E |
Storage node maintenance recovery was canceled because the memory capacity of the storage node subject to maintenance recovery is less than the minimum memory capacity xxx MiB in the protection domain. [Event Name] Memory capacity of the storage node subject to maintenance recovery is less than the minimum [Category] StorageNode [Solution] Allocate memory capacity to storage nodes subject to maintenance recovery so that the capacity is at least the minimum, and then perform maintenance recovery for the storage node. |
KARS06216-I |
Inflow restriction (I/O suppression) for each volume was canceled because depletion of internal resources for each volume was resolved. (Storage controller ID = xxx, Volume ID = xxx) [Event Name] Inflow restriction (I/O suppression) canceled [Category] DataReduction |
KARS06217-W |
Inflow restriction (I/O suppression) for each volume was started because internal resources for each volume are depleted. (Storage controller ID = xxx, Volume ID = xxx) [Event Name] Inflow restriction (I/O suppression) started [Category] DataReduction |
KARS06218-W |
Inflow restriction (I/O suppression) for the volumes with data reduction enabled was started because the free space of the storage pool managed by the storage controller was insufficient with cached data accumulated. (Storage controller ID = xxx) [Event Name] Inflow restriction (I/O suppression) started [Category] DataReduction |
KARS06220-C |
Invalid volumes with data reduction enabled were detected. (Storage controller ID = xxx) [Event Name] Invalid volumes with data reduction enabled were detected [Category] DataReduction [Solution] Collect the logs, and then contact customer support. |
KARS06221-C |
The data reduction function operation ended abnormally. (Storage controller ID = xxx, Volume ID = xxx, LBA = xxx) [Event Name] Abnormal data reduction operation [Category] DataReduction [Solution] Collect the logs, and then contact customer support. |
KARS06222-C |
The data reduction function operation ended abnormally. (Storage controller ID = xxx, Volume ID = xxx) [Event Name] Abnormal data reduction operation [Category] DataReduction [Solution] Collect the logs, and then contact customer support. |
KARS06230-E |
Storage cluster starting was stopped because the minimum memory capacity was changed when planned shutdown of the storage cluster did not complete normally. (Protection domain ID = xxx, Minimum memory capacity before change = xxx, Minimum memory capacity after change = xxx) [Event Name] Storage cluster startup stopped due to memory change in failed storage cluster planned shutdown [Category] StorageCluster [Solution] See the VSP One SDS Block System Administrator Operation Guide and shut down all the storage nodes forcibly. Change the minimum memory capacity back to the state before change, and then start the storage cluster again. |
KARS06300-I |
The volume has been migrated(Volume unit). (Volume ID = xxx, Job ID = xxx) [Event Name] One volume migration completed [Category] Migration |
KARS06301-I |
Migration complete volume displays additional information(Volume unit). (Migration source storage node ID = xxx, Migration destination storage node ID = xxx, Job ID = xxx) [Event Name] Additional information for the migration completed volume [Category] Migration |
KARS06302-I |
The volume has been migrated xxx%. (Total volume capacity to be migrated = xxxbyte, Job ID = xxx) [Event Name] Copy progress notification [Category] Migration |
KARS06303-I |
Migration of the volume started. (Job ID = xxx) [Event Name] Volume migration started [Category] Migration |
KARS06304-I |
All volumes have been migrated. (Job ID = xxx) [Event Name] Whole volume migration completed [Category] Migration |
KARS06305-I |
Started data migration of the ExternalVolumes in the storage node and they can accept access from compute nodes. (Storage node ID = xxx, Job ID = xxx) [Event Name] Data migration of all external volumes started [Category] Migration |
KARS06306-I |
Volume migration started. (Number of volumes = xxx, Job ID = xxx) [Event Name] Volume migration started [Category] Migration |
KARS06310-E |
An unexpected error has occurred during volume migration. (Job ID = xxx) [Event Name] Internal error occurred [Category] Migration [Solution] Collect the logs, and then contact customer support. |
KARS06311-E |
Recovery processing for volume migration has timed out. (Job ID = xxx) [Event Name] Volume migration recovery timeout [Category] Migration [Solution] Collect the logs, and then contact customer support. |
KARS06320-E |
It is taking more time than usual to migrate the volume. (Job ID = xxx) [Event Name] Volume migration delayed [Category] Migration [Solution] Check the progress rate displayed in event log KARS06302-I which is output regularly. Contact customer support if processing has not progressed. |
KARS06330-I |
Rebuilding of the drive overrode and canceled volume migration. (Job ID = xxx) [Event Name] Volume migration canceled [Category] Migration [Solution] Wait until the drive is rebuilt, and then retry the operation. |
KARS06331-I |
Volume migration was canceled for a higher-priority operation. (Job ID = xxx) [Event Name] Volume migration cancel request received [Category] Migration [Solution] Wait a while, and then retry the operation. |
KARS06332-I |
Volume migration was canceled to allow for a high-priority operation or by a detected volume migration cancellation request (unit: volume). (Volume ID = xxx, Job ID = xxx) [Event Name] One volume migration canceled [Category] Migration |
KARS06333-I |
Volume migration was canceled to allow for a high-priority operation (unit: volume). For Capacity balance that runs automatically, no action is required. (Volume ID = xxx, Job ID = xxx) [Event Name] Volume migration canceled to allow for a high-priority operation [Category] Migration |
KARS06334-E |
Volume migration was canceled because resources could not be secured. (Volume ID = xxx, Job ID = xxx) [Event Name] Migration canceled due to volume resource allocation failure [Category] Migration [Solution] Wait a while, and then retry the operation. |
KARS06335-I |
Volume migration was canceled because some drives need to be rebuilt. (Job ID = xxx) [Event Name] Volume migration canceled [Category] Migration |
KARS06336-I |
Volume migration was canceled to allow for a high-priority operation or by a volume migration cancellation request. (Job ID = xxx) [Event Name] Volume migration cancel request received [Category] Migration |
KARS06337-I |
Volume migration was canceled. (Protection domain ID = xxx, Job ID = xxx) [Event Name] Volume migration cancel request received [Category] Migration |
KARS06339-E |
Volume migration was canceled because the capacity of the storage pool managed by the migration destination storage controller is almost depleted. (Job ID = xxx) [Event Name] Migration canceled due to detection of insufficient capacity [Category] Migration [Solution] Retry the operation. |
KARS06340-E |
Processing failed because an abnormal volume was instructed to migrate. (Volume ID = xxx, Job ID = xxx) [Event Name] Invalid volume status [Category] Migration [Solution] Try again after restoring the volume to normal. |
KARS06341-E |
Migration failed because the volume to be migrated has snapshots. (Volume ID = xxx, Job ID = xxx) [Event Name] Volume migration directed on a volume with snapshot [Category] Migration [Solution] Try again after deleting snapshots from the volume to be migrated. |
KARS06342-E |
Migration failed because the volume to be migrated was being used by another volume migration process. (Volume ID = xxx, Job ID = xxx) [Event Name] Duplicated volume migration instruction [Category] Migration [Solution] Try again after ongoing volume migration has been finished. |
KARS06344-E |
I/O for volume migration was unsuccessful. (Volume ID = xxx, Job ID = xxx) [Event Name] I/O for volume migration failed [Category] Migration [Solution] See the event logs indicating other errors, if any, and then take action. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS06345-E |
Communication with the volume migration source storage node failed during volume migration. (Migration source storage node ID = xxx, Job ID = xxx) [Event Name] Failed to access the source node of volume migration [Category] Migration [Solution] Try again after restoring the volume migration source storage node to normal. |
KARS06346-E |
Access to the database failed during volume migration. (Job ID = xxx) [Event Name] Failed to access the database [Category] Migration [Solution] Wait a while, and then retry the operation. When the same error occurs, collect the logs, and then contact customer support. |
KARS06347-E |
Communication between storage nodes failed during volume migration. (Job ID = xxx) [Event Name] Inter-storage node communication failed [Category] Migration [Solution] Wait a while, and then retry the operation. |
KARS06348-E |
Recovery processing for volume migration failed. (Job ID = xxx) [Event Name] Volume migration recovery failed [Category] Migration |
KARS06349-E |
The storage cluster is not in a state available for volume migration. (Job ID = xxx) [Event Name] Invalid storage cluster status [Category] Migration [Solution] Try again after restoring the storage cluster to normal. |
KARS06350-E |
Volume migration failed due to insufficient memory capacity in the cluster master node (primary). (Job ID = xxx) [Event Name] Storage node memory shortage [Category] Migration [Solution] Wait a while, and then retry the operation. When the same error occurs, collect the logs, and then contact customer support. |
KARS06351-E |
Volume migration failed due to insufficient storage pool capacity. (Job ID = xxx) [Event Name] Pool capacity shortage [Category] Migration [Solution] Delete unnecessary volumes to free up storage pool space. |
KARS06352-E |
Volume migration failed because the maximum number of volumes has been reached. (Number of excess volumes = xxx, Job ID = xxx) [Event Name] Limit of the number of volumes [Category] Migration [Solution] Delete the excess volumes, and then try again. |
KARS06353-E |
Volume migration failed due to invalid storage controller status. (Volume ID = xxx, Job ID = xxx) [Event Name] Invalid storage controller status [Category] Migration [Solution] Wait a while, and then retry the operation. |
KARS06354-I |
Volume migration was canceled due to invalid storage controller status. (Volume ID = xxx, Job ID = xxx) [Event Name] Invalid storage controller status [Category] Migration |
KARS06355-E |
Volume migration for expanding the pool capacity was stopped. (Job ID = xxx) [Event Name] Addition of storage pool capacity controlled by the storage controller triggered by storage node removal [Category] Migration [Solution] Verify the event log about the addition of storage pool capacity controlled by the storage controller. If an event log (KARS16081-I, indicating that storage pool capacity controlled by the storage controller expansion was successful) is displayed, retry storage node removal. If a warning event log (KARS16018-W) is displayed, verify that event log (either KARS16017-I, KARS16020-I, KARS16022-I, or KARS16081-I, indicating that pool capacity expansion was successful) is also displayed, and then retry storage node removal. If a failure event log (KARS16019-E) is displayed, collect the logs, and then contact customer support. |
KARS06356-E |
Volume migration for expanding the pool capacity was stopped. (Job ID = xxx) [Event Name] Addition of storage pool capacity controlled by the storage controller [Category] Migration [Solution] Verify the event log about the addition of storage pool capacity controlled by the storage controller. If an event log (KARS16081-I, indicating that storage pool capacity controlled by the storage controller expansion was successful) is displayed, retry the operation. If a warning event log (KARS16018-W) is displayed, verify that event log (either KARS16017-I, KARS16020-I, KARS16022-I, or KARS16081-I, indicating that pool capacity expansion was successful) 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. |
KARS06357-I |
Volume migration was canceled because the volume to be migrated was being used by another volume migration process. (Volume ID = xxx, Job ID = xxx) [Event Name] Duplicated volume migration instruction [Category] Migration |
KARS06358-W |
I/O for volume migration was unsuccessful. (Volume ID = xxx, Job ID = xxx) [Event Name] I/O for volume migration failed [Category] Migration |
KARS06359-I |
Volume migration was canceled because communication with the volume migration source storage node did not succeed. (Migration source storage node ID = xxx, Job ID = xxx) [Event Name] Failed to access the source node of volume migration [Category] Migration |
KARS06360-I |
Volume migration was canceled because access to the database did not succeed. (Job ID = xxx) [Event Name] The database could not be accessed [Category] Migration |
KARS06361-I |
Volume migration was canceled because communication between storage nodes did not succeed. (Job ID = xxx) [Event Name] Inter-storage node communication failed [Category] Migration |
KARS06362-W |
Volume migration was canceled because the storage cluster is not in a state that allows for volume migration. (Job ID = xxx) [Event Name] Invalid storage cluster status [Category] Migration |
KARS06363-I |
Volume migration was canceled because insufficient memory capacity in the cluster master node (primary). (Job ID = xxx) [Event Name] Storage node memory shortage [Category] Migration |
KARS06364-I |
Volume migration was canceled because Processing did not succeed because migration of an abnormal volume. (Volume ID = xxx, Job ID = xxx) [Event Name] Volume status invalid [Category] Migration |
KARS06365-I |
Volume migration was canceled because the volume to be migrated has snapshots. (Volume ID = xxx, Job ID = xxx) [Event Name] Volume migration directed on a volume with snapshot [Category] Migration |
KARS06366-E |
Volume migration was unsuccessful because the volume was invalid. (Volume ID = xxx, Job ID = xxx) [Event Name] Volume migration was unsuccessful because the volume was invalid [Category] Migration [Solution] Collect the logs, and then contact customer support. |
KARS06367-E |
I/O for volume migration was unsuccessful. (Volume ID = xxx, Job ID = xxx) [Event Name] I/O for volume migration failed [Category] Migration |
KARS06368-E |
Migration processing was unsuccessful because the volume to be migrated contained a Universal Replicator pair or a journal volume. (Volume ID = xxx, Job ID = xxx) [Event Name] Migration guard of a Universal Replicator pair or a journal volume [Category] Migration [Solution] Exclude the Universal Replicator pair or journal volume from the migration, and then retry the operation. |
KARS06400-E |
A file in the storage node could not be deleted. (Storage node ID = xxx, File path = xxx) [Event Name] cfm.dat file delete failed [Category] StorageNode [Solution] Delete the file according to the message. Or, replace the storage node. |
KARS06401-E |
Storage controller configuration recovery processing was unsuccessful. (Storage controller ID = xxx) [Event Name] Storage controller config recovery failure [Category] StorageNode [Solution] Collect the logs, and then contact customer support. |
KARS06410-E |
Update of the storage software ended abnormally due to a storage controller failure. (Storage controller ID = xxx, Job ID = xxx) [Event Name] Invalid software update conditions (Storage controller failure) [Category] StorageNode [Solution] Perform maintenance recovery for the storage node managed by the faulty storage controller indicated in this message. Then, update the storage software again. |
KARS06411-E |
The request could not be executed. (Job ID = xxx) [Event Name] Database access error [Category] StorageNode [Solution] Wait a while, and then retry the operation. When the same error occurs, collect the logs, and then contact customer support. |
KARS06412-C |
An internal error occurred in the storage node. This storage node stops accepting I/O operations. (Storage node ID = xxx) [Event Name] Stops accepting I/O operations due to an internal error [Category] StorageNode [Solution] If there are blocked storage nodes, perform maintenance recovery for the storage nodes. If I/O operation does not restart after storage node maintenance recovery, after the event log KARS07001-I is generated, perform maintenance blockade for the storage nodes in which an internal error indicated in this message occurred. Storage node maintenance blockade restarts I/O operation. After storage node maintenance blockade, perform maintenance recovery for the storage nodes in which an internal error indicated in this message occurred. Do not perform a planned shutdown of the storage cluster until I/O operation restarts after storage node maintenance blockade. |
KARS06413-W |
Balancing processing of user data capacity managed by each storage controller ended abnormally. (Storage controller ID = xxx) [Event Name] Balancing processing of user data capacity managed by each storage controller stopped [Category] StorageNode [Solution] Collect the logs, and then contact customer support. |
KARS06414-W |
An internal error occurred in the storage node. Balancing processing of user data capacity managed by each storage controller ended abnormally. (Storage node ID = xxx, Storage controller ID = xxx) [Event Name] Balancing processing of user data capacity managed by each storage controller stopped [Category] StorageNode [Solution] If there are blocked storage nodes, perform maintenance recovery for the storage nodes. If blocked storage nodes no longer exist, perform maintenance blocking for the storage nodes in which an internal error (as indicated in this message) occurred. After storage node maintenance blocking, perform maintenance recovery for the storage nodes in which an internal error (as indicated in this message) occurred. |
KARS06450-E |
The request could not be executed. [Cause] The status of the storage cluster is invalid. [Solution] Wait until the status of the storage cluster is Ready, and then retry the operation. |
KARS06451-E |
The request could not be executed. [Cause] The specified parameters are invalid. [Solution] Verify the parameter settings, and then retry the operation. |
KARS06452-E |
The request could not be executed. [Cause] The operations that cannot be executed at the same time are executing. [Solution] Verify whether no other operation is being performed. If no other operation is being performed, retry the operation. If any other operation is being performed, wait until it is complete, and then retry the operation. |
KARS06453-E |
The request could not be executed. [Cause] An unexpected error occurred. [Solution] Collect the logs, and then contact customer support. |
KARS06454-E |
The request could not be executed. [Cause] Accesses to the database are congested, or the database is not operating correctly. [Solution] Wait a while, and then retry the operation. |
KARS06455-E |
The request could not be executed. [Cause] Recovery of storage controller configuration information did not succeed. [Solution] Collect the logs, and then contact customer support. |
KARS06456-E |
The request could not be executed. [Cause] The storage cluster status is not in maintenance mode. [Solution] Make transition to maintenance mode for the storage cluster, and then retry the operation. |
KARS06460-E |
The redundancy of the storage controller in the storage node is degraded. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Maintenance pre-check (Storage controller redundancy degraded) [Category] StorageNode [Solution] Perform maintenance recovery for the blocked storage node, make the storage controller redundant, and then retry the operation. |
KARS06461-E |
The redundancy of the storage controller in the storage node is degraded by two. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Maintenance pre-check (Storage controller redundancy degraded by two) [Category] StorageNode [Solution] Perform maintenance recovery for the two or more blocked storage nodes, make the storage controller redundant, and then retry the operation. |
KARS06462-E |
The processing cannot be performed because the status of the storage node in which Standby that is the redundancy-destination of the storage controller is located is not Ready and the storage controller is not redundant. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Maintenance pre-check (Redundant storage node not ready) [Category] StorageNode [Solution] If the storage node in which Standby of the target storage controller is located is undergoing maintenance, wait until the processing for the storage node is completed, and then retry the operation. If there are any blocked storage nodes, perform maintenance recovery for them, make the storage controller redundant, and then retry the operation. |
KARS06463-E |
The processing cannot be performed because the status of the storage node in which Standby that is the redundancy-destination of the storage controller is located is not Ready and the storage controller is not redundant. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Maintenance pre-check (Redundant storage node not ready) [Category] StorageNode [Solution] If the storage node in which Standby of the target storage controller is located is undergoing maintenance, wait until the processing for the storage node is completed, and then retry the operation. If there are any blocked storage nodes, perform maintenance recovery for two or more storage nodes, make the storage controller redundant, and then retry the operation. |
KARS06464-E |
The processing cannot be performed because two Active storage controllers exist in the storage node in which Standby that is the redundancy-destination of the storage controller is located. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Maintenance pre-check (Redundant storage node not ready) [Category] StorageNode [Solution] Perform maintenance recovery for all the blocked storage nodes, make the storage controller redundant, and then retry the operation. |
KARS06470-E |
The redundancy of the storage controller in the storage node is degraded. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Storage node removal pre-check (Storage controller redundancy degraded) [Category] StorageNode [Solution] Perform maintenance recovery for the blocked storage node, make the storage controller redundant, and then retry the operation. |
KARS06471-E |
The redundancy of the storage controller in the storage node is degraded by two. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Storage node removal pre-check (Storage controller redundancy degraded by two) [Category] StorageNode [Solution] Perform maintenance recovery for the two or more blocked storage nodes, make the storage controller redundant, and then retry the operation. |
KARS06472-E |
The processing cannot be performed because the status of the storage node in which Standby that is the redundancy-destination of the storage controller is located is not Ready and the storage controller is not redundant. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Storage node removal pre-check (Redundant storage node not ready) [Category] StorageNode [Solution] If the storage node in which Standby of the target storage controller is located is undergoing maintenance, wait until the processing for the storage node is completed, and then retry the operation. If there are any blocked storage nodes, perform maintenance recovery for them, make the storage controller redundant, and then retry the operation. |
KARS06473-E |
The processing cannot be performed because the status of the storage node in which Standby that is the redundancy-destination of the storage controller is located is not Ready and the storage controller is not redundant. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Storage node removal pre-check (Redundant storage node not ready) [Category] StorageNode [Solution] If the storage node in which Standby of the target storage controller is located is undergoing maintenance, wait until the processing for the storage node is completed, and then retry the operation. If there are any blocked storage nodes, perform maintenance recovery for two or more storage nodes, make the storage controller redundant, and then retry the operation. |
KARS06474-E |
The processing cannot be performed because two Active storage controllers exist in the storage node that is the redundancy destination of the storage controller. (Job ID = xxx, Storage controller ID = xxx) [Event Name] Storage node removal pre-check (Redundant storage node not ready) [Category] StorageNode [Solution] Perform maintenance recovery for all the blocked storage nodes, make the storage controller redundant, and then retry the operation. |
KARS06480-E |
Two Active storage controllers exist in the storage node in which the Active storage controller is to be created. (Job ID = xxx, HostName = xxx) [Event Name] Addition of storage nodes failed (Storage controller creation failed) [Category] StorageNode [Solution] If some storage controllers are degraded in redundancy, perform maintenance recovery for the blocked storage nodes, make the storage controllers redundant, and then retry the operation. |
KARS06485-C |
Storage controller I/O was stopped because two other Active storage controllers exist in the storage node in which a Standby system of this storage controller is located. (Storage controller ID = xxx) [Event Name] The storage controller I/O function stopped [Category] StorageNode [Solution] Collect the logs, and then contact customer support. |
KARS06500-W |
The memory usage of the data capacity of a storage controller is increasing. Therefore, host I/O inflow for volumes is restricted. (Storage controller ID = xxx) [Event Name] Inflow restriction occurred [Category] Volume [Solution] Specify the ID of the storage controller, and then obtain a list of volume information. Verify that performance is not degraded for the target volume. If the volume belongs to a virtual private storage, report the message contents to the VPS administrator who manages the virtual private storage and ask them to handle the performance degradation as required. |
KARS06501-C |
PIN status occurred in a storage controller. (Storage controller ID = xxx) [Event Name] Abnormal cache memory [Category] PIN [Solution] whether PIN status has occurred. If it has occurred, collect the logs, and then contact customer support. |
KARS06510-I |
Preparation for enabling the write back mode with cache protection has completed successfully. (Job ID = xxx) [Event Name] Preparation for enabling write back mode with cache protection completed successfully [Category] StorageCluster [Solution] Restart the storage cluster, and then complete enabling of the write back mode with cache protection. |
KARS06511-I |
Preparation for disabling the write back mode with cache protection has completed successfully. (Job ID = xxx) [Event Name] Preparation for disabling write back mode with cache protection completed successfully [Category] StorageCluster [Solution] Restart the storage cluster, and then complete disabling of the write back mode with cache protection. |
KARS06512-I |
The write back mode with cache protection has been enabled. (Job ID = xxx) [Event Name] Write back mode with cache protection has been enabled successfully [Category] StorageCluster |
KARS06513-I |
The write back mode with cache protection has been disabled. (Job ID = xxx) [Event Name] Write back mode with cache protection has been disabled successfully [Category] StorageCluster |
KARS06514-W |
The write back mode with cache protection is already in the specified state. (Job ID = xxx) [Event Name] Write back mode with cache protection is already in the specified state [Category] StorageCluster [Solution] Review the specified write back mode with cache protection. |
KARS06515-E |
The write back mode with cache protection could not be updated because of another operation in progress. (Job ID = xxx) [Event Name] Write back mode with cache protection update was aborted to allow for a high-priority operation [Category] StorageCluster [Solution] Wait for a while, and then retry the update of the write back mode with cache protection. If the problem persists, collect the logs, and then contact customer support. |
KARS06516-E |
The write back mode with cache protection could not be updated because of a blocked storage node. (Job ID = xxx, Storage node ID = xxx) [Event Name] Write back mode with cache protection update error [Category] StorageCluster [Solution] Recover the blocked storage node, and then retry the operation. |
KARS06517-E |
The write back mode with cache protection could not be updated because user data redundancy degraded. (Job ID = xxx) [Event Name] Write back mode with cache protection update error [Category] StorageCluster [Solution] Retry the operation after the data rebuild is complete |
KARS06518-E |
A failure occurred while enabling the write back mode with cache protection and the mode returned to the disabled state. (Job ID = xxx) [Event Name] Enabling write back mode with cache protection failed [Category] StorageCluster [Solution] To enable the write back mode with cache protection, retry the operation from making settings to enable the mode according to the VSP One SDS Block System Administrator Operation Guide. |
KARS06519-E |
The write back mode with cache protection was being updated, so the new request to update it was rejected. (Job ID = xxx) [Event Name] Write back mode with cache protection update error [Category] StorageCluster [Solution] Complete updating of the write back mode with cache protection in progress. |
KARS06520-E |
The write back mode with cache protection could not be updated because the number of drives for which storage pool expansion had been performed was less than three. (Job ID = xxx, Storage node ID = xxx, Deficit number of drives = xxx) [Event Name] Write back mode with cache protection update error [Category] StorageCluster [Solution] Perform storage pool expansion for the drive whose status is Offline on the specified storage node. If there are not sufficient drives, add drives to the specified storage node, and then perform storage pool expansion. |
KARS06521-E |
The write back mode with cache protection could not be updated. [Cause] Accesses to the database are congested, or the database is not operating correctly. [Solution] Wait a while, and then retry the operation. |
KARS06522-E |
The write back mode with cache protection could not be updated because of volumes with data reduction enabled. (Job ID = xxx) [Event Name] Write back mode with cache protection update error [Category] StorageCluster [Solution] Delete the volumes with data reduction enabled, and then retry the operation. |
KARS06523-E |
The write back mode with cache protection could not be updated because of blocked storage nodes. (Job ID = xxx) [Event Name] Write back mode with cache protection update error [Category] StorageCluster [Solution] Recover all the blocked storage nodes. |
KARS06524-E |
A failure occurred while disabling the write back mode with cache protection and the mode returned to the enabled state. (Job ID = xxx) [Event Name] Disabling write back mode with cache protection failed [Category] StorageCluster [Solution] To disable the write back mode with cache protection, retry the operation from making settings to disable the mode according to the VSP One SDS Block System Administrator Operation Guide. |
KARS06526-E |
The write back mode with cache protection could not be updated because of a virtual private storage with data reduction enabled. (Job ID = xxx) [Event Name] Write back mode with cache protection update error [Category] StorageCluster [Solution] Obtain a list of virtual private storage information to confirm the virtual private storages with data reduction enabled. Disable the data reduction function setting of all the virtual private storages with data reduction enabled, or delete all the virtual private storages with data reduction enabled, and then retry the operation. |
KARS06527-E |
The write back mode with cache protection could not be updated because resources related to the Universal Replicator function exist. (Job ID = xxx) [Event Name] Write back mode with cache protection update error [Category] StorageCluster [Solution] See the VSP One SDS Block Universal Replicator Guide to delete all Universal Replicator configuration information, and then retry the operation. |
KARS06529-E |
The write back mode with cache protection could not be updated. [Cause] An internal error occurred. [Solution] Wait a while, and then retry the operation. When the same error occurs, collect the logs, and then contact customer support. |
KARS06530-E |
The processing cannot be continued because metadata redundancy for the write back mode with cache protection degraded. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage node maintenance blocking pre-check [Category] StorageNode [Solution] See the VSP One SDS Block System Administrator Operation Guide to confirm the conditions for storage node maintenance blocking. Take necessary action according to the VSP One SDS Block System Administrator Operation Guide, and then retry the operation. |
KARS06531-E |
An error occurred while accessing the database. (Job ID = xxx) [Event Name] Database access error [Category] StorageNode [Solution] Wait a while, and then retry the operation. When the same error occurs, collect the logs, and then contact customer support. |
KARS06540-C |
The storage cluster could not be started because storage controller metadata could not be restored. (Storage controller ID = xxx) [Event Name] Starting the storage cluster failed (Metadata restore failed) [Category] StorageNode [Solution] whether failures occurred in the internode network, and then resolve the cause of any failures. Wait at least 45 minutes from when the event log was output, and then stop the storage cluster forcibly according to the VSP One SDS Block System Administrator Operation Guide. After that, start the storage cluster again according to the VSP One SDS Block System Administrator Operation Guide. If the same error occurs, collect the logs, and then contact customer support. |
KARS06550-W |
The write back mode with cache protection could not be updated. [Cause] The write back mode with cache protection is already in the specified state. [Solution] Review the specified write back mode with cache protection. |
KARS06551-E |
The write back mode with cache protection could not be updated. [Cause] Another operation is running. [Solution] Wait for a while, and then retry the update of the write back mode with cache protection. If the problem persists, collect the logs, and then contact customer support. |
KARS06552-E |
The write back mode with cache protection could not be updated. [Cause] One or more blocked storage nodes exist. [Solution] Recover the blocked storage nodes, and then retry the operation. |
KARS06553-E |
The write back mode with cache protection could not be updated. [Cause] User data redundancy is reduced. [Solution] Retry the operation after Data rebuild completes. |
KARS06554-E |
A new request for updating the write back mode with cache protection was rejected. [Cause] Updating of the write back mode with cache protection is already in progress. [Solution] Complete updating of the write back mode with cache protection in progress. |
KARS06555-E |
The write back mode with cache protection could not be updated. [Cause] One or more storage nodes on which the number of installed drives (for which storage pool expansion was performed) is fewer than three exist. [Solution] Take action according to the event log (KARS06520-E). |
KARS06556-E |
The write back mode with cache protection could not be updated. [Cause] Volumes with data reduction enabled exist. [Solution] Delete the volumes with data reduction enabled, and then retry the operation. |
KARS06557-E |
The write back mode with cache protection could not be updated. [Cause] Virtual private storages with data reduction enabled exist. [Solution] Obtain a list of virtual private storage information to confirm the virtual private storages with data reduction enabled. Disable the data reduction function setting of all the virtual private storages with data reduction enabled, or delete all the virtual private storages with data reduction enabled, and then retry the operation. |
KARS06558-E |
The write back mode with cache protection could not be updated. [Cause] Resources related to the Universal Replicator function exist. [Solution] See the VSP One SDS Block Universal Replicator Guide to delete all Universal Replicator configuration information, and then retry the operation. |
KARS06580-I |
Allocation of metadata capacity for the write back mode with cache protection started. (Storage controller ID = xxx) [Event Name] Metadata allocation processing start [Category] Drive |
KARS06581-I |
Allocation of metadata capacity for the write back mode with cache protection is complete. (Storage controller ID = xxx) [Event Name] Metadata allocation processing complete [Category] Drive |
KARS06582-I |
Allocation of metadata capacity for the write back mode with cache protection was aborted to allow for a high-priority operation. After the high-priority operation is completed, allocation of metadata capacity for the write back mode with cache protection will be resumed. (Storage controller ID = xxx) [Event Name] Metadata allocation processing aborted [Category] Drive |
KARS06583-E |
Allocation of metadata capacity for the write back mode with cache protection was unsuccessful. (Storage controller ID = xxx) [Event Name] Metadata allocation processing failed [Category] Drive [Solution] See the event logs indicating other errors, if any, and then take action. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS06584-I |
Prepare for capacity allocation processing of the storage controller is started. (Storage controller ID = xxx) [Event Name] Prepare for capacity allocation processing of the storage controller start [Category] Drive |
KARS06585-I |
Prepare for capacity allocation processing of the storage controller is complete. (Storage controller ID = xxx) [Event Name] Prepare for capacity allocation processing of the storage controller complete [Category] Drive |
KARS06586-I |
Prepare for capacity allocation processing of the storage controller was aborted to allow for a high-priority operation. After the high-priority operation is completed, prepare for capacity allocation processing of the storage controller will be resumed. (Storage controller ID = xxx) [Event Name] Prepare for capacity allocation processing of the storage controller aborted [Category] Drive |
KARS06587-E |
Prepare for capacity allocation processing of the storage controller was unsuccessful. (Storage controller ID = xxx) [Event Name] Prepare for capacity allocation processing of the storage controller failed [Category] Drive [Solution] See the event logs indicating other errors, if any, and then take action. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS06588-I |
Metadata redundancy of the write back mode with cache protection is degraded, so shrinkage of the metadata capacity for the write back mode with cache protection started. (Storage controller ID = xxx) [Event Name] Metadata capacity shrinkage start [Category] Drive |
KARS06589-I |
Shrinkage of the metadata capacity for the write back mode with cache protection is complete. (Storage controller ID = xxx) [Event Name] Metadata capacity shrinkage complete [Category] Drive |
KARS06590-I |
Shrinkage of the metadata capacity for the write back mode with cache protection was aborted to allow for a high-priority operation. After the high-priority operation is completed, shrinkage of the metadata capacity for the write back mode with cache protection will be resumed. (Storage controller ID = xxx) [Event Name] Metadata capacity shrinkage aborted [Category] Drive |
KARS06591-E |
Shrinkage of the metadata capacity for the write back mode with cache protection was unsuccessful. (Storage controller ID = xxx) [Event Name] Metadata capacity shrinkage failed [Category] Drive [Solution] See the event logs indicating other errors, if any, and then take action. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS06592-I |
Restoration of the metadata redundancy of the write back mode with cache protection started. (Storage controller ID = xxx) [Event Name] Metadata redundancy restoration start [Category] Drive |
KARS06593-I |
Recovery of metadata redundancy for the write back mode with cache protection was completed. Metadata redundancy may not have been partially recovered. To verify the metadata redundancy, see the VSP One SDS Block System Administrator Operation Guide. If metadata redundancy has not been fully recovered, drive addition or storage node maintenance recovery may be necessary. If event logs that require troubleshooting are output, take action according to the event log. (Storage controller ID = xxx) [Event Name] Metadata redundancy restoration complete [Category] Drive |
KARS06594-I |
Restoration of the metadata redundancy of the write back mode with cache protection was aborted to allow for a high-priority operation. After the high-priority operation is completed, restoration of the metadata redundancy of the write back mode with cache protection will be resumed. (Storage controller ID = xxx) [Event Name] Metadata redundancy restoration aborted [Category] Drive |
KARS06595-E |
Restoration of the metadata redundancy of the write back mode with cache protection was unsuccessful. (Storage controller ID = xxx) [Event Name] Metadata redundancy restoration failed [Category] Drive [Solution] See the event logs indicating other errors, if any, and then take action. If the phenomenon persists, collect the logs, and then contact customer support. |
KARS06596-E |
Restoration of the write back mode with cache protection could not be entirely completed because the number of drives required for the restoration is insufficient. (Storage node ID = xxx, Required additional number of drives = xxx) [Event Name] The number of drives to restore the metadata redundancy is insufficient [Category] Drive [Solution] Refer to the message, and then add new drives that satisfy system requirements to the target storage node. |
KARS06597-E |
The request could not be executed. [Cause] Metadata redundancy for the write back mode with cache protection is degraded. [Solution] Wait until metadata redundancy for the write back mode with cache protection recovers, and then retry the operation. However, if event log KARS06596-E (indicating that the number of drives is insufficient) is displayed, handle the problem according to the event log first. |
KARS06598-E |
The request could not be performed because metadata redundancy for the write back mode with cache protection is degraded. (Job ID = xxx) [Event Name] Invalid software update conditions (Metadata redundancy verification) [Category] StorageCluster [Solution] Wait until metadata redundancy for the write back mode with cache protection recovers, and then retry the operation. However, if event log KARS06596-E (indicating that the number of drives is insufficient) is displayed, handle the problem according to the event log first. |
KARS06600-W |
The volume I/O status exceeded the value set for the upper limit of volume performance. (Volume ID = xxx) [Event Name] QoS alert threshold was exceeded [Category] StorageCluster [Solution] See the volume list, and take the following actions if there are volumes that exceed the upper limit of the alert threshold. For volumes that do not belong to a virtual private storage, review the I/O load or QoS-related parameter settings as necessary. For volumes that belong to a virtual private storage, ask the VPS administrator who manages the virtual private storage to review the I/O load on the volumes or QoS-related parameter settings as necessary. |
KARS06701-I |
A Universal Replicator pair was created and a volume to serve as a P-VOL (or S-VOL) was specified. (Volume number = xxx) [Event Name] Universal Replicator pair creation [Category] UniversalReplicator |
KARS06702-I |
The Universal Replicator P-VOL (or S-VOL) started initial copy. (Volume number = xxx) [Event Name] Universal Replicator initial copy started [Category] UniversalReplicator |
KARS06703-I |
The Universal Replicator P-VOL (or S-VOL) completed initial copy. (Volume number = xxx) [Event Name] Universal Replicator initial copy completed [Category] UniversalReplicator |
KARS06704-I |
Pair suspending for the Universal Replicator P-VOL (or S-VOL) was requested. (Volume number = xxx) [Event Name] Universal Replicator pair suspending started [Category] UniversalReplicator |
KARS06705-I |
Pair suspending for the Universal Replicator P-VOL (or S-VOL) was completed. (Volume number = xxx) [Event Name] Universal Replicator pair suspending completed [Category] UniversalReplicator |
KARS06706-I |
Pair deletion for the Universal Replicator P-VOL (or S-VOL) was requested. (Volume number = xxx) [Event Name] Universal Replicator pair deletion started [Category] UniversalReplicator |
KARS06707-I |
Pair deletion for the Universal Replicator P-VOL (or S-VOL) was completed. (Volume number = xxx) [Event Name] Universal Replicator pair deletion completed [Category] UniversalReplicator |
KARS06709-I |
The pair status change (from SMPL to COPY) for the Universal Replicator S-VOL was instructed by the primary storage system. (Volume number = xxx) [Event Name] Universal Replicator S-VOL status changed [Category] UniversalReplicator |
KARS06710-I |
The pair status change (from SMPL to PAIR) for the Universal Replicator S-VOL was instructed by the primary storage system. (Volume number = xxx) [Event Name] Universal Replicator S-VOL status changed [Category] UniversalReplicator |
KARS06711-I |
The pair status change (from COPY to PAIR) for the Universal Replicator S-VOL was instructed by the primary storage system. (Volume number = xxx) [Event Name] Universal Replicator S-VOL status changed [Category] UniversalReplicator |
KARS06712-I |
The pair status change (from COPY to PSUS or PSUE) for the Universal Replicator S-VOL was instructed by the primary storage system. (Volume number = xxx) [Event Name] Universal Replicator S-VOL status changed [Category] UniversalReplicator |
KARS06713-I |
The pair status change (from PAIR to PSUS or PSUE) for the Universal Replicator S-VOL was instructed by the primary storage system. (Volume number = xxx) [Event Name] Universal Replicator S-VOL status changed [Category] UniversalReplicator |
KARS06714-I |
The pair status change (from PAIR to SMPL) for the Universal Replicator S-VOL was instructed by the primary storage system. (Volume number = xxx) [Event Name] Universal Replicator S-VOL status changed [Category] UniversalReplicator |
KARS06715-I |
The pair status change (from COPY to SMPL) for the Universal Replicator S-VOL was instructed by the primary storage system. (Volume number = xxx) [Event Name] Universal Replicator S-VOL status changed [Category] UniversalReplicator |
KARS06716-I |
The pair status change (from PSUS or PSUE to SMPL) for the Universal Replicator S-VOL was instructed by the primary storage system. (Volume number = xxx) [Event Name] Universal Replicator S-VOL status changed [Category] UniversalReplicator |
KARS06717-I |
The pair status change (from PSUS or PSUE to COPY) for the Universal Replicator S-VOL was instructed by the primary storage system. (Volume number = xxx) [Event Name] Universal Replicator S-VOL status changed [Category] UniversalReplicator |
KARS06725-I |
The pair status for the Universal Replicator S-VOL is changed from COPY or PAIR to Suspending. (Volume number = xxx) [Event Name] Universal Replicator S-VOL status changed [Category] UniversalReplicator |
KARS06726-I |
The pair status for the Universal Replicator S-VOL is changed from Suspending to PSUS or PSUE. (Volume number = xxx) [Event Name] Universal Replicator S-VOL status changed [Category] UniversalReplicator |
KARS06727-I |
The pair status for the Universal Replicator S-VOL is changed from PSUS or PSUE to Deleting. (Volume number = xxx) [Event Name] Universal Replicator S-VOL status changed [Category] UniversalReplicator |
KARS06728-I |
The pair status for the Universal Replicator S-VOL is changed from COPY to Deleting. (Volume number = xxx) [Event Name] Universal Replicator S-VOL status changed [Category] UniversalReplicator |
KARS06729-I |
The pair status for the Universal Replicator S-VOL is changed from PAIR to Deleting. (Volume number = xxx) [Event Name] Universal Replicator S-VOL status changed [Category] UniversalReplicator |
KARS06730-I |
The pair status for the Universal Replicator S-VOL is changed from Deleting to SMPL. (Volume number = xxx) [Event Name] Universal Replicator S-VOL status changed [Category] UniversalReplicator |
KARS06732-E |
One or more Universal Replicator P-VOLs were suspended because of remote path failure. (Volume number = xxx) [Event Name] Universal Replicator P-VOL suspending [Category] UniversalReplicator [Solution] Verify the remote path status both in the primary and secondary storage systems. Correct any problems as necessary. Verify the pair status of all the P-VOLs managed by the same storage controller as the displayed volume. Then, resynchronize the suspended pair. |
KARS06733-E |
One or more P-VOLs were suspended because of a failure or maintenance operation in the primary storage system of Universal Replicator. (Volume number = xxx) [Event Name] Universal Replicator P-VOL suspending [Category] UniversalReplicator [Solution] Verify the pair status of all the P-VOLs managed by the same storage controller as the displayed volume. Handle any error in the primary storage system as necessary. Then, resynchronize the suspended pair. If there is any pair whose status is PFUS, take action according to "Troubleshooting" in the VSP One SDS Block Universal Replicator Guide. |
KARS06734-E |
One or more P-VOLs were suspended because of a failure in the secondary storage system of Universal Replicator. (Volume number = xxx) [Event Name] Universal Replicator P-VOL suspending [Category] UniversalReplicator [Solution] Verify the pair status of all the P-VOLs managed by the same storage controller as the displayed volume. Handle the secondary storage system error. Then, resynchronize the suspended pair. |
KARS06735-W |
The P-VOL was suspended because suspending of the Universal Replicator S-VOL was detected. (Volume number = xxx) [Event Name] Universal Replicator P-VOL suspending [Category] UniversalReplicator [Solution] To resume remote copy, resynchronize the pair (paying attention to the copy direction). |
KARS06736-W |
One or more P-VOLs were suspended because pair deletion for an S-VOL of Universal Replicator was detected. (Volume number = xxx) [Event Name] Universal Replicator P-VOL suspending [Category] UniversalReplicator [Solution] Verify the pair status of all the P-VOLs managed by the same storage controller as the displayed volume. Delete any pair for which the P-VOL is PSUS and the S-VOL is SMPL. To resume remote copy, consider the copy direction, and then recreate the pair. |
KARS06737-E |
One or more Universal Replicator S-VOLs were suspended because of remote path failure. (Volume number = xxx) [Event Name] Universal Replicator S-VOL suspending [Category] UniversalReplicator [Solution] Verify the remote path status both in the primary and secondary storage systems. Correct any problems as necessary. Verify the pair status of all the S-VOLs managed by the same storage controller as the displayed volume. Then, resynchronize the suspended pair. If there is any pair whose status is SSWS, take action according to "Troubleshooting" in the VSP One SDS Block Universal Replicator Guide. |
KARS06738-E |
One or more S-VOLs were suspended because of a failure or maintenance operation in the secondary storage system of Universal Replicator. (Volume number = xxx) [Event Name] Universal Replicator S-VOL suspending [Category] UniversalReplicator [Solution] Verify the pair status of all the S-VOLs managed by the same storage controller as the displayed volume. If there is no pair whose status is PSUE or PFUS, no action is required. Handle any error in the secondary storage system as necessary. Then, resynchronize the suspended pair. If there is any pair whose status is PFUS, take action according to "Troubleshooting" in the VSP One SDS Block Universal Replicator Guide. |
KARS06739-W |
The S-VOL was suspended because the primary storage system of Universal Replicator was powered off. (Volume number = xxx) [Event Name] Universal Replicator S-VOL suspending [Category] UniversalReplicator [Solution] Power on the primary storage system. The Universal Replicator pair is automatically resynchronized. |
KARS06741-W |
Read-journal requests from the secondary site of Universal Replicator could not be accepted for one minute. (Storage controller ID = xxx) [Event Name] Universal Replicator communication disconnected [Category] UniversalReplicator [Solution] If this problem repeatedly occurs, verify the remote path status both in the primary and secondary storage systems. Correct any problems as necessary. |
KARS06742-E |
Read-journal requests from the secondary site of Universal Replicator could not be accepted for five minute. (Storage controller ID = xxx) [Event Name] Universal Replicator communication disconnected [Category] UniversalReplicator [Solution] Verify the remote path status both in the primary and secondary storage systems. Correct any problems as necessary. |
KARS06743-W |
Read-journal response from the primary site of Universal Replicator could not be accepted for one minute. (Storage controller ID = xxx) [Event Name] Universal Replicator communication disconnected [Category] UniversalReplicator [Solution] If this problem repeatedly occurs, verify the remote path status both in the primary and secondary storage systems. Correct any problems as necessary. |
KARS06744-E |
Read-journal response from the primary site of Universal Replicator could not be accepted for five minutes. (Storage controller ID = xxx) [Event Name] Universal Replicator communication disconnected [Category] UniversalReplicator [Solution] Verify the remote path status both in the primary and secondary storage systems. Correct any problems as necessary. |
KARS06745-W |
The consumed amount of the master journal metadata area exceeded the threshold. If update I/O inflow is restricted with the journal option, host I/O response for the P-VOL that uses this journal is degraded. (Journal number = xxx) [Event Name] Journal threshold exceeded [Category] Journal [Solution] If update I/O inflow restriction causes any problem in I/O response, split the pair. After that, resolve the cause of the journal bottleneck. Then, resynchronize the pair. If this problem repeatedly occurs, the pair status might become PFUS. Consider taking action for PFUS according to "Troubleshooting" in the VSP One SDS Block Universal Replicator Guide. |
KARS06746-W |
The consumed amount of the master journal data area exceeded the threshold. If update I/O inflow is restricted with the journal option, host I/O response for the P-VOL that uses this journal is degraded. (Journal number = xxx) [Event Name] Journal threshold exceeded [Category] Journal [Solution] If update I/O inflow restriction causes any problem in I/O response, split the pair. After that, resolve the cause of the journal bottleneck. Then, resynchronize the pair. If this problem repeatedly occurs, the pair status might become PFUS. Consider taking action for PFUS according to "Troubleshooting" in the VSP One SDS Block Universal Replicator Guide. |
KARS06747-W |
The consumed amount of the restore journal metadata area exceeded the threshold. (Journal number = xxx) [Event Name] Journal threshold exceeded [Category] Journal [Solution] If this problem repeatedly occurs, the pair status might become PFUS. Consider taking action for PFUS according to "Troubleshooting" in the VSP One SDS Block Universal Replicator Guide. |
KARS06748-W |
The consumed amount of the restore journal data area exceeded the threshold. (Journal number = xxx) [Event Name] Journal threshold exceeded [Category] Journal [Solution] If this problem repeatedly occurs, the pair status might become PFUS. Consider taking action for PFUS according to "Troubleshooting" in the VSP One SDS Block Universal Replicator Guide. |
KARS06780-E |
Automatic recovery of the status of the Universal Replicator pair in the storage controller did not succeed. (Storage controller ID = xxx) [Event Name] Request for automatic UR pair status recovery failed [Category] Volume [Solution] Verify the status of the Universal Replicator pair for which an S-VOL was created in the target storage controller, and then recover the status by pair operations. |
KARS06781-E |
Automatic recovery of the status of the Universal Replicator pair in the storage controller did not succeed. (Storage controller ID = xxx) [Event Name] Automatic UR pair status recovery failed [Category] Volume [Solution] Verify the status of the Universal Replicator pair for which an S-VOL was created in the target storage controller, and then recover the status by pair operations. |
KARS06900-E |
A failure occurred during storage pool expansion. [Event Name] Storage controller failure occurred during storage pool expansion [Category] StorageNode [Solution] If a storage node is blocked, perform maintenance recovery. Collect the logs, and then contact customer support. If no storage node is blocked, this event log can be ignored. |
KARS06901-E |
A failure occurred during volume creation. (Volume ID = xxx) [Event Name] Storage controller failure occurred during volume creation [Category] StorageNode [Solution] If a storage node is blocked, perform maintenance recovery and verify volume status. If a volume is created, delete it, and then create one again. If a volume is not created, create one. If the problem persists, collect the logs, and then contact customer support. If no storage node is blocked, this event log can be ignored. |
KARS06902-E |
A failure occurred during volume deletion. (Volume ID = xxx) [Event Name] Storage controller failure occurred during volume deletion [Category] StorageNode [Solution] If a storage node is blocked, perform maintenance recovery and verify volume status. If a volume remains, delete it. If the problem persists, collect the logs, and then contact customer support. If no storage node is blocked, this event log can be ignored. |
KARS06903-E |
A failure occurred during snapshot creation. (S-VOL ID = xxx) [Event Name] Storage controller failure occurred during snapshot creation [Category] StorageNode [Solution] If a storage node is blocked, perform maintenance recovery and verify snapshot status. If there is an unhealthy snapshot, delete the snapshot, delete it, and then create one again. If a snapshot is not created, create one. If the problem persists, collect the logs, and then contact customer support. If no storage node is blocked, this event log can be ignored. |
KARS06904-E |
A failure occurred during snapshot deletion. (S-VOL ID = xxx) [Event Name] Storage controller failure occurred during snapshot deletion [Category] StorageNode [Solution] If a storage node is blocked, perform maintenance recovery and verify snapshot status. If a snapshot remains, delete it. If the problem persists, collect the logs, and then contact customer support. If no storage node is blocked, this event log can be ignored. |
KARS06905-E |
A failure occurred during snapshot restore. (S-VOL ID = xxx) [Event Name] Storage controller failure occurred during snapshot restore [Category] StorageNode [Solution] If a storage node is blocked, perform maintenance recovery and verify snapshot status. If restore is not started, perform restore again. If the problem persists, collect the logs, and then contact customer support. If no storage node is blocked, this event log can be ignored. |
KARS06906-E |
A failure occurred during snapshot creation. (P-VOL ID = xxx) [Event Name] Storage controller failure occurred during snapshot creation [Category] StorageNode [Solution] If a storage node is blocked, perform maintenance recovery and verify snapshot status. If a snapshot is not created, create one. If the problem persists, collect the logs, and then contact customer support. If no storage node is blocked, this event log can be ignored. |
KARS06907-E |
A failure occurred during snapshot deletion. (P-VOL ID = xxx) [Event Name] Storage controller failure occurred during snapshot deletion [Category] StorageNode [Solution] If a storage node is blocked, perform maintenance recovery and verify snapshot status. If a snapshot remains, delete it. If the problem persists, collect the logs, and then contact customer support. If no storage node is blocked, this event log can be ignored. |
KARS06908-E |
A failure occurred during storage controller expansion. (Storage node ID = xxx) [Event Name] Storage controller failure occurred [Category] StorageNode [Solution] Do not perform maintenance recovery for the storage node indicated in this message. Collect the logs, and then contact customer support. |