Update Installed -- System booted in EFI-mode but 'grub-efi-amd64' meta-package not installed!
- Thread starter Unknown2k
- Start date
hi all, i have same issue,
i have installed package "grub-efi-amd64"
than i make reboot
after command: echo 'grub-efi-amd64 grub2/force_efi_extra_removable boolean true' | debconf-set-selections -v -u comes
what is the problem here, why this error comes, package was installed and rebooted. reboot works normal, but error comes. any ideas?
regards
Solution was: proxmox-boot-tool init /dev/sda2
i have init manually my EFI Partition, why manually, no plan.
i have installed package "grub-efi-amd64"
than i make reboot
after command: echo 'grub-efi-amd64 grub2/force_efi_extra_removable boolean true' | debconf-set-selections -v -u comes
update-initramfs -u -k all
what is the problem here, why this error comes, package was installed and rebooted. reboot works normal, but error comes. any ideas?
regards
Solution was: proxmox-boot-tool init /dev/sda2
i have init manually my EFI Partition, why manually, no plan.
Last edited:
Hello,
I was getting the error about missing grub-efi-amd64 and did an apt install grub-efi-amd64 as suggested on this forum. This resulted in grub-pc being removed which is expected as I have a system that booted in efi not bios. Now I get new warning:
I am confused about what steps should I take next? Is the system broken? Will it boot? This was a fresh install of v9 from about 4 months ago after catastrophic failure of 8to9 upgrade that broke boot. I really would not like to repeat that. I also see that /boot/efi is not mounted but partition exists on my nvme hard drive. Efi partition is also not in fstab as on my other systems. Why would this happen? What shall I do?
I also see installed packages:
but bootctl status shows the following:
Is the system using grub or systemd-boot? Looks like grub to me. The boot drive is single nvme. LVM, no ZFS on it, no mirror. Is the boot broken or not? I dare not to reboot just to find out. Please advise.
also proxmox-boot-tool status reports:
My guess would be to do the following:
1. mount the existing efi partition to /boot/efi (and add it to /etc/fstab with UUID)
2. apt reinstall grub-efi-amd64
3. if needed do a grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=proxmox
4. update-grub
But I really want confirmation from you guys what to do. I don't want to mess up boot environment on this system. Thank you.
Best regards,
JF.
I was getting the error about missing grub-efi-amd64 and did an apt install grub-efi-amd64 as suggested on this forum. This resulted in grub-pc being removed which is expected as I have a system that booted in efi not bios. Now I get new warning:
Code:
grub-install.real: error: cannot find EFI directory.
Failed: grub-install --target=x86_64-efi --force-extra-removable
WARNING: Bootloader is not properly installed, system may not be bootable
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.17.2-2-pve
Found initrd image: /boot/initrd.img-6.17.2-2-pve
Found linux image: /boot/vmlinuz-6.17.2-1-pve
Found initrd image: /boot/initrd.img-6.17.2-1-pve
Found linux image: /boot/vmlinuz-6.14.11-4-pve
Found initrd image: /boot/initrd.img-6.14.11-4-pve
Found linux image: /boot/vmlinuz-6.14.11-2-pve
Found initrd image: /boot/initrd.img-6.14.11-2-pve
Found linux image: /boot/vmlinuz-6.14.8-2-pve
Found initrd image: /boot/initrd.img-6.14.8-2-pve
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
Found memtest86+ 32bit EFI image: /boot/memtest86+ia32.efi
Found memtest86+ 64bit image: /boot/memtest86+x64.bin
Found memtest86+ 32bit image: /boot/memtest86+ia32.bin
Adding boot menu entry for UEFI Firmware Settings ...
doneI am confused about what steps should I take next? Is the system broken? Will it boot? This was a fresh install of v9 from about 4 months ago after catastrophic failure of 8to9 upgrade that broke boot. I really would not like to repeat that. I also see that /boot/efi is not mounted but partition exists on my nvme hard drive. Efi partition is also not in fstab as on my other systems. Why would this happen? What shall I do?
I also see installed packages:
Code:
systemd-boot-efi/stable,stable,now 257.9-1~deb13u1 amd64 [installed]
systemd-boot-tools/stable,stable,now 257.9-1~deb13u1 amd64 [installed]but bootctl status shows the following:
Code:
bootctl status:
System:
Firmware: n/a (n/a)
Firmware Arch: x64
Secure Boot: disabled (unknown)
TPM2 Support: no
Measured UKI: no
Boot into FW: supported
Current Boot Loader:
Product: GRUB 2.12-9+pmx2
Features: ✗ Boot counting
✗ Menu timeout control
✗ One-shot menu timeout control
✗ Default entry control
✗ One-shot entry control
✗ Support for XBOOTLDR partition
✗ Support for passing random seed to OS
✗ Load drop-in drivers
✗ Support Type #1 sort-key field
✗ Support @saved pseudo-entry
✗ Support Type #1 devicetree field
✗ Enroll SecureBoot keys
✗ Retain SHIM protocols
✗ Menu can be disabled
✗ Multi-Profile UKIs are supported
✓ Boot loader set partition information
Partition: /dev/disk/by-partuuid/643e35a2-91b5-4c16-9085-983ec9a306c8
Random Seed:
System Token: not set
Boot Loaders Listed in EFI Variables:
Title: proxmox
ID: 0x0000
Status: active, boot-order
Partition: /dev/disk/by-partuuid/643e35a2-91b5-4c16-9085-983ec9a306c8
File: └─/EFI/proxmox/shimx64.efi
Title: UEFI OS
ID: 0x0011
Status: active, boot-order
Partition: /dev/disk/by-partuuid/643e35a2-91b5-4c16-9085-983ec9a306c8
File: └─/EFI/BOOT/BOOTX64.EFIIs the system using grub or systemd-boot? Looks like grub to me. The boot drive is single nvme. LVM, no ZFS on it, no mirror. Is the boot broken or not? I dare not to reboot just to find out. Please advise.
also proxmox-boot-tool status reports:
Code:
root@:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
E: /etc/kernel/proxmox-boot-uuids does not exist.My guess would be to do the following:
1. mount the existing efi partition to /boot/efi (and add it to /etc/fstab with UUID)
2. apt reinstall grub-efi-amd64
3. if needed do a grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=proxmox
4. update-grub
But I really want confirmation from you guys what to do. I don't want to mess up boot environment on this system. Thank you.
Best regards,
JF.
Last edited:
After mounting the ESP I did just apt reinstall grub-efi-amd64. I see no warnings apart from "File descriptor 3 (pipe:[1095470647]) leaked on vgs invocation" which I don't think is a problem. This should be OK now I guess. Here is the output.
Code:
root@pve1:~# apt reinstall grub-efi-amd64
The following package was automatically installed and is no longer required:
proxmox-kernel-6.14.11-2-pve-signed
Use 'apt autoremove' to remove it.
Summary:
Upgrading: 0, Installing: 0, Reinstalling: 1, Removing: 0, Not Upgrading: 0
Download size: 46.7 kB
Space needed: 0 B / 48.0 GB available
Get:1 https://enterprise.proxmox.com/debian/pve trixie/pve-enterprise amd64 grub-efi-amd64 amd64 2.12-9+pmx2 [46.7 kB]
Fetched 46.7 kB in 0s (219 kB/s)
Preconfiguring packages ...
(Reading database ... 85157 files and directories currently installed.)
Preparing to unpack .../grub-efi-amd64_2.12-9+pmx2_amd64.deb ...
Unpacking grub-efi-amd64 (2.12-9+pmx2) over (2.12-9+pmx2) ...
Setting up grub-efi-amd64 (2.12-9+pmx2) ...
Installing for x86_64-efi platform.
File descriptor 3 (pipe:[1095470647]) leaked on vgs invocation. Parent PID 641010: grub-install.real
File descriptor 3 (pipe:[1095470647]) leaked on vgs invocation. Parent PID 641010: grub-install.real
Installation finished. No error reported.
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.17.2-2-pve
Found initrd image: /boot/initrd.img-6.17.2-2-pve
Found linux image: /boot/vmlinuz-6.17.2-1-pve
Found initrd image: /boot/initrd.img-6.17.2-1-pve
Found linux image: /boot/vmlinuz-6.14.11-4-pve
Found initrd image: /boot/initrd.img-6.14.11-4-pve
Found linux image: /boot/vmlinuz-6.14.11-2-pve
Found initrd image: /boot/initrd.img-6.14.11-2-pve
Found linux image: /boot/vmlinuz-6.14.8-2-pve
Found initrd image: /boot/initrd.img-6.14.8-2-pve
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
Found memtest86+ 32bit EFI image: /boot/memtest86+ia32.efi
Found memtest86+ 64bit image: /boot/memtest86+x64.bin
Found memtest86+ 32bit image: /boot/memtest86+ia32.bin
Adding boot menu entry for UEFI Firmware Settings ...
done
Processing triggers for shim-signed:amd64 (1.47+pmx1+15.8-1+pmx1) ...
root@pve1:~#JF
Code:
root@pve1:~# efibootmgr -v
BootCurrent: 0011
Timeout: 1 seconds
BootOrder: 0000,0011,0001,0003,000D,000E,000F,0010
Boot0000* proxmox HD(2,GPT,643e35a2-91b5-4c16-9085-983ec9a306c8,0x800,0x200000)/File(\EFI\proxmox\shimx64.efi)
dp: 04 01 2a 00 02 00 00 00 00 08 00 00 00 00 00 00 00 00 20 00 00 00 00 00 a2 35 3e 64 b5 91 16 4c 90 85 98 3e c9 a3 06 c8 02 02 / 04 04 36 00 5c 00 45 00 46 00 49 00 5c 00 70 00 72 00 6f 00 78 00 6d 00 6f 00 78 00 5c 00 73 00 68 00 69 00 6d 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0001* Hard Drive BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)0000474f00004e4fbf00000001000000850054004f005300480049004200410020004d0047003000390041004300410031003800540045000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600001703120a000500ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce6200020002000200020002000200020003400380030005400300041004c004a004a0046004800440000007fff04000000424f00004e4fbf00000001000000850054004f005300480049004200410020004d0047003000390041004300410031003800540045000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600001703120a000600ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce62000200020002000200020002000200034003800300054003000410034004d004a0046004800440000007fff04000000424f00004e4fbf00000001000000850054004f005300480049004200410020004d0047003000390041004300410031003800540045000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600001703120a000700ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce62000200020002000200020002000200034003800300054003000410043004d004a0046004800440000007fff04000000424f00004e4fc7000000010000008500530061006d00730075006e006700200053005300440020003800370030002000510056004f0020003800540042000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600001703120a000400ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce635005300530053004a004e005800300031003400300031003500340020005400200020002000200000007fff04000000424f
dp: 05 01 09 00 02 00 00 00 00 / 01 04 16 00 8b 12 e8 5c ec 2c f0 40 83 72 80 64 0e 3d c8 58 02 00 / 7f ff 04 00
data: 00 00 47 4f 00 00 4e 4f bf 00 00 00 01 00 00 00 85 00 54 00 4f 00 53 00 48 00 49 00 42 00 41 00 20 00 4d 00 47 00 30 00 39 00 41 00 43 00 41 00 31 00 38 00 54 00 45 00 00 00 05 01 09 00 02 00 00 00 00 01 04 16 00 8b 12 e8 5c ec 2c f0 40 83 72 80 64 0e 3d c8 58 02 00 7f ff 04 00 02 01 0c 00 d0 41 03 0a 00 00 00 00 01 01 06 00 00 17 03 12 0a 00 05 00 ff ff 00 00 7f ff 04 00 01 04 3e 00 ef 47 64 2d c9 3b a0 41 ac 19 4d 51 d0 1b 4c e6 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 34 00 38 00 30 00 54 00 30 00 41 00 4c 00 4a 00 4a 00 46 00 48 00 44 00 00 00 7f ff 04 00 00 00 42 4f 00 00 4e 4f bf 00 00 00 01 00 00 00 85 00 54 00 4f 00 53 00 48 00 49 00 42 00 41 00 20 00 4d 00 47 00 30 00 39 00 41 00 43 00 41 00 31 00 38 00 54 00 45 00 00 00 05 01 09 00 02 00 00 00 00 01 04 16 00 8b 12 e8 5c ec 2c f0 40 83 72 80 64 0e 3d c8 58 02 00 7f ff 04 00 02 01 0c 00 d0 41 03 0a 00 00 00 00 01 01 06 00 00 17 03 12 0a 00 06 00 ff ff 00 00 7f ff 04 00 01 04 3e 00 ef 47 64 2d c9 3b a0 41 ac 19 4d 51 d0 1b 4c e6 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 34 00 38 00 30 00 54 00 30 00 41 00 34 00 4d 00 4a 00 46 00 48 00 44 00 00 00 7f ff 04 00 00 00 42 4f 00 00 4e 4f bf 00 00 00 01 00 00 00 85 00 54 00 4f 00 53 00 48 00 49 00 42 00 41 00 20 00 4d 00 47 00 30 00 39 00 41 00 43 00 41 00 31 00 38 00 54 00 45 00 00 00 05 01 09 00 02 00 00 00 00 01 04 16 00 8b 12 e8 5c ec 2c f0 40 83 72 80 64 0e 3d c8 58 02 00 7f ff 04 00 02 01 0c 00 d0 41 03 0a 00 00 00 00 01 01 06 00 00 17 03 12 0a 00 07 00 ff ff 00 00 7f ff 04 00 01 04 3e 00 ef 47 64 2d c9 3b a0 41 ac 19 4d 51 d0 1b 4c e6 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 34 00 38 00 30 00 54 00 30 00 41 00 43 00 4d 00 4a 00 46 00 48 00 44 00 00 00 7f ff 04 00 00 00 42 4f 00 00 4e 4f c7 00 00 00 01 00 00 00 85 00 53 00 61 00 6d 00 73 00 75 00 6e 00 67 00 20 00 53 00 53 00 44 00 20 00 38 00 37 00 30 00 20 00 51 00 56 00 4f 00 20 00 38 00 54 00 42 00 00 00 05 01 09 00 02 00 00 00 00 01 04 16 00 8b 12 e8 5c ec 2c f0 40 83 72 80 64 0e 3d c8 58 02 00 7f ff 04 00 02 01 0c 00 d0 41 03 0a 00 00 00 00 01 01 06 00 00 17 03 12 0a 00 04 00 ff ff 00 00 7f ff 04 00 01 04 3e 00 ef 47 64 2d c9 3b a0 41 ac 19 4d 51 d0 1b 4c e6 35 00 53 00 53 00 53 00 4a 00 4e 00 58 00 30 00 31 00 34 00 30 00 31 00 35 00 34 00 20 00 54 00 20 00 20 00 20 00 20 00 00 00 7f ff 04 00 00 00 42 4f
Boot0003* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f
dp: 04 03 14 00 5c b9 23 50 26 db 9b 42 a6 48 bd 47 66 4c 80 12 / 7f ff 04 00
data: 00 00 42 4f
Boot000D* (B27/D0/F0) UEFI PXE IPv4: Intel(R) Ethernet Connection X722 for 10GBASE-T(MAC:xxxxxxxxxxxx) PciRoot(0x1)/Pci(0x2,0x0)/Pci(0x0,0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/MAC(xxxxxxxxxxxx,1)/IPv4(0.0.0.00.0.0.0,0,0)0000424f
dp: 02 01 0c 00 d0 41 03 0a 01 00 00 00 / 01 01 06 00 00 02 / 01 01 06 00 00 00 / 01 01 06 00 00 03 / 01 01 06 00 00 00 / 03 0b 25 00 ac 1f 6b 4d 19 84 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 / 03 0c 1b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 7f ff 04 00
data: 00 00 42 4f
Boot000E* (B27/D0/F1) UEFI PXE IPv4: Intel(R) Ethernet Connection X722 for 10GBASE-T(MAC:xxxxxxxxxxxx) PciRoot(0x1)/Pci(0x2,0x0)/Pci(0x0,0x0)/Pci(0x3,0x0)/Pci(0x0,0x1)/MAC(xxxxxxxxxxxx,1)/IPv4(0.0.0.00.0.0.0,0,0)0000424f
dp: 02 01 0c 00 d0 41 03 0a 01 00 00 00 / 01 01 06 00 00 02 / 01 01 06 00 00 00 / 01 01 06 00 00 03 / 01 01 06 00 01 00 / 03 0b 25 00 ac 1f 6b 4d 19 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 / 03 0c 1b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 7f ff 04 00
data: 00 00 42 4f
Boot000F* (B27/D0/F0) UEFI PXE IPv6: Intel(R) Ethernet Connection X722 for 10GBASE-T(MAC:xxxxxxxxxxxx) PciRoot(0x1)/Pci(0x2,0x0)/Pci(0x0,0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/MAC(xxxxxxxxxxxx,1)/IPv6([::]:<->[::]:,0,0)0000424f
dp: 02 01 0c 00 d0 41 03 0a 01 00 00 00 / 01 01 06 00 00 02 / 01 01 06 00 00 00 / 01 01 06 00 00 03 / 01 01 06 00 00 00 / 03 0b 25 00 ac 1f 6b 4d 19 84 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 / 03 0d 3c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 7f ff 04 00
data: 00 00 42 4f
Boot0010* (B27/D0/F1) UEFI PXE IPv6: Intel(R) Ethernet Connection X722 for 10GBASE-T(MAC:xxxxxxxxxxxx) PciRoot(0x1)/Pci(0x2,0x0)/Pci(0x0,0x0)/Pci(0x3,0x0)/Pci(0x0,0x1)/MAC(xxxxxxxxxxxx,1)/IPv6([::]:<->[::]:,0,0)0000424f
dp: 02 01 0c 00 d0 41 03 0a 01 00 00 00 / 01 01 06 00 00 02 / 01 01 06 00 00 00 / 01 01 06 00 00 03 / 01 01 06 00 01 00 / 03 0b 25 00 ac 1f 6b 4d 19 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 / 03 0d 3c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 7f ff 04 00
data: 00 00 42 4f
Boot0011* UEFI OS HD(2,GPT,643e35a2-91b5-4c16-9085-983ec9a306c8,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
dp: 04 01 2a 00 02 00 00 00 00 08 00 00 00 00 00 00 00 00 20 00 00 00 00 00 a2 35 3e 64 b5 91 16 4c 90 85 98 3e c9 a3 06 c8 02 02 / 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
data: 00 00 42 4f
MirroredPercentageAbove4G: 0.00
MirrorMemoryBelow4GB: false
root@pve1:~#
Code:
root@pve1:~# pve8to9
= CHECKING VERSION INFORMATION FOR PVE PACKAGES =
Checking for package updates..
PASS: all packages up-to-date
Checking proxmox-ve package version..
PASS: already upgraded to Proxmox VE 9
Checking running kernel version..
PASS: running new kernel '6.14.8-2-pve' after upgrade.
= CHECKING CLUSTER HEALTH/SETTINGS =
SKIP: standalone node.
= CHECKING HYPER-CONVERGED CEPH STATUS =
SKIP: no hyper-converged ceph setup detected!
= CHECKING CONFIGURED STORAGES =
PASS: storage 'local' enabled and active.
PASS: storage 'local-lvm' enabled and active.
PASS: storage 'qvo8TB' enabled and active.
PASS: storage 'samsungZFS' enabled and active.
INFO: Checking storage content type configuration..
PASS: no storage content problems found
PASS: no storage reuses a directory for multiple content types.
INFO: Check for usage of native GlusterFS storage plugin...
PASS: No GlusterFS storage found.
INFO: Checking whether all external RBD storages have the 'keyring' option configured
SKIP: No RBD storage configured.
= VIRTUAL GUEST CHECKS =
SKIP: Skipping check for running guests - already upgraded.
INFO: Checking if LXCFS is running with FUSE3 library, if already upgraded..
PASS: systems seems to be upgraded and LXCFS is running with FUSE 3 library
INFO: Checking for VirtIO devices that would change their MTU...
PASS: All guest config descriptions fit in the new limit of 8 KiB
INFO: Checking container configs for deprecated lxc.cgroup entries
PASS: No legacy 'lxc.cgroup' keys found.
INFO: Checking VM configurations for outdated machine versions
PASS: All VM machine versions are recent enough
= MISCELLANEOUS CHECKS =
INFO: Checking common daemon services..
PASS: systemd unit 'pveproxy.service' is in state 'active'
PASS: systemd unit 'pvedaemon.service' is in state 'active'
PASS: systemd unit 'pvescheduler.service' is in state 'active'
PASS: systemd unit 'pvestatd.service' is in state 'active'
INFO: Checking for supported & active NTP service..
PASS: Detected active time synchronisation unit 'chrony.service'
INFO: Checking if the local node's hostname 'pve1' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP 'xxx.xxx.xxx.xxx' configured and active on single interface.
INFO: Check node certificate's RSA key size
PASS: Certificate 'pve-root-ca.pem' passed Debian Busters (and newer) security level for TLS connections (4096 >= 2048 RSA)
PASS: Certificate 'pve-ssl.pem' passed Debian Busters (and newer) security level for TLS connections (2048 >= 2048 RSA)
PASS: Certificate 'pveproxy-ssl.pem' passed Debian Busters (and newer) security level for TLS connections (4096 >= 2048 RSA)
INFO: Checking backup retention settings..
PASS: no backup retention problems found.
INFO: checking CIFS credential location..
PASS: no CIFS credentials at outdated location found.
INFO: Checking permission system changes..
INFO: Checking custom role IDs
PASS: no custom roles defined
INFO: Checking node and guest description/note length..
PASS: All node config descriptions fit in the new limit of 64 KiB
INFO: Checking if the suite for the Debian security repository is correct..
PASS: found no suite mismatch
INFO: Checking for existence of NVIDIA vGPU Manager..
PASS: No NVIDIA vGPU Service found.
INFO: Checking bootloader configuration...
PASS: bootloader packages installed correctly
INFO: Check for dkms modules...
SKIP: could not get dkms status
INFO: Check for legacy 'filter' or 'group' sections in /etc/pve/notifications.cfg...
PASS: No legacy 'filter' or 'group' sections found!
INFO: Check for legacy 'notification-policy' or 'notification-target' options in /etc/pve/jobs.cfg...
PASS: No legacy 'notification-policy' or 'notification-target' options found!
INFO: Check for LVM autoactivation settings on LVM and LVM-thin storages...
PASS: all guest volumes on storage 'local-lvm' have autoactivation disabled
PASS: all guest volumes on storage 'qvo8TB' have autoactivation disabled
PASS: No problematic volumes found.
INFO: Checking lvm config for thin_check_options...
PASS: Check for correct thin_check_options passed
INFO: Check post RRD metrics data format update situation...
PASS: No old RRD metric files found, normally this means all have been migrated.
INFO: Checking for IPAM DB files that have not yet been migrated.
PASS: No legacy IPAM DB found.
PASS: No legacy MAC DB found.
INFO: Checking if the legacy sysctl file '/etc/sysctl.conf' needs to be migrated to new '/etc/sysctl.d/' path.
PASS: Legacy file '/etc/sysctl.conf' is not present.
INFO: Checking if matching CPU microcode package is installed.
PASS: Found matching CPU microcode package 'intel-microcode' installed.
SKIP: NOTE: Expensive checks, like CT cgroupv2 compat, not performed without '--full' parameter
= SUMMARY =
TOTAL: 53
PASSED: 47
SKIPPED: 6
WARNINGS: 0
FAILURES: 0
root@pve1:~#Best regards,
JF
Last edited:
Thank you very much for your help. I am always a bit nervous when it comes to boot loader issues when working on remote systems.
Best regards,
JF
Recently I had a problem rebooting updating and rebooting my PVE 8.1 to 8.4. I got the "Disk not found Error" probably because I upgraded from PVE 7 at the time. In that page of the wiki, it is recommended to execute
I suspect that my system is not bootable anymore. Is there something I can do to verify and correct that? Thanks in advance.
[ -d /sys/firmware/efi ] && apt install grub-efi-amd64 and I did but it give me the following errors from the console:
Bash:
[root@pve32 ~]$ apt install --reinstall grub-efi-amd64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libsgutils2-2 proxmox-headers-6.2.16-19-pve proxmox-headers-6.2.16-6-pve proxmox-headers-6.5.13-3-pve proxmox-kernel-6.2.16-19-pve proxmox-kernel-6.2.16-6-pve pve-headers
pve-headers-5.15.107-2-pve pve-headers-5.15.108-1-pve pve-headers-5.15.126-1-pve pve-headers-5.15.143-1-pve pve-headers-5.15.74-1-pve pve-headers-6.2
pve-headers-6.2.16-5-pve pve-kernel-6.2.16-5-pve telnet
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
7 not fully installed or removed.
Need to get 0 B/45.7 kB of archives.
After this operation, 0 B of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 435112 files and directories currently installed.)
Preparing to unpack .../grub-efi-amd64_2.06-13+pmx7_amd64.deb ...
Unpacking grub-efi-amd64 (2.06-13+pmx7) over (2.06-13+pmx7) ...
Setting up proxmox-kernel-6.8.12-18-pve-signed (6.8.12-18) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.8.12-18-pve /boot/vmlinuz-6.8.12-18-pve
dkms: running auto installation service for kernel 6.8.12-18-pve.
Sign command: /lib/modules/6.8.12-18-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Building module:
Cleaning build area...
make -j12 KERNELRELEASE=6.8.12-18-pve -C /lib/modules/6.8.12-18-pve/build M=/var/lib/dkms/r8168/8.051.02/build.......(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.8.12-18-pve (x86_64)
Consult /var/lib/dkms/r8168/8.051.02/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.8.12-18-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.8.12-18-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.8.12-18-pve-signed (--configure):
installed proxmox-kernel-6.8.12-18-pve-signed package post-installation script subprocess returned error exit status 2
Setting up grub-efi-amd64 (2.06-13+pmx7) ...
Installing for x86_64-efi platform.
File descriptor 3 (pipe:[36517406]) leaked on vgs invocation. Parent PID 297014: grub-install.real
File descriptor 3 (pipe:[36517406]) leaked on vgs invocation. Parent PID 297014: grub-install.real
Installation finished. No error reported.
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.12-18-pve
Found linux image: /boot/vmlinuz-6.5.13-6-pve
Found linux image: /boot/vmlinuz-6.5.13-3-pve
Found linux image: /boot/vmlinuz-6.2.16-20-pve
Found initrd image: /boot/initrd.img-6.2.16-20-pve
Found linux image: /boot/vmlinuz-6.2.16-19-pve
Found initrd image: /boot/initrd.img-6.2.16-19-pve
Found linux image: /boot/vmlinuz-6.2.16-6-pve
Found initrd image: /boot/initrd.img-6.2.16-6-pve
Found linux image: /boot/vmlinuz-6.2.16-5-pve
Found initrd image: /boot/initrd.img-6.2.16-5-pve
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
Setting up proxmox-kernel-6.5.13-6-pve-signed (6.5.13-6) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.5.13-6-pve /boot/vmlinuz-6.5.13-6-pve
dkms: running auto installation service for kernel 6.5.13-6-pve.
Sign command: /lib/modules/6.5.13-6-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Building module:
Cleaning build area...
make -j12 KERNELRELEASE=6.5.13-6-pve -C /lib/modules/6.5.13-6-pve/build M=/var/lib/dkms/r8168/8.051.02/build.......(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.13-6-pve (x86_64)
Consult /var/lib/dkms/r8168/8.051.02/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.5.13-6-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.5.13-6-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.5.13-6-pve-signed (--configure):
installed proxmox-kernel-6.5.13-6-pve-signed package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.8:
proxmox-kernel-6.8 depends on proxmox-kernel-6.8.12-18-pve-signed | proxmox-kernel-6.8.12-18-pve; however:
Package proxmox-kernel-6.8.12-18-pve-signed is not configured yet.
Package proxmox-kernel-6.8.12-18-pve is not installed.
Package proxmox-kernel-6.8.12-18-pve-signed which provides proxmox-kernel-6.8.12-18-pve is not configured yet.
dpkg: error processing package proxmox-kernel-6.8 (--configure):
dependency problems - leaving unconfigured
Setting up proxmox-kernel-6.5.13-3-pve-signed (6.5.13-3) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.5.13-3-pve /boot/vmlinuz-6.5.13-3-pve
dkms: running auto installation service for kernel 6.5.13-3-pve.
Sign command: /lib/modules/6.5.13-3-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Building module:
Cleaning build area...
make -j12 KERNELRELEASE=6.5.13-3-pve -C /lib/modules/6.5.13-3-pve/build M=/var/lib/dkms/r8168/8.051.02/build.......(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.13-3-pve (x86_64)
Consult /var/lib/dkms/r8168/8.051.02/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.5.13-3-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.5.13-3-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.5.13-3-pve-signed (--configure):
installed proxmox-kernel-6.5.13-3-pve-signed package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.5:
proxmox-kernel-6.5 depends on proxmox-kernel-6.5.13-6-pve-signed | proxmox-kernel-6.5.13-6-pve; however:
Package proxmox-kernel-6.5.13-6-pve-signed is not configured yet.
Package proxmox-kernel-6.5.13-6-pve is not installed.
Package proxmox-kernel-6.5.13-6-pve-signed which provides proxmox-kernel-6.5.13-6-pve is not configured yet.
dpkg: error processing package proxmox-kernel-6.5 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
proxmox-default-kernel depends on proxmox-kernel-6.8; however:
Package proxmox-kernel-6.8 is not configured yet.
dpkg: error processing package proxmox-default-kernel (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on proxmox-default-kernel; however:
Package proxmox-default-kernel is not configured yet.
dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
proxmox-kernel-6.8.12-18-pve-signed
proxmox-kernel-6.5.13-6-pve-signed
proxmox-kernel-6.8
proxmox-kernel-6.5.13-3-pve-signed
proxmox-kernel-6.5
proxmox-default-kernel
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)I suspect that my system is not bootable anymore. Is there something I can do to verify and correct that? Thanks in advance.
Hello,
The problem you see comes from building dkms module for your network card r8168. The build returns error. You can check what went wrong in /var/lib/dkms/r8168/8.051.02/build/make.log. This happens in both kernel version 6.8.12 as in 6.5.13. Make sure you have all kernel headers and build tools installed. I see pve-headers up in the no longer required section of your system output. Kernel headers were renamed from pve-headers to proxmox-headers in v8 as you can check here https://forum.proxmox.com/threads/unable-to-install-r8168-dkms-for-realtek-nic.137727/post-613558 where someone has similar issue. If you have downloaded the source for the r8168 driver yourself make sure you have the latest version of driver. I had similar problems with Intel nic driver some time ago that was resolved by updating source.
Imho your system should still boot but with older kernel, check what kernel version are you running now.
JF.
Last edited:
The content of the make.log file regarding the r8168 is this. Some compile error I don't understand.
Code:
DKMS make.log for r8168-8.051.02 for kernel 6.5.13-3-pve (x86_64)
Sun Jan 18 04:56:08 PM -03 2026
make: Entering directory '/usr/src/linux-headers-6.5.13-3-pve'
warning: the compiler differs from the one used to build the kernel
The kernel was built by: gcc (Debian 12.2.0-14) 12.2.0
You are using: gcc (Debian 12.2.0-14+deb12u1) 12.2.0
CC [M] /var/lib/dkms/r8168/8.051.02/build/r8168_n.o
CC [M] /var/lib/dkms/r8168/8.051.02/build/r8168_asf.o
CC [M] /var/lib/dkms/r8168/8.051.02/build/rtl_eeprom.o
CC [M] /var/lib/dkms/r8168/8.051.02/build/rtltool.o
/var/lib/dkms/r8168/8.051.02/build/r8168_n.c: In function ‘r8168_csum_workaround’:
/var/lib/dkms/r8168/8.051.02/build/r8168_n.c:29208:24: error: implicit declaration of function ‘skb_gso_segment’; did you mean ‘skb_gso_reset’? [-Werror=implicit-function-declaration]
29208 | segs = skb_gso_segment(skb, features);
| ^~~~~~~~~~~~~~~
| skb_gso_reset
/var/lib/dkms/r8168/8.051.02/build/r8168_n.c:29208:22: warning: assignment to ‘struct sk_buff *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
29208 | segs = skb_gso_segment(skb, features);
| ^
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:251: /var/lib/dkms/r8168/8.051.02/build/r8168_n.o] Error 1
make[1]: *** [/usr/src/linux-headers-6.5.13-3-pve/Makefile:2039: /var/lib/dkms/r8168/8.051.02/build] Error 2
make: *** [Makefile:234: __sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-6.5.13-3-pve'Edit: If I understood correctly this is a problem between the drivers for the r8168 and the headers of the new versions of the kernels. I pinned the kernel version to the one I am still booting (
6.2.16-20-pve), so it should be fine. Thanks for that.I was wondering if there is no conflict with this kernel version and the LXCs that use Debian 13. Where can I check that? Thanks in advance.
Last edited: