[SOLVED] Problem with "Removable Bootloader"

A

alex01763

Member
Feb 28, 2023
11
1
8
I was just trying to update my node using the apt package manager and got this message:

Code: 
Removable bootloader found at '/boot/efi/EFI/BOOT/BOOTX64.efi', but GRUB packages not set up to update it!
Run the following command:

echo 'grub-efi-amd64 grub2/force_efi_extra_removable boolean true' | debconf-set-selections -v -u

Then reinstall GRUB with 'apt install --reinstall grub-efi-amd64'

But when I actually try to do what it tells me to do (echo and reinstall), I get the following error:
Code: 
debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied
info: Trying to set 'grub2/force_efi_extra_removable' [boolean] to 'true'
info: Loading answer for 'grub2/force_efi_extra_removable'
debconf: DbDriver "config": could not write /var/cache/debconf/config.dat-new: Permission denied

I tried using sudo to execute the command, but had no luck. I don't have much experience with grub so I didn't try anything else to not break anything. I usually reboot my system after an update, but I'm holding it until I get this sorted out. What should I do?
 
  • Like
Reactions: mignochrono
Soon after I posted this, the server became unresponsive, and won't reboot(power on, but no display. Not only ssh, but no physical display too). Any help would be appreciated.
 
Last edited:
just updated one node and i got a similar message,
Code: 
Removable bootloader found at '/boot/efi/EFI/BOOT/BOOTX64.efi', but GRUB packages not set up to update it!
Run the following command:

echo 'grub-efi-amd64 grub2/force_efi_extra_removable boolean true' | debconf-set-selections -v -u

Then reinstall GRUB with 'apt install --reinstall grub-efi-amd64'
Im glad to know im not the only one
 
  • Like
Reactions: alex01763
Turns out, I had no display because I forgot to plug out my GPU. After that, it was the "welcome to grub" issue mentioned on the other post in this forum. I switched the boot order in the uefi settings and having no issues so far. I'll open a new thread if anything else goes wrong.
 
you need to execute the full command as root. if you are using sudo, you can switch to a root shell using "sudo -s" and then run the command there.
 
I just had this issue after an update. I had the install iso mounted still, which was causing it. Removed the iso and is no longer showing the message.
 
  • Like
Reactions: Kingneutron
I just ran across this as well. What causes this issue in the first place? Just wondering if it will/may happen again the future.
 
drwtsn32 said:
I just ran across this as well. What causes this issue in the first place? Just wondering if it will/may happen again the future.
Click to expand...
it shouldn't happen anymore once you've fixed it up on a system.
 
  • Like
Reactions: drwtsn32
we must also launch the reinstallation of : grub-efi-amd64-signed or just grub-efi-amd64 ?
 
if you are using secure boot, you need to have the signed variant installed as well, it will then automatically be picked up by the update scripts.
 
fabian said:
if you are using secure boot, you need to have the signed variant installed as well, it will then automatically be picked up by the update scripts.
Click to expand...
Thanks for the reply

Code: 
root@pve:~# apt install --reinstall grub-efi-amd64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 45.7 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 grub-efi-amd64 amd64 2.06-13+pmx6 [45.7 kB]
Fetched 45.7 kB in 0s (207 kB/s)       
Preconfiguring packages ...
(Reading database ... 61627 files and directories currently installed.)
Preparing to unpack .../grub-efi-amd64_2.06-13+pmx6_amd64.deb ...
Unpacking grub-efi-amd64 (2.06-13+pmx6) over (2.06-13+pmx6) ...
Setting up grub-efi-amd64 (2.06-13+pmx6) ...
Installing for x86_64-efi platform.
File descriptor 3 (pipe:[99508490]) leaked on vgs invocation. Parent PID 4141935: grub-install.real
File descriptor 3 (pipe:[99508490]) leaked on vgs invocation. Parent PID 4141935: grub-install.real
Installation finished. No error reported.
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.12-9-pve
Found initrd image: /boot/initrd.img-6.8.12-9-pve
Found linux image: /boot/vmlinuz-6.8.12-8-pve
Found initrd image: /boot/initrd.img-6.8.12-8-pve
Found linux image: /boot/vmlinuz-6.8.12-4-pve
Found initrd image: /boot/initrd.img-6.8.12-4-pve
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
done
Processing triggers for shim-signed:amd64 (1.44+pmx1+15.8-1+pmx1) ...

So if I understand correctly everything has been updated, it says at the end: Processing triggers for shim-signed:amd64 ? right ?
 
the output looks okay, yes.
 
You must log in or register to reply here.
Top Bottom