Problem
This article describes the steps on how to resolve a specific issue that causes an OS boot timeout error on Linux systems. This issue is applicable to BIOS origins synced to UEFI targets in the following cases:
- Redhat/Oracle Linux when using RMM version 7.4.0.370 and earlier
OR
- CentOS when using RMM version 7.4.0.371 and later
In the above cases, the target can end up with a grub2-efi-x64 package that doesn't match the OS. If the grub2-efi-x64 package is updated using the system package manager, the grub configuration can end up in an unbootable state. A subsequent reboot of the target machine will likely end up in the grub shell.
If the target from the sync is then used as the source for another sync (For example, if the original machine was migrated to another location and then DR was configured using that target as a source), the new target will fail to boot into the OS and the sync will fail with the SYNC_ERROR_OS_BOOT_TIMEOUT error.
For any host meeting one of the two cases mentioned above, the following steps should be taken.
Steps
- Copy the attached script (host_fix_boot_files.sh) to the affected machine.
- In the case of Migration followed by DR, copy the script to the migration target/DR source.
- As root, execute the script. On success, the last line output will be "Successfully fixed the boot files".