Help Center/ Server Migration Service/ User Guide (Kuala Lumpur Region)/ FAQs/ Disk Management/ Why Can't I Attach the Original System Disk Back to a Target Server?

Updated on 2024-03-15 GMT+08:00

View PDF

Why Can't I Attach the Original System Disk Back to a Target Server?

Symptom

If a migration fails, the system disk of the target server is a temporary disk with the disk name starting with sms. As a result, the original system disk of the target server cannot be attached back.

Possible Causes

The temporary system disk was not detached. You need to manually detach the temporary disk.

Procedure

The following uses Linux as an example to describe how to handle this problem.

Connect the source server to SMS by switching to the SMS-Agent directory on the source server, running ./agent-cli, entering connect, and pressing Enter.
Run clear in the CLI.
After about a minute, the temporary disk on the target server will be detached and deleted, and the original system disk will be re-attached.

Parent topic: Disk Management

Previous topic: Why Was a 40 GB EVS Disk Added to the Target Server During the Migration?

Next topic: How Do I Resolve Error "Disk info in source server has changed, task fail, please delete the task and then restart the agent"?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank 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.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.