SMS.3102 Failed to Modify the initrd File on the Target Server

Symptom

When the migration task reached the Modify Linux configurations subtask, the error message "SMS.3102: Failed to modify the initrd file on the target server" was displayed on the SMS console.

Possible Causes

The SMS-Agent may fail to modify the initrd file on the target server due to any of the following reasons:

• Cause 1: The source server uses a custom kernel. It prevents the SMS-Agent from generating or updating the initrd or initramfs image file. As a result, the native KVM drivers required for booting the target server cannot be injected into the kernel.
• Cause 2: The target server is stopped or frozen.
• Cause 3: The network latency fluctuates greatly between the source server and the target server. As a result, the SMS-Agent fails to obtain data due to timeouts.

Solutions

• For possible cause 1:

  Manually generate the initrd or initramfs image file that matches the kernel on the source server. For details, see Installing Native KVM Drivers on a KVM ECS. Note that this risky operation may affect the source server OS.

  If you are worried about the impact of this method on the source server, you are advised to use Cloud Migration Service from Huawei Cloud. It provides professional migration solutions and dedicated tools.

• For possible cause 2:

  Access the ECS list and check the status of the target server.

  • If the ECS is stopped, choose More > Start in the Operation column. Then retry the migration task.
  • If the ECS is frozen, unfreeze the ECS and retry the migration task.
• For possible cause 3:

  Use SSH or Telnet to test the network connectivity between the source and target servers. If the connection fails, check the network and firewall settings.

  The commands are in the following format:

  • telnet <target-server-IP-address> <port>
  • ssh <target-server-IP-address> <port>
  For example, if the target server's IP address is 192.168.0.x and port 22 is used, run either of the following commands:

  telnet 192.168.0.x 22

  ssh 192.168.0.x 22