Question about updating UEFI NVRAM
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
Hi all.
I have an environment where a PC EFI-boots from network first, and if that
fails or exits, it continues onto HDD etc. When restoring images with
clonezilla, I noticed that clonezilla would sometimes update the efi boot
options (something which I want), but also update the boot sequence in a
way that puts the restored disk's Windows boot manager in the first place. I
tried the "-iefi" option, but that seems to skip NVRAM modification
altogether.
Is this behaviour expected? Is there something I can do to make clonezilla
only modify the outdated option, and preserve the boot order?
MZ
Going by the log (and manual for efibootmgr), the new UEFI boot entry is set as first in the boot sequence by the efibootmanager's "create" action, so it's not something easily fixed by clonezilla, I think. Oh well... I made a script to perform a fixup in my environment (basically, put the "bootcurrent" record first, then add the boot order string, skipping the current entry).
Last edit: Michal Zatloukal 2018-03-13
Clonezilla does not really change the EFI boot order, just check if the EFI system partition UUID in EFI NVRAM matches the one on partition /dev/sda1, for example. If not, it will force to update the one in the EFI NVRAM. This might be is what you mentioned as updating the boot order.
The program which handles this in Clonezilla is /usr/sbin/update-efi-nvram-boot-entry.
Steven