Server Migration Center:What do I do if I receive an S3 error code indicating an error in the data synchronization of disk partitions?

Symptom

During an SMC migration, the migration job fails with the error "S3_* An error occurred in the data synchronization of the disk partition." The S3_* placeholder can be any of the following error codes:

• S3_F30

• S3_F32

• S3_F6

• S3_F4

• S3_F40

• S3_F70

Causes

These errors occur when the SMC client on the source server fails to synchronize disk partition data at the block level. The possible causes are as follows:

• S3_F30, S3_F32, S3_F6: SMC failed to read disk partition data on the source server.

• S3_F4: The network connection was interrupted during block-level data synchronization of the source disk partition.

• S3_F40: The source server cannot reach port 8703 on the destination instance.

• S3_F70: Block-level data synchronization of the source disk partition stalled, which caused the migration job to time out.

Solutions

Apply the solution that corresponds to the error code you received:

• S3_F30, S3_F32, S3_F6

  During block-level replication, the SMC client automatically creates a snapshot device for each disk partition on the source server to synchronize data. If this device is disabled or malfunctions, these errors can occur. To check the device and resolve the issue, see Error S6: Failed to create partition snapshot.

• S3_F4

  Check whether the network connection between the source server and the destination instance over port 8703 is stable. Do not interrupt the network during migration, and retry the job after the network recovers.

• S3_F40

  Check whether the source server can access port 8703 on the destination instance.

  1. Check whether the security group of the destination instance allows inbound traffic on port 8703, and whether any other security group rule causes a conflict that blocks this port.

     Note

     By default, an SMC migration job automatically associates a temporary security group with the destination instance to allow inbound traffic on port 8703.

  2. Check your local network configuration and any intermediate network devices, such as firewalls or proxies, for outbound IP address or port access restrictions.

  3. Check whether Cloud Firewall is blocking the connection by reviewing access control policies for the internet firewall and VPC firewall. Firewall settings.

• S3_F70

  Check whether the network connection between the source server and the destination instance over port 8703 is stable, and whether the bandwidth of the source server is sufficient. Insufficient bandwidth slows the transfer and can cause the migration job to time out.

After you resolve the network issue, run the SMC client to retry the migration. For more information, see Run the SMC client.