The error message S5_* An error occurred in the configurations of the destination disk partition. during an SMC migration job points to a GRUB bootloader issue on the source server or a network connectivity failure to the destination instance.
The following table lists the error codes covered in this topic:
| Error code | Cause |
|---|---|
| S5_204 | Invalid GRUB 2 configuration |
| S5_205 | GRUB 2 installation failure |
| S5_206 | GRUB Legacy installation failure |
| S5_207 | Unsupported GRUB version |
| S5_U28, S5_U7, S5_U56, S5_U6 | Network connectivity failure to the intermediate service on port 8080 |
Identify your GRUB version
For error codes S5_204, S5_205, S5_206, and S5_207, check the GRUB version on the source server:
grub-install --version
If grub-install is not found, try:
grub2-install --version
-
0.97 = GRUB Legacy
-
2.x = GRUB 2
Match your version to the corresponding resolution below.
S5_206: GRUB Legacy installation failure
Cause: The SMC client failed to install GRUB Legacy (version 0.97) on the destination disk.
Resolution:
-
Install GRUB 2.12 or later on the source Linux server. For instructions, see Install GRUB in a Linux server.
-
After the installation completes, re-run the migration from the SMC client installation directory: For details on locating the SMC client, see the View and run the SMC client section.
./go2aliyun_client --rerun --forcesync
If the issue persists after upgrading GRUB, contact technical support.
S5_207: Unsupported GRUB version
Cause: The GRUB version on the source server is not supported for migration.
Resolution:
-
Install GRUB 2.12 or later on the source Linux server. For instructions, see Install GRUB in a Linux server.
-
After the installation completes, re-run the migration from the SMC client installation directory: For details on locating the SMC client, see the View and run the SMC client section.
./go2aliyun_client --rerun --forcesync
If the issue persists after upgrading GRUB, contact technical support.
S5_204: Invalid GRUB 2 configuration
Cause: The GRUB 2 configuration generated during migration is invalid.
Resolution:
Before contacting support, collect the following diagnostic information:
-
Check the GRUB configuration file on the source server. The file is typically located at:
-
/boot/grub2/grub.cfg(RHEL, CentOS, Fedora) -
/boot/grub/grub.cfg(Ubuntu, Debian)
-
-
Check the SMC client migration log for detailed error output.
-
Contact technical support and provide the GRUB configuration file contents and the migration log.
S5_205: GRUB 2 installation failure
Cause: The SMC client failed to install GRUB 2 on the destination disk.
Resolution:
Before contacting support, collect the following diagnostic information:
-
Verify that GRUB 2 is installed on the source server:
grub-install --versiongrub2-install --version -
Check the SMC client migration log for detailed error output.
-
Contact technical support and provide the GRUB version, the migration log, and the source server OS version.
S5_U28, S5_U7, S5_U56, S5_U6: Intermediate service connectivity failure
Cause: The source server cannot communicate with the intermediate service on the destination instance over port 8080. Possible reasons:
-
An exception occurred on port 8080 of the intermediate service on the destination instance.
-
The source server cannot reach the IP address of the destination instance on port 8080.
Resolution:
For detailed troubleshooting steps, see Resolve S11 error codes for intermediate service network connection errors.
After you resolve the network issue, run the SMC client to retry the migration. For more information, see Run the SMC client.