Migration Failed Over SSH from CentOS 8.5 - computer keeps restarting in BIOS with "Boot Option Restoration" and reboot timer

rocky-linux / rocky-tools

MIT License

393 stars 137 forks source link

Migration Failed Over SSH from CentOS 8.5 - computer keeps restarting in BIOS with "Boot Option Restoration" and reboot timer #212

Closed brarharry closed 4 months ago

brarharry commented 4 months ago

Migration scripts completes with no errors on local computer:

Adding boot menu entry for EFI firmware configuration
done
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0003,0000,0002,0001
Boot0000* CentOS Linux
Boot0001* UEFI: Built-in EFI Shell
Boot0002* UEFI OS
Boot0003* Rocky Linux

Done, please reboot your system.
A log of this installation can be found at /var/log/migrate2rocky.log

But keeps rebooting with in BIOS with a blue screen "Boot Option Restoration" until I manually select "Always Continue Boot".

I would be upgrading servers remotely via SSH and using this script and would not be able to enter the BIOS remotely. Has anyone experienced this?

pajamian commented 4 months ago

Can you share your migrate2rocky.log file?

brarharry commented 4 months ago

migrate2rocky.txt

pajamian commented 4 months ago

I can't find anything of concern in your logs, so I would say that there is something else that needs to be done in addition to the normal steps taken to fix up the EFI boot by migrate2rocky.

Can you take a copy of the blue screen you're getting from your BIOS? I'd like to see exactly what it's saying.

brarharry commented 4 months ago

When I checked BIOS settings, the boot order was set to prioritize “UEFI OS”. Not sure if there is a way to set the boot order if you are trying to upgrade an iot device remotely from Centos 8.5 to RockyLinux 8 via SSH.

pajamian commented 4 months ago

Not sure either, as a security issue it may require physical access to the machine or at least some sort of ikvm solution to change the BIOS boot order. I'd like to know if you find a solution that works, though, as I might be able to include it at least in the README docs for migrate2rocky if not in the script itself.