Update Installed -- System booted in EFI-mode but 'grub-efi-amd64' meta-package not installed!

please post the output of "ls /sys/firmware/efi/efivars" and "dmesg | grep -i efi"
 
Code: 
Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c     Lang-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c  LangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c    MTC-eb704011-1402-11d3-8e77-00a0c969723b
ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c        PerfDataMemAddr-59d1c24f-50f1-401a-b101-f33e0daed443
ConInDev-8be4df61-93ca-11d2-aa0d-00e098032b8c     PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c
ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c       PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
ConOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c    Timeout-8be4df61-93ca-11d2-aa0d-00e098032b8c
ErrOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c

Code: 
[    0.000000] efi: EFI v2.1 by TianoCore.org
[    0.000000] efi: ACPI 2.0=0xdfc9e000 ACPI=0xdfc9d000 SMBIOS=0xdfc9c000
[    0.047299] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
[    0.379814] pci 0000:03:00.0: BAR 3: assigned to efifb
[    0.405211] efivars: Registered efivars operations
[    1.496781] tsc: Refined TSC clocksource calibration: 2931.261 MHz
[    6.372500] systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
[    6.383700] pstore: Registered efi_pstore as persistent store backend
[    6.392792] systemd[1]: modprobe@efi_pstore.service: Deactivated successfully.
[    6.392974] systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
 
yeah, so your system is booting using EFI ;)
 
dan.ger said:
I installed grub-efi-amd64 on a test machine made some changes in /etc/defaults/grub.cfg and reboot the system. System is started normally without any issues. If installing grub-efi-amd64 the package grub-pc is removed. System is a Dell R740XD Intel Xeon Gold based system.
Click to expand...
can confirm, after initial 7to8 check, turned off vms/lxc, followed steps, re-ran 7to8, saw error, thank you @dan.ger i also installed
Code: 
grub-efi-amd64
before rebooting
post reboot it functions as expected, thank you Community and Proxmox!!
 
Last edited:
My system is a few months old non zfs root and didn't have grub-efi-amd64 installed by default.
I've been running update-grub when I change /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT without problems so far but the /etc/kernel hooks are not triggered even though they are with apt upgrades. When I run proxmox-boot-tool it just says No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
I'm not sure what the implications are but efi looks active like this:
Code: 
efibootmgr -v
BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0006,0007,0008,0001,0005,0004,0000,0003
Boot0000* Linux Boot Manager    HD(2,GPT,ebcd006f-d6db-4726-8420-358f66f52888,0x800,0x100000)/File(\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI)
Boot0001* proxmox       HD(2,GPT,00bedd26-0b8c-44d0-8f44-669400748710,0x800,0x200000)/File(\EFI\PROXMOX\SHIMX64.EFI)
Boot0003  Linux Boot Manager    HD(2,GPT,5aa69d35-aa11-4b6d-8939-62c3b1694488,0x800,0x100000)/File(\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI)
Boot0004* UEFI OS       HD(2,GPT,ebcd006f-d6db-4726-8420-358f66f52888,0x800,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0005* UEFI OS       HD(2,GPT,5aa69d35-aa11-4b6d-8939-62c3b1694488,0x800,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0006* proxmox       HD(2,GPT,91cd324d-9633-4f27-a0f0-8a323728b6c7,0x800,0x200000)/File(\EFI\PROXMOX\SHIMX64.EFI)
Boot0007* UEFI OS       HD(2,GPT,91cd324d-9633-4f27-a0f0-8a323728b6c7,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0008* UEFI OS       HD(2,GPT,00bedd26-0b8c-44d0-8f44-669400748710,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)..BO

Is there any reason to install grub-efi-amd64 here?
 
fabian said:
yes, the recommendation is to install the matching grub package for your boot mode (if booting using grub), else you won't get any updates to the actual *installed* grub binaries that are used when booting, even if the grub packages are upgraded.
Click to expand...
Could you provide the source of this recommendation please @fabian
If a system is booting using efi + grub and root is on a lvm like btrfs but it boots and updates fine, is grub-efi-amd64 still required?
What is meant by:
you won't get any updates to the actual *installed* grub binaries that are used when booting
Click to expand...
What specifically is updated when using grub-efi-amd64?
 
the Grub EFI binaries on your ESP (the first thing that gets executed after the UEFI firmware, before that one in turn loads the kernel and passes execution to it).
 
fabian said:
the Grub EFI binaries on your ESP (the first thing that gets executed after the UEFI firmware, before that one in turn loads the kernel and passes execution to it).
Click to expand...
Is there some way to examine which grub is installed in the esp and compare that with the grub which is installed by package manager?
Can't seem to find the source code for the grub-efi-amd64 2.06-13+pmx1 script anywhere
 
Last edited:
/usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed (if you have the -signed variant installed) or /usr/lib/grub/x86_64-efi/monolithic/grubx64.efi (if not) and the copy on your ESP (/boot/efi/EFI/proxmox/grubx64.efi) should be identical.
 
  • Like
Reactions: Kodey
I found these on the "https://pve.proxmox.com/wiki/Upgrade_from_7_to_8"

GRUB Might Fail To Boot From LVM in UEFI Mode​

Due to a bug in grub in PVE 7 and before, grub may fail to boot from LVM with an error message disk `lvmid/...` not found. When booting in UEFI mode, you need to ensure that the new grub version containing the fix is indeed used for booting the system.

Systems with Root on ZFS and systems booting in legacy mode are not affected.

On systems booting in EFI mode with root on LVM, install the correct grub meta-package with:

[ -d /sys/firmware/efi ] && apt install grub-efi-amd64
_____

Unable to boot due to grub failure​

See Recover From Grub Failure

If your system was installed on ZFS using legacy BIOS boot before the Proxmox VE 6.4 ISO, incompatibilities between the ZFS implementation in grub and newer ZFS versions can lead to a broken boot. Check the article on switching to proxmox-boot-tool ZFS: Switch Legacy-Boot to Proxmox Boot Tool for more details.
 
Last edited:
For my understanding;

I had hosts on which the message “System booted in EFI-mode but ‘grub-efi-amd64’ meta-package not installed!” appeared during the update.

[ -d /sys/firmware/efi ] && apt install grub-efi-amd64
worked fine here.

Now I have systems (ZFS root, not LVM) that don't show the message, boot via EFI, /boot/efi is empty and grub-pc is installed, but boot without problems.

proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
5091-500E is configured with: uefi (versions: 6.2.16-15-pve, 6.2.16-20-pve, 6.8.12-4-pve)
5091-C640 is configured with: uefi (versions: 6.2.16-15-pve, 6.2.16-20-pve, 6.8.12-4-pve)

[ -d /sys/firmware/efi ] && apt install grub-efi-amd64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
grub-pc
The following NEW packages will be installed:
grub-efi-amd64
0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 45.7 kB of archives.
After this operation, 384 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

ll /boot/efi
total 0


Should grub-efi-amd64 still be installed for the future, or does it not matter in this case / on this systems?
 
yes, it should also be installed since the managed ESP contains a copy of it that might otherwise be(come) outdated..
 
  • Like
Reactions: tomgem
After update proxmox-kernel-helper_8.1.1_all.deb I got following messages:

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'

Now worried to reboot. Any hints or thoughts? What to verify?

Booting from the HPE NS204i-p Gen10+ Boot Controller, which has 3 partitions:
Bash: 
root@pve4:/# fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 447.07 GiB, 480036519936 bytes, 937571328 sectors
Disk model: HPE NS204i-p Gen10+ Boot Controller     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: EFB28272-CB2F-40CA-A76B-94D929A5CD32

Device           Start       End   Sectors   Size Type
/dev/nvme0n1p1      34      2047      2014  1007K BIOS boot
/dev/nvme0n1p2    2048   2099199   2097152     1G EFI System
/dev/nvme0n1p3 2099200 937571294 935472095 446.1G Linux LVM

Bash: 
root@pve4:/# efibootmgr -v
BootCurrent: 001B
Timeout: 20 seconds
BootOrder: 001B,000E,0010,0011,0012,0013,0009,000A,000B,000C,000D,0000,0001,0002,0003,0004,0005,0006,0007,0008,000F,0016,0017,0014,0015,0018,0019
Boot0000* System Utilities      FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(1fd631e5-44e0-2f91-10ab-f88f3568ef30)
Boot0001  Non bootable Hotkey   FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(4affaab0-1376-44b4-9c6e-e92388751bc6)
Boot0002  Intelligent Provisioning      FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(4a433501-ddaa-490b-96b2-04f42d8669b8)
Boot0003  Embedded UEFI Shell   FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(c57ad6b7-0515-40a8-9d21-551652854e37)
Boot0004  Embedded iPXE FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(e22ad661-333a-4452-a101-64cc1898b837)
Boot0005  Diagnose Error        FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(0849279d-40d5-53ea-e764-2496766f9844)
Boot0006  Boot Menu     FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(d3fd6286-43c5-bb8d-0793-07b70aa9de36)
Boot0007  Network Boot  FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(0334f316-c276-49f6-9879-aaf1ecffa5d5)
Boot0008  View Integrated Management Log        FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(93c92423-d1c6-4286-be67-b76b6671047e)
Boot0009  View GUI mode Integrated Management Log       FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(f77778ab-a777-7777-9c58-60b5f0cba9d4)
Boot000A  View BIOS Event Log   FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(c20a40f3-4f7f-b41f-f614-628093c6b567)
Boot000B  HTTP Boot     FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(3f770860-3d63-4803-9ea3-df37144ab546)
Boot000C  PXE Boot      FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(ee8b26b0-37e9-11e1-b86c-0800200c9a66)
Boot000D  Embedded Diagnostics  FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(b57fe6f1-4f49-d46e-4bba-0a8add34d2f3)
Boot000E* Generic USB Boot      UsbClass(ffff,ffff,255,255)
Boot000F* Slot 1 : HPE NS204i-p Gen10+ Boot Controller  PciRoot(0x1)/Pci(0x2,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-50-43-DC-05-00-00-01)N.....YM....R,Y.
Boot0010* Storage Slot 12 : HPE MR216i-a Gen10+ - Box 1, Bay 1  PciRoot(0x4)/Pci(0x2,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/SCSI(1,0)N.....YM....R,Y.
Boot0011* Storage Slot 12 : HPE MR216i-a Gen10+ - Box 1, Bay 2  PciRoot(0x4)/Pci(0x2,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/SCSI(2,0)N.....YM....R,Y.
Boot0012* Storage Slot 12 : HPE MR216i-a Gen10+ - Box 1, Bay 3  PciRoot(0x4)/Pci(0x2,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/SCSI(3,0)N.....YM....R,Y.
Boot0013* Storage Slot 12 : HPE MR216i-a Gen10+ - Box 1, Bay 4  PciRoot(0x4)/Pci(0x2,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/SCSI(4,0)N.....YM....R,Y.
Boot0014* OCP Slot 10 Port 1 : Broadcom NetXtreme-E 2Px10GBASE-T OCP 3.0 Ethernet - NIC (PXE IPv6)   PciRoot(0x4)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00620bb13d00,1)/IPv6([::]:<->[::]:,0,0)N.....YM....R,Y.
Boot0015* OCP Slot 10 Port 1 : Broadcom NetXtreme-E 2Px10GBASE-T OCP 3.0 Ethernet - NIC (HTTP(S) IPv6)PciRoot(0x4)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00620bb13d00,1)/IPv6([::]:<->[::]:,0,0)/Uri()N.....YM....R,Y.
Boot0016* OCP Slot 10 Port 1 : Broadcom NetXtreme-E 2Px10GBASE-T OCP 3.0 Ethernet - NIC (HTTP(S) IPv4)PciRoot(0x4)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00620bb13d00,1)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()N.....YM....R,Y.
Boot0017* OCP Slot 10 Port 1 : Broadcom NetXtreme-E 2Px10GBASE-T OCP 3.0 Ethernet - NIC (PXE IPv4)   PciRoot(0x4)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00620bb13d00,1)/IPv4(0.0.0.00.0.0.0,0,0)N.....YM....R,Y.
Boot0018* Storage Slot 12 : HPE MR216i-a Gen10+ - Box 1, Bay 5  PciRoot(0x4)/Pci(0x2,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/SCSI(5,0)N.....YM....R,Y.
Boot0019* Storage Slot 12 : HPE MR216i-a Gen10+ - Box 1, Bay 6  PciRoot(0x4)/Pci(0x2,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/SCSI(6,0)N.....YM....R,Y.
Boot001B* proxmox       HD(2,GPT,0d7cf343-5b18-4fd9-967a-a8410f9b37d0,0x800,0x200000)/File(\EFI\proxmox\shimx64.efi)
[/CODE=bash]
 
simple follow the steps listed in the warning before rebooting.
 
Read this thread as to why you got that message.

1. Complete those instructions as instructed - before rebooting.
2. I'd also check the command proxmox-boot-tool status - before rebooting.
 
gfngfn256 said:
Read this thread as to why you got that message.

1. Complete those instructions as instructed - before rebooting.
2. I'd also check the command proxmox-boot-tool status - before rebooting.
Click to expand...
Bash: 
root@pve4:/# 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 0 B/45.7 kB of archives.
After this operation, 0 B of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 62683 files and directories currently installed.)
Preparing to unpack .../grub-efi-amd64_2.06-13+pmx5_amd64.deb ...
Unpacking grub-efi-amd64 (2.06-13+pmx5) over (2.06-13+pmx5) ...
Setting up grub-efi-amd64 (2.06-13+pmx5) ...
Installing for x86_64-efi platform.
File descriptor 3 (pipe:[30994077]) leaked on vgs invocation. Parent PID 2342610: grub-install.real
File descriptor 3 (pipe:[30994077]) leaked on vgs invocation. Parent PID 2342610: grub-install.real
Installation finished. No error reported.
Generating grub configuration file ...
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
Adding boot menu entry for UEFI Firmware Settings ...
done
Processing triggers for shim-signed:amd64 (1.44+pmx1+15.8-1+pmx1) ...
root@pve4:/# efibootmgr -v
BootCurrent: 001B
Timeout: 20 seconds
BootOrder: 001B,000E,0010,0011,0012,0013,0009,000A,000B,000C,000D,0000,0001,0002,0003,0004,0005,0006,0007,0008,000F,0016,0017,0014,0015,0018,0019
Boot0000* System Utilities      FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(1fd631e5-44e0-2f91-10ab-f88f3568ef30)
Boot0001  Non bootable Hotkey   FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(4affaab0-1376-44b4-9c6e-e92388751bc6)
Boot0002  Intelligent Provisioning      FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(4a433501-ddaa-490b-96b2-04f42d8669b8)
Boot0003  Embedded UEFI Shell   FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(c57ad6b7-0515-40a8-9d21-551652854e37)
Boot0004  Embedded iPXE FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(e22ad661-333a-4452-a101-64cc1898b837)
Boot0005  Diagnose Error        FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(0849279d-40d5-53ea-e764-2496766f9844)
Boot0006  Boot Menu     FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(d3fd6286-43c5-bb8d-0793-07b70aa9de36)
Boot0007  Network Boot  FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(0334f316-c276-49f6-9879-aaf1ecffa5d5)
Boot0008  View Integrated Management Log        FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(93c92423-d1c6-4286-be67-b76b6671047e)
Boot0009  View GUI mode Integrated Management Log       FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(f77778ab-a777-7777-9c58-60b5f0cba9d4)
Boot000A  View BIOS Event Log   FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(c20a40f3-4f7f-b41f-f614-628093c6b567)
Boot000B  HTTP Boot     FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(3f770860-3d63-4803-9ea3-df37144ab546)
Boot000C  PXE Boot      FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(ee8b26b0-37e9-11e1-b86c-0800200c9a66)
Boot000D  Embedded Diagnostics  FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(b57fe6f1-4f49-d46e-4bba-0a8add34d2f3)
Boot000E* Generic USB Boot      UsbClass(ffff,ffff,255,255)
Boot000F* Slot 1 : HPE NS204i-p Gen10+ Boot Controller  PciRoot(0x1)/Pci(0x2,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-50-43-DC-05-00-00-01)N.....YM....R,Y.
Boot0010* Storage Slot 12 : HPE MR216i-a Gen10+ - Box 1, Bay 1  PciRoot(0x4)/Pci(0x2,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/SCSI(1,0)N.....YM....R,Y.
Boot0011* Storage Slot 12 : HPE MR216i-a Gen10+ - Box 1, Bay 2  PciRoot(0x4)/Pci(0x2,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/SCSI(2,0)N.....YM....R,Y.
Boot0012* Storage Slot 12 : HPE MR216i-a Gen10+ - Box 1, Bay 3  PciRoot(0x4)/Pci(0x2,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/SCSI(3,0)N.....YM....R,Y.
Boot0013* Storage Slot 12 : HPE MR216i-a Gen10+ - Box 1, Bay 4  PciRoot(0x4)/Pci(0x2,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/SCSI(4,0)N.....YM....R,Y.
Boot0014* OCP Slot 10 Port 1 : Broadcom NetXtreme-E 2Px10GBASE-T OCP 3.0 Ethernet - NIC (PXE IPv6)      PciRoot(0x4)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00620bb13d00,1)/IPv6([::]:<->[::]:,0,0)N.....YM....R,Y.
Boot0015* OCP Slot 10 Port 1 : Broadcom NetXtreme-E 2Px10GBASE-T OCP 3.0 Ethernet - NIC (HTTP(S) IPv6)  PciRoot(0x4)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00620bb13d00,1)/IPv6([::]:<->[::]:,0,0)/Uri()N.....YM....R,Y.
Boot0016* OCP Slot 10 Port 1 : Broadcom NetXtreme-E 2Px10GBASE-T OCP 3.0 Ethernet - NIC (HTTP(S) IPv4)  PciRoot(0x4)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00620bb13d00,1)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()N.....YM....R,Y.
Boot0017* OCP Slot 10 Port 1 : Broadcom NetXtreme-E 2Px10GBASE-T OCP 3.0 Ethernet - NIC (PXE IPv4)      PciRoot(0x4)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00620bb13d00,1)/IPv4(0.0.0.00.0.0.0,0,0)N.....YM....R,Y.
Boot0018* Storage Slot 12 : HPE MR216i-a Gen10+ - Box 1, Bay 5  PciRoot(0x4)/Pci(0x2,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/SCSI(5,0)N.....YM....R,Y.
Boot0019* Storage Slot 12 : HPE MR216i-a Gen10+ - Box 1, Bay 6  PciRoot(0x4)/Pci(0x2,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/SCSI(6,0)N.....YM....R,Y.
Boot001B* proxmox       HD(2,GPT,0d7cf343-5b18-4fd9-967a-a8410f9b37d0,0x800,0x200000)/File(\EFI\proxmox\shimx64.efi)

Bash: 
root@pve4:/# 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.

Anything else I can check?
 
You must log in or register to reply here.
Top Bottom