Message ID |
Message |
|---|---|
KARS07000-I |
The data rebuild has started. (Request ID = xxx, Drive ID = xxx, Rebuild type = xxx) [Event Name] The data rebuild start [Category] Drive |
KARS07001-I |
The data rebuild is complete. (Request ID = xxx, Drive ID = xxx) [Event Name] The data rebuild complete [Category] Drive |
KARS07002-I |
The data rebuild was aborted. (Request ID = xxx) [Event Name] The data rebuild abort [Category] Drive [Solution] Wait until the data rebuild restarts. When some functions such as storage node maintenance recovery are running, the data rebuild restarts after they complete. If the data rebuild does not restart or the same event log is repeatedly output, verify whether other event logs that require troubleshooting are output, and then take action. |
KARS07003-I |
The data rebuild progress is xxx %. Approximate time remaining is xxx hours and xxx minutes. [Event Name] The data rebuild progress [Category] Drive |
KARS07004-E |
An internal processing error occurred during data rebuild. (Request ID = xxx) [Event Name] The data rebuild failed (Internal error) [Category] Drive [Solution] An error occurred when rebuilding the drive data. Operation continues in the rebuildable area. Wait until the rebuild is completed. |
KARS07005-E |
Free drive space is insufficient to rebuild the drive data. The data rebuild is not performed for the insufficient drive space. (Request ID = xxx, Required capacity = xxx GiB, Storage node ID = xxx) [Event Name] Free drive space insufficient to rebuild the drive data [Category] Drive [Solution] Refer to the message, and then add new drives to the target storage node. Note: If drives and storage nodes on which the drives exist are both blocked, insufficient free capacity might be temporary. If the conditions are met, wait until Rebuild completes. If event log KARS07001-I is output and Rebuild completes, insufficient free capacity has been resolved. If event log KARS07001-I was not output and Rebuild is no longer in progress, add new drives. |
KARS07006-E |
The request could not be executed. [Cause] The status of the target resource or associated resources do not satisfy the operation prerequisites. [Solution] Verify the status of the target resource and associated resources. If Data rebuild is being performed, wait until the processing completes. After that, retry any operations that have been performed. |
KARS07007-E |
The user data in the drive is not redundant. (Job ID = xxx) [Event Name] Storage node maintenance failed (User data redundancy pre-check) [Category] StorageCluster |
KARS07008-E |
The user data in the drive mounted on the storage node is not redundant. (Job ID = xxx, Storage node ID = xxx) [Event Name] Storage cluster maintenance failed (User data redundancy pre-check) [Category] StorageNode |
KARS07009-E |
The request could not be executed. [Cause] No more drives can be added to the storage pool because the maximum physical capacity per storage node that can be registered in a storage pool has been reached. [Solution] Verify the physical capacity of the storage node in which the target drive is installed. |
KARS07010-I |
Drive data relocation has started. (Storage node ID = xxx) [Event Name] Drive data relocation start [Category] Drive |
KARS07011-I |
Drive data relocation is complete. (Storage node ID = xxx) [Event Name] Drive data relocation complete [Category] Drive |
KARS07012-I |
Drive data relocation was aborted. (Storage node ID = xxx) [Event Name] Drive data relocation abort [Category] Drive [Solution] Wait until the drive data relocation restarts. If the drive data relocation is suspended due to interrupt by other functions, the drive data relocation restarts after they complete. If the drive data relocation does not restart or the same event log is repeatedly output, verify whether other event logs that require troubleshooting are output, and then take action. |
KARS07013-I |
Drive data relocation was manually aborted. (Request ID = xxx, Storage node ID = xxx) [Event Name] Drive data relocation manual abort [Category] Drive |
KARS07014-I |
The drive data relocation progress is xxx %. (Request ID = xxx, Storage node ID = xxx) [Event Name] Drive data relocation progress [Category] Drive |
KARS07015-E |
An internal processing error occurred during drive data relocation. [Event Name] Drive data relocation failed (Internal error) [Category] Drive [Solution] Wait until drive data relocation restarts. If drive data relocation does not restart within 5 minutes and an event log indicating another error is output, take action referring to the event log. If drive data relocation does not restart or the same event log is repeatedly output, collect the logs, and then contact customer support. |
KARS07016-E |
The requested operation could not be executed because drive data relocation is in progress. (Job ID = xxx) [Event Name] Failure to verify a user requested operation [Category] Drive [Solution] Retry the operation after drive data relocation is complete or drive data relocation has been aborted manually. |
KARS07017-E |
The request could not be executed. [Cause] An unexpected error occurred. [Solution] Collect the logs, and then contact customer support. |
KARS07018-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 execute the operation again. If the error occurs again, collect the logs, and then contact customer support. |
KARS07019-I |
Drive data relocation was aborted by another operation. (Storage node ID = xxx) [Event Name] Drive data relocation aborted. [Category] Drive [Solution] When adding a storage node, expand the pool after addition of the storage node has completed. Do not perform any other operations until this process has completed. |
KARS07020-E |
Drive data relocation was aborted because an error occurred. (Storage node ID = xxx) [Event Name] Drive data relocation aborted. [Category] Drive [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. |
KARS07021-E |
Drive data relocation was aborted because a database access error occurred. (Storage node ID = xxx) [Event Name] Drive data relocation aborted. [Category] Drive [Solution] Wait until the drive data relocation restarts. If the drive data relocation does not start within 30 minutes or the same event log is repeatedly output, verify whether other event logs that require troubleshooting are output, and then take action. If the problem persists, collect the logs, and then contact customer support. |
KARS07100-E |
Failed to complete the data rebuild because the storage node is blocked. (Request ID = xxx, Storage node ID = xxx) [Event Name] The data rebuild failed (Blockade StorageNode) [Category] StorageNode [Solution] Restore the blocked storage node. |
KARS07101-E |
The data rebuild was aborted because a database access error occurred. (Request ID = xxx) [Event Name] The data rebuild aborted. [Category] Drive [Solution] Wait until the data rebuild restarts. If the data rebuild does not start within 30 minutes or the same event log is repeatedly output, verify whether other event logs that require troubleshooting are output, and then take action. If the problem persists, collect the logs, and then contact customer support. |
KARS07102-I |
The data rebuild type was changed to normal mode. (Request ID = xxx) [Event Name] The data rebuild type changed [Category] Drive |
KARS07150-E |
The storage node cannot be removed because there is a request of drive data relocation from another job. (Job ID = xxx) [Event Name] Storage node removal pre-check. (Drive data relocation cannot be performed) [Category] StorageNode [Cause] Duplicate drive data request [Solution] Wait until drive data relocation is completed, and then remove storage nodes again. If drive data relocation is suspended, restart drive data relocation and wait until it is completed. |
KARS07151-E |
The request could not be executed. [Cause] The specified Protection domain ID is not correct. [Solution] Set the parameter correctly, and then retry the operation. |
KARS07200-E |
The request could not be executed. [Cause] An internal processing error occurred. [Solution] Verify the status of the target resource or associated resources, and then correct any problems. After that, retry any operations that have been performed. If the same error occurs repeatedly, collect the logs, and then contact customer support. |
KARS07250-I |
Drive replacement has been started. (Job ID = xxx) [Event Name] Drive replacement started [Category] Drive |
KARS07252-I |
The drive to be replaced was successfully removed. (Job ID = xxx, Drive ID = xxx) [Event Name] Drive to be replaced was successfully removed [Category] Drive |
KARS07253-I |
Drive replacement has been completed. (Job ID = xxx) [Event Name] Drive replacement completed [Category] Drive |
KARS07254-E |
Drive replacement did not succeed. (Job ID = xxx) [Event Name] Drive replacement unsuccessful [Category] Drive [Solution] See the error details with the job ID described in the message, and then take action. |
KARS07260-E |
Drive replacement did not succeed. [Solution] Wait a while and execute the operation again. If the error occurs again, collect the logs, and then contact customer support. |
KARS07261-C |
Drive replacement did not succeed. [Solution] Collect the logs, and then contact customer support. |
KARS07262-E |
Drive replacement did not succeed. [Cause] The drive to be replaced is not specified. [Solution] Specify a drive to be replaced, and then retry the request. |
KARS07263-E |
Drive replacement did not succeed. [Cause] The replacement drive is not specified. [Solution] Specify a replacement drive, and then retry the request. |
KARS07264-E |
Drive replacement did not succeed. [Cause] The drive to be replaced cannot be found. [Solution] Verify the parameter settings, and then retry the request. |
KARS07265-E |
Drive replacement did not succeed. [Cause] The replacement drive cannot be found. [Solution] Verify the parameter settings, and then retry the request. |
KARS07266-W |
Drive replacement has been completed. [Cause] The drive specified to be replaced does not need replacement. The specified drive is in Offline state. [Solution] Specify a drive whose status is Blockage for a drive to be replaced. |
KARS07267-E |
Drive replacement did not succeed. [Cause] A drive which cannot be specified for a replacement drive was specified. [Solution] Verify that the status of the specified drive is Normal. Verify the parameter settings, and then retry the request. |
KARS07268-E |
Drive replacement did not succeed. [Cause] The replacement drive has insufficient capacity. [Solution] Specify a drive whose capacity is at least that of the drive to be replaced. |
KARS07270-E |
Drive replacement did not succeed. [Cause] The drive to be replaced could not be removed. [Solution] See the event logs indicating other errors, if any, and then take action. If an event log indicating another error is not output, wait a while, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS07271-E |
Drive replacement did not succeed. [Cause] The storage cluster was not started in maintenance mode. [Solution] The storage cluster must be started in maintenance mode. Start the storage cluster in maintenance mode, and then retry the operation. |
KARS07280-E |
Data could not be formatted. [Solution] Wait a while and execute the operation again. If the error occurs again, collect the logs, and then contact customer support. |
KARS07281-C |
Data could not be formatted. [Solution] Collect the logs, and then contact customer support. |
KARS07282-E |
Data could not be formatted. [Cause] The storage cluster was not started in maintenance mode. [Solution] The storage cluster must be started in maintenance mode. Start the storage cluster in maintenance mode, and then retry the operation. |
KARS07290-C |
A drive failure occurred in the absence of data redundancy. [Event Name] Blockage exceeding data redundancy occurred due to drive failure [Category] Drive |
KARS07291-C |
A storage node failure occurred in the absence of data redundancy. [Event Name] Blockage exceeding data redundancy occurred due to storage node failure [Category] StorageNode |
KARS07300-E |
The drive was blocked. (Storage node ID = xxx, Drive ID = xxx) [Event Name] Drive blockage due to an internal error [Category] StorageNode [Solution] Collect the logs, and then contact customer support. |
KARS07301-C |
The storage cluster is being blocked because a communication error occurred in the internode network. (Storage node ID = xxx) [Event Name] Storage cluster blocking due to an internode network communication error [Category] StorageNode |