When a Server Migration Center (SMC) migration job fails with the error "S4_* Failed to initialize destination disk partition", the SMC client on the source server cannot initialize partitions on the destination disk. This error may be caused by insufficient disk space or a connection issue with the intermediate service.
Symptoms
An SMC migration job fails with the error "S4_* Failed to initialize destination disk partition". The asterisk (*) represents one of the following error codes:
-
S4_105 -
S4_U28,S4_U7,S4_U56, andS4_U6
Causes
The cause depends on the error code:
-
S4_105: The destination disk does not have enough space for the partitions specified in the migration job. -
S4_U28,S4_U7,S4_U56, andS4_U6-
The intermediate service on the destination instance is not running correctly on port 8080.
-
The source server cannot connect to the destination instance over port 8080.
-
Solutions
The solution depends on the error code.
-
S4_105The total size of the new partitions, plus an additional 1 MB for the disk partition header, exceeds the specified size of the destination disk. Use one of the following methods to resolve this issue:
-
Method 1: Expand the destination disk by 1 GB and then retry the migration job.
-
Method 2: Re-create the migration job, increase the destination disk size by 1 GB, and then retry the job.
-
-
S4_U28,S4_U7,S4_U56, andS4_U6For more information, see S11 error: Failed to connect to the intermediate service on the destination instance.
After you resolve the network issue, run the SMC client to retry the operation. For more information, see Run the SMC client.