A number of support threads have been raised in which this has been evident.
On a test system, installed OS from LL7.4 iso and attempting all the updates post installation.
During the upgrade, it appears the grub-efi-amd64-signed set up script can't find the location of the GRUB boot loader.
As a result of this problem, the grub script requires user intervention to manually confirm where it is or should be.
If update/upgrade is done from the cli, the grub-efi-amd64-signed configuration script calls a text based configuration tool.
The tool is similar in style to something like nmtui and the user is expected to navigate the menu to select and confirm the location of the GRUB boot loader.
My guess is that the lite-updates script is not equipped to handle this situation and throws an update/upgrade failure message with a cryptic message stating
Checking indicates that the update/upgrade initiated by lite-updates did in fact work despite the error message but this is transparent to the user who is instructed to seek help on the forum.
On a test system, installed OS from LL7.4 iso and attempting all the updates post installation.
During the upgrade, it appears the grub-efi-amd64-signed set up script can't find the location of the GRUB boot loader.
As a result of this problem, the grub script requires user intervention to manually confirm where it is or should be.
If update/upgrade is done from the cli, the grub-efi-amd64-signed configuration script calls a text based configuration tool.
The tool is similar in style to something like nmtui and the user is expected to navigate the menu to select and confirm the location of the GRUB boot loader.
My guess is that the lite-updates script is not equipped to handle this situation and throws an update/upgrade failure message with a cryptic message stating
Quote:mount: /var/lib/grub/esp: special device /dev/disk/by-id/ata-VBOX_HARDDISK_VBad170837-5acc172c-part2 does not exist.and
Quote:grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32
Checking indicates that the update/upgrade initiated by lite-updates did in fact work despite the error message but this is transparent to the user who is instructed to seek help on the forum.
stevef
clueless
clueless