Messages KARS04000-KARS04999

Virtual Storage Platform One SDS Block Message Reference

Version
1.14.x
Audience
anonymous
Part Number
MK-24VSP1SDS007-01

Message ID

Message

KARS04100-E

The request could not be executed.

[Cause]

An invalid storage node ID was specified.

[Solution]

Verify the specified storage node ID, and then retry the operation.

KARS04101-E

Data migration processing ended abnormally.

[Cause]

A failure occurred.

[Solution]

See the event log with the job ID of this job, and then take action. After that, retry the data migration.

KARS04102-E

The volume could not be registered.

[Cause]

The volume ID is not specified.

[Solution]

Specify the volume ID.

KARS04103-E

The volume could not be registered.

[Cause]

An error occurred while accessing the database.

[Solution]

Wait a while, and then retry the operation. If the error occurs again, collect the logs, and then contact customer support.

KARS04104-E

The volume could not be registered.

[Cause]

An unexpected error occurred.

[Solution]

Wait a while, and then retry the operation. If the error occurs again, collect the logs, and then contact customer support.

KARS04200-E

Processing xxx could not be performed because external volumes exist. (Job ID = xxx)

[Event Name]

Precheck for running external volumes

[Category]

Migration

[Solution]

Wait until external volume migration completes, and then retry the operation.

KARS04201-E

An invalid storage node was specified. (Storage node ID = xxx, Job ID = xxx)

[Event Name]

Data migration pre-check

[Category]

Migration

[Solution]

Verify the specified storage node ID, and then retry the operation.

KARS04202-E

Data migration could not be performed because the specified storage node status is not ready. (Storage node ID = xxx, Job ID = xxx)

[Event Name]

Data migration pre-check (Node status)

[Category]

Migration

[Solution]

Recover the specified storage node, and then retry the operation.

KARS04203-E

Data migration could not be performed because the specified storage node has no FC port. (Storage node ID = xxx, Job ID = xxx)

[Event Name]

Data migration pre-check (Port protocol)

[Category]

Migration

[Solution]

Specify a storage node that has an FC port, and then retry the operation.

KARS04204-E

The processing cannot be performed because the specified storage node is not an initiator node. (Storage node ID = xxx, Job ID = xxx)

[Event Name]

Data migration pre-check (Storage node attribute)

[Category]

Migration

[Solution]

Specify the initiator node, and then retry the operation.

KARS04205-E

Processing cannot be performed because the specified storage node has no volume for migration. (Storage node ID = xxx, Job ID = xxx)

[Event Name]

No migratable volumes

[Category]

Migration

[Solution]

Confirm that the correct storage node is specified, and then retry the operation.

KARS04206-E

Data migration could not be performed due to storage pool capacity shortage. (Total capacity of volumes data migration unsuccessful = xxxGiB, Job ID = xxx)

[Event Name]

Data could not be migrated due to storage pool capacity shortage

[Category]

Migration

[Solution]

Add drives to expand the storage pool. Or, delete volumes to increase free space, and then retry the operation.

KARS04207-E

Data migration could not be performed because the maximum number of volumes that can be created has been reached. (Total volume number = xxx, Exceed volume number of possible creation = xxx, Job ID = xxx)

[Event Name]

Limit of the number of volumes

[Category]

Migration

[Solution]

Delete volumes, and then retry the operation.

KARS04208-E

An unexpected error occurred. (Job ID = xxx)

[Event Name]

An internal error occurred

[Category]

Migration

[Solution]

Collect the logs, and then contact customer support.

KARS04209-E

The database could not be accessed during data migration. (Job ID = xxx)

[Event Name]

The database could not be accessed

[Category]

Migration

[Solution]

Wait a while, and then retry the operation. When the same error occurs, collect the logs, and then contact customer support.

KARS04210-I

Rebuilding of the drive overrode and aborted data migration. (Job ID = xxx)

[Event Name]

Volume migration canceled

[Category]

Migration

[Solution]

Wait until the drive is rebuilt, and then retry the operation. Or, if any event log indicates cancellation of drive rebuild, complete the drive rebuild according to the event log, and then retry the operation.

KARS04211-E

Data 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.

KARS04212-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.

KARS04213-E

The processing could not be performed because the specified storage node has no external volume path. (Storage node ID = xxx, Job ID = xxx)

[Event Name]

No external volume path

[Category]

Migration

[Solution]

Confirm that the correct storage node is specified, and then retry the operation.

KARS04214-E

Memory capacity is insufficient. (Job ID = xxx)

[Event Name]

Memory allocation could not be performed

[Category]

Migration

[Solution]

Restart the storage cluster, and then retry the operation. If the phenomenon does not change, collect the logs, and then contact customer support.

KARS04215-E

Processing xxx could not be performed because the external volume data migration destination storage node was specified. (Job ID = xxx)

[Event Name]

Precheck for running external volumes

[Category]

Migration

[Solution]

Wait until external volume migration completes, and then retry the operation.

KARS04216-E

Data migration was canceled. (Job ID = xxx)

[Event Name]

Data migration cancellation

[Category]

Migration

[Solution]

Data migration was canceled because a failure was detected. See other event logs and confirm the cause of the failure. If the data migration is not completed, retry the data migration.