How Do I Fix Error "Failed to start sms agent! 'disks'" When I Start the Agent on a Linux Source Server?
Symptom
When you started the Agent on a Linux source server, message "Failed to start sms agent!'disks'" was displayed.
Possible Causes
Possible causes are:
- Multiple volume groups are with the same name.
Check whether the SmsAgent_Error.log file records "Multiple VGs found with the same name".
SMS requires that a Linux source server cannot have volume groups with the same name, or the Agent will be unable to collect information about the source server disks. Run the vgdisplay command to check whether there are volume groups with the same name, and run the lvdisplay command to view logical volume properties, such as the host name and creation time.
- The fdisk command cannot be found on the source server.
Run the fdisk -l command on the source server to check whether the fdisk command exists in your path. If fdisk cannot be found, the possible cause is that the /sbin directory is not included in PATH, or the /sbin directory is included in PATH but does not take effect. This problem may occur after you run the su command to switch to the root user.
Solutions
- If there are volume groups with the same name in Linux, these volume groups and the corresponding logical volumes cannot be mounted or read.
You can detach the disks in the volume groups that fail to be mounted from the source server and attach them to another server. Then check whether the data in the disks needs to be migrated.
- If the data needs to be migrated, run the vgrename command to rename each of these volume groups, and attach the disks in these groups back to the source server. Then restart the SMS Agent.
- If the data does not need to be migrated, restart the SMS Agent. After the migration is complete, attach the disks back to the source server.
- Run the source /etc/profile command and restart the SMS Agent.
Agent Installation and Startup FAQs
- How Do I Download and 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 Configure Certificate Verification in the SMS-Agent Configuration File?
- 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 Error "The application cannot be started due to incorrect parallel configuration" When I Start the Agent?
- Why Does the Agent Not Start the First Time I Launch It?
- Why Does the Windows Agent Executable Not Run When I Double-Click It?
- How Do I Fix Error "INTERNAL ERROR: cannot create temporary directory!" When I Start the Agent?
- How Do I Troubleshoot Failures of Pasting the AK/SK Pair When I Start the Agent (Python 2)?
- 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 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 "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?
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.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore