Call the ReInitializeVolume interface to reinitialize the volume.

Usage instructions

After reinitializing the volume, the volume ID remains unchanged. Different creation methods of volumes result in different initial states after reinitialization, as detailed below:

Volume created by snapshot: After reinitialization, it will be restored to the snapshot state when the volume was created, and the data generated after the volume creation was successful will be cleared.

Volume not created by snapshot: After reinitialization, all volume data is cleared.

It is recommended that you create a snapshot to back up the volume data before reinitializing the volume.

Reinitialization is supported only for data disks, see Reinitializing volume for more information.

Debugging

API Explorer

You can initiate calls online through API Explorer without paying attention to the signature generation process and quickly obtain the call results.

Go to debug

request parameters

Only the request parameters specific to this API and some common parameters are listed below. For more information, see common parameters.

Action string required Example: ReInitializeVolume

Operation to perform: ReInitializeVolume.

Version string required Example value: 2020-04-01

The version of the API is: 2020-04-01.

VolumeId string required Example: vol-3vi4xtz7r142xlz6****

Initialized volume ID.

Response Parameters

This API does not have specific response parameters. For more information, see response structure.

Request example

Back to example

error code

The table below lists error codes related to the business logic of this API. For public error codes, please refer to the Public Error Codes documentation.

Status code	error code	error message	Create Volume
400	VolumeInCreatingSnapshot	The operation is not permitted due to the volume is creating a snapshot.	The specified volume has snapshots being created.
400	MissingVolumeID	The specified parameter VolumeId is missing.	Volume ID is missing.
400	IncorrectSnapshotStatus	The specified snapshot status is invalid.	The specified snapshot status is invalid.
400	SnapshotStatusNotAvailable	Current snapshot state does not support volume reinitialization.	The snapshot status of the volume pending initialization does not support volume initialization.
403	IncorrectInstanceStatus	The rollback condition is not permitted due to the instance which volume attached must be in stopped status.	The current instance is not in a stopped state and cannot perform a reinitialization operation.
403	OperationDenied.InstanceIsCreatingImage	The operation is not permitted due to the instance is creating an image.	The current instance is creating an image and cannot perform a reinitialization operation.
403	OperationDenied.InstanceIsSnapshotRollback	The operation is not permitted due to the instance is locked by snapshot rollback or volume reInitialization.	The volume mounted by the current instance is performing a snapshot rollback or volume initialization and cannot perform a reinitialization operation.
404	VolumeNotFound	The specified volume does not exist.	Volume does not exist.
404	SnapshotNotFound	The specified snapshot does not exist.	The specified snapshot does not exist.
412	VolumeStatusForbidReInitialize	volume status forbid reInitialize.	The current volume state does not support performing reinitialization operations.
412	SystemVolumeForbidReInitialize	system volume currently does not support reInitialize.	The system disk does not support performing reinitialization operations.
412	SnapshotTaskExceedLimit	Exceeded the limit on the number of ongoing snapshot tasks.	Exceeded the limit number of snapshot tasks in progress.

Elastic Compute Service