proxmox-boot-tool: how to do grub+uefi?

Michael Herf

Active Member
May 31, 2019
12
2
43
49
Replaced a disk in a 4-disk raidz2, but proxmox-boot-tool won't match the configuration with the existing disks. How do I make these match?

It shows:

Code:
# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with legacy bios
044B-xxxx is configured with: uefi (versions: 5.4.106-1-pve, 5.4.73-1-pve), grub (versions: 5.15.149-1-pve, 6.8.8-2-pve, 6.8.8-3-pve)
044C-xxxx is configured with: uefi (versions: 5.4.106-1-pve, 5.4.73-1-pve), grub (versions: 5.15.149-1-pve, 6.8.8-2-pve, 6.8.8-3-pve)
044C-xxxx is configured with: uefi (versions: 5.4.106-1-pve, 5.4.73-1-pve), grub (versions: 5.15.149-1-pve, 6.8.8-2-pve, 6.8.8-3-pve)
F892-xxxx is configured with: grub (versions: 5.15.149-1-pve, 6.8.8-2-pve, 6.8.8-3-pve)

# sgdisk -p /dev/sdd
Number  Start (sector)    End (sector)  Size       Code  Name
   1              34            2047   1007.0 KiB  EF02
   2            2048         1050623   512.0 MiB   EF00
   3         1050624     23437770718   10.9 TiB    BF01

I think the existing disks are using grub for sda1, then uefi for sda2, zfs on sda3 (legacy mode), probably formatted in Proxmox 6.
The newly added disk ("sdd") does not use this scheme, instead seems to have grub on sdd2, or uefi, but not both?

I "dd"-copied sda1 to sdd1 but I don't expect the system would boot off this new disk. Luckily it's the fourth in the array so it probably never will have to.

The pool is a "legacy" boot, was probably formatted with Proxmox 6, now updated to 8. Is there a way to make these disks match?