When an SMC migration job fails with the S9_* Disk partition header data synchronization error, the SMC client cannot sync block-level data for a disk partition header. This topic covers the causes and solutions.
Symptom
An SMC migration job fails with S9_* Disk partition header data synchronization error. Possible error codes:
-
S9_F4 -
S9_F40
Causes
The SMC client on the source server fails to sync block-level data for the disk partition header. The cause depends on the error code:
-
S9_F4: Network connection interrupted during block-level data sync from the source server. -
S9_F40: Source server cannot connect to the destination instance on TCP port 8703.
Solutions
Apply the fix for your error code:
-
S9_F4Ensure the network connection from the source server to the destination instance on TCP port 8703 stays stable during migration, then retry the job.
-
S9_F40Verify that the source server can access the destination instance over TCP port 8703.
-
Check the security group rules of the destination instance. Ensure inbound traffic on port 8703 is allowed and not blocked by conflicting rules.
NoteBy default, an SMC migration job automatically associates a temporary security group with the destination instance that allows inbound traffic on port 8703.
-
Check local network configuration and intermediate devices (firewalls, proxy servers). Ensure outbound rules do not block access to the destination IP address and port 8703.
-
After you resolve the network issue, run the SMC client to retry the operation. For more information, see Run the SMC client.