Help Center>
Server Migration Service>
FAQs>
Known Errors and Solutions>
SMS.6562: Component i386-pc Not Found on Source Server For solution, see SMS API Reference
Updated on 2024-03-29 GMT+08:00
SMS.6562: Component i386-pc Not Found on Source Server For solution, see SMS API Reference
Symptom
When you started the Agent installed on a Linux source server, you received error message "SMS.6562: Component i386-pc not found on source server. For solution, see SMS API Reference."
Possible Causes
Huawei Cloud requires that component i386-pc be available on servers booted in BIOS mode for installing GRUB. The error message indicates that the source server is started in BIOS mode but does not have component i386-pc. In this case, during the target server configuration by the Agent, GRUB will fail to be installed. As a result, this error is reported during the configuration.
The i386-pc component is located is in the /usr/lib/grub/i386-pc directory.
Procedure
- Check whether the source server is booted to BIOS.
#[ -d /sys/firmware/efi ] && echo UEFI || echo BIOS
- If the output is bios, the server is booted to BIOS.
- If the output is uefi, the server is booted to UEFI.
- Check whether the i386-pc folder is in the /usr/lib/grub/ directory.
#ls /usr/lib/grub
- If the i386-pc folder is not there, go to step 3.
- If the i386-pc folder is there, check whether the i386-pc folder is empty.
#ls /usr/lib/grub/i386-pc
- On the source cloud platform or Huawei Cloud, use a public image to create a temporary server that runs the same OS as the source server.
- Log in to the temporary server and transfer the i386-pc folder in the /usr/lib/grub/ directory on the temporary server to the /usr/lib/grub/ directory on the source server. If there is an empty i386-pc folder on the source server, overwrite it.
You can use Secure Copy (SCP) or rsync to transfer the folder. The following command uses SCP as an example:
#scp -r /usr/lib/grub/i386-pc Username@xx.xx.xx.xx:/usr/lib/grub/
- Replace Username with the username of the source server.
- Replace xx.xx.xx.xx with the IP address of the source server.
- Modify the security group of the source server to allow access from the temporary server.
- Log in to the source server, check if the i386-pc folder is in the /usr/lib/grub/ directory, and restart the Agent.
Parent topic: Known Errors and Solutions
Known Errors and Solutions FAQs
- SMS.0202 AK/SK Authentication Failed. Ensure that the AK and SK Are Correct
- SMS.0203 Connection from Source Server to API Gateway Timed Out
- SMS.0204 Insufficient Permissions. Obtain the Required Fine-Grained Permissions
- SMS.0205 Incorrect System Time or Time Zone On Source Server
- SMS.0206 Only x86 Servers Can Be Migrated
- SMS.0210 Failed to Create File on Target Server
- SMS.0303 Unable to Access Domain Name
- SMS.0410 Failed to Obtain NIC Information
- SMS.0412 Target Server Does Not Exist
- SMS.0515 Migration Failed. Source Disk Information Has Changed. Delete Target Server Configuration and Restart the Agent
- SMS.0609 An Older Version of Agent Is Detected. Please Exit The Current Program, Uninstall the Old Agent Completely, and Install the Newest One
- SMS.0805 Failed to Migrate Partition to Target Server
- SMS.0806 Failed to Synchronize Partition to Target Server
- SMS.1105 Disk Creation Failed
- SMS.1106 Failed to Delete Disk XXX
- SMS.1204 Failed to Create File on Source Server
- SMS.1205 Failed to Load WMI
- SMS.1351: Mount Point /xxx Detected on the Source Server, Which Has No Free Space. Ensure that There Is at Least 1 MB of Space
- SMS.1352: Unknown Physical Volumes Detected on the Source Server
- SMS.1353: Bind Mount or Repeated Mount Detected on /xxx of the Source Server
- SMS.1402 SSH Client Not Installed
- SMS.1414 The Migration Module Stopped Abnormally and Cannot Synchronize Data
- SMS.1807 Failed to Connect to the Target Server. Check Whether Its IP Address Is Reachable and Confirm that Port 8900 Is Enabled
- SMS.1901 Agent Could Not Read Disk Information
- SMS.1902 Failed to Start the I/O Monitoring Module
- SMS.1904 Failed to Create a Snapshot for the Windows Server
- SMS.2802 Failed to Connect to the Target Server. Check Whether Its IP Address Is Reachable and Port 8899 Is Enabled
- SMS.3205 Failed to Mount Partition XXX to Directory XXX
- SMS.3802 Failed to Establish an SSH Connection with the Target Server
- SMS.5102 Agent Startup Failed Because the noexec Permission Is Unavailable on /tmp in Linux
- SMS.5105 Agent Startup Failed. Insufficient Permissions to Add Files to or Delete Files from xxx
- SMS.5108 Failed to Execute df -TH
- SMS.6303 The Installed Agent Is of an Earlier Version. Download the Latest Version
- SMS.6509 Incompatible File System of the Source Server
- SMS.6511 The Source Server Lacks Driver Files
- SMS.6517 rsync Not Installed on the Source Server
- SMS.6528 Complete Real-name Authentication to Invoke SMS APIs
- SMS.6533 VSS Not Installed on the Source Server
- SMS.6537 SMS Cannot Migrate System Disks Larger Than 1 TB
- SMS.6562: Component i386-pc Not Found on Source Server For solution, see SMS API Reference
- SMS.6563: File initrd or initramfs of the xxxx version Not Found Under /boot Directory For solution, see SMS API Reference
- SMS.6616 The Current OS Does Not Support Block-level Migration/SMS.6617 The Current Kernel Version Does Not Support Block-level Migration
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
