Server migration error message Client.SystemConfigure.BootNotFound

Updated at:

The "Client.SystemConfigure.BootNotFound" error occurs during an SMC migration task when the boot directory on the source system is missing or corrupted.

Problem description

During SMC migration, the migration task displays the error message "Client.SystemConfigure.BootNotFound".

Causes

The target disk system configuration is incorrect and the boot directory cannot be found. Possible causes:

  • The boot directory and critical files in the directory are missing from the source system.

  • The file system is corrupted.

Solutions

  • Check whether the boot directory in the source system is intact:

    1. Run ls /boot to check whether the boot directory exists.

    2. Run ls /boot/initr* and ls /boot/vmlinu* to check whether the initramfs and vmlinuz files exist in the boot directory.

      If the boot directory does not exist or does not contain the initramfs and vmlinuz files, the critical files in the source system are abnormal. Rebuild the boot directory, initramfs file, and vmlinuz file. Then, run the ./go2aliyun_client --rerun --forcesync command in the SMC client installation directory to retry.

  • If the issue persists, collect the /smc/go2aliyun_client*/Logs logs and contact us.