- FAQs
- Agent Installation and Startup
- How Do I Install the Agent on Source Servers?
- What Can I Do If I Fail to Download the Agent Installation File?
- How Do I Verify the Integrity of the Agent Installation File?
- Why Wasn't My Source Server Added to the SMS Console After I Configured the Agent?
- How Do I Find and Modify the Agent Configuration Files?
- Where Can I Find the Agent Run Logs?
- Why Is My Target Server Locked During the Migration?
- How Do I Unlock a Target Server Manually?
- How Do I Resolve the "No such file or directory: 'rsync':'rsync" Error When I Start the Linux Agent?
- How Do I Fix Error "Failed to start the I/O monitoring module" When I Start the Agent?
- How Do I Fix Error "INTERNAL ERROR: cannot create temporary directory!" When I Start the Agent?
- How Do I Resolve Error "AK/SK authentication failed. Ensure that the system time is consistent with the standard time and the AK and SK are correct" When I Start the Agent?
- How Do I Resolve Error "utf-8 codec can't decode byte 0xce in position0: invalid continuation byte" When I Start the Agent?
- How Do I Fix the Agent Startup Failures Due to Agent Files Write or Read Failures?
- How Do I Restart the Agent?
- How Do I Fix Agent Startup Failures Due to Insufficient Space in /tmp on a Linux Source Server?
- How Do I Fix Error "Agent startup failed because the noexec permission is not allowed on /tmp for SMS Agent. Please remount /tmp without noexec" When I Start the Linux Agent?
- How Do I Resolve Error "Only servers with x86 architecture can be migrated"?
- How Do I Fix Error "Failed to start sms agent! 'disks'" When I Start the Agent on a Linux Source Server?
- How Do I Fix Error "Failed to obtain information about disk X" When I Start the Agent on a Linux Source Server?
- How Do I Choose When the System Asks Whether to Disable the Google Services Detected on My Source Server on the Google Cloud?
- How Do I Fix Error "SMS.0410: Failed to obtain NicName/IPAddress information of source server " When I Start the Agent on a Linux Server?
- What Do I Do If the SMS-Agent Fails to Start and Error "SMS.0609 An earlier version of Agent is detected. Please exit the old Agent, uninstall the old Agent completely, and install the latest version" Is Displayed?
- How Do I Fix Error "SMS.5103: Agent startup failed." When I Fail to Start the Agent on a Linux Source Server? Folder /tmp is missing
- How Do I Fix Error "SMS.1353: Bind mount or repeated mount detected on /xxx of the source server" When I Fail to Start the Agent on a Linux Source Server?
- How Do I Fix Error "SMS.1352: Unknown physical volumes detected on the source server" When I Fail to Start the Agent on a Linux Source Server?
- How Do I Fix Error "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" When I Fail to Start the Agent on a Linux Source Server?
- Change History
How Do I Resolve Error "Only servers with x86 architecture can be migrated"?
Symptom
When you started the Agent, you got the message "Only servers with x86 architecture can be migrated."
Possible Causes
SMS can only migrate x86 servers.
Parent topic: Agent Installation and Startup
Была ли эта статья полезна?
- Symptom
- Possible Causes