Legacy or UEFI?

killmasta93

Renowned Member
Aug 13, 2017
973
58
68
31
Hi
recently installed proxmox latest iso on dell r720 with Bios on legacy mode. Everything went well and when it started the boot it shows the blue screen, As normally on uefi it shows the blackscreen. But i was updating a config and i saw that the boot was uefi. This is what i did
so not sure why it says efiboot when the bios is on legacy and when it boots up it shows the bluescreen

Thank you

Code:
root@prometheus:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.34-1-pve
Running hook script 'zz-pve-efiboot'..
Re-executing '/etc/kernel/postinst.d/zz-pve-efiboot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/8AF2-7BF7
    Copying kernel and creating boot-entry for 5.4.34-1-pve
Copying and configuring kernels on /dev/disk/by-uuid/8AF3-4DB9
    Copying kernel and creating boot-entry for 5.4.34-1-pve
root@prometheus:~# zfs list
NAME               USED  AVAIL     REFER  MOUNTPOINT
rpool              942M  7.02T      104K  /rpool
rpool/ROOT         940M  7.02T       96K  /rpool/ROOT
rpool/ROOT/pve-1   940M  7.02T      940M  /
rpool/data          96K  7.02T       96K  /rpool/data
root@prometheus:~# ls /b
bin/  boot/
root@prometheus:~# ls /boot/
config-5.4.34-1-pve       grub/                     memtest86+.bin            pve/                      vmlinuz-5.4.34-1-pve     
efi/                      initrd.img-5.4.34-1-pve   memtest86+_multiboot.bin  System.map-5.4.34-1-pve   
root@prometheus:~# ls /boot/grub/
fonts  grub.cfg  grubenv  i386-pc  locale  unicode.pf2
 
Something in your configuration might have created the file '/etc/kernel/pve-efiboot-uuid' - can you post it's contents, as well as lsblk -f?

In general though, if it is working and you do indeed boot into new kernels after they're installed (verify with uname -a) then this should be a non-issue and you can most likely just ignore the output.
 
Thanks for the reply,
what i ran
Code:
update-initramfs -u

Code:
root@prometheus:~# cat /etc/kernel/pve-efiboot-uuids
8AF2-7BF7
8AF3-4DB9

Code:
root@prometheus:~# lsblk -f
NAME FSTYPE LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda  zfs_me rpool 7344873492832984806
├─sda1
│    zfs_me rpool 7344873492832984806
├─sda2
│    vfat   rpool 8AF2-7BF7
└─sda3
     zfs_me rpool 7344873492832984806
sdb  zfs_me rpool 7344873492832984806
├─sdb1
│    zfs_me rpool 7344873492832984806
├─sdb2
│    vfat   rpool 8AF3-4DB9
└─sdb3
     zfs_me rpool 7344873492832984806
sdc
├─sdc1
│    zfs_me rpool 7344873492832984806
└─sdc9

sdd
├─sdd1
│    zfs_me rpool 7344873492832984806
└─sdd9

sde
├─sde1
│    zfs_me rpool 7344873492832984806
└─sde9

sdf
├─sdf1
│    zfs_me rpool 7344873492832984806
└─sdf9

sdg
├─sdg1
│    zfs_me rpool 7344873492832984806
└─sdg9

sdh
├─sdh1
│    zfs_me rpool 7344873492832984806
└─sdh9

sr0
zd16
zd32
 
Last edited:
Yes, our installer might have detected an UEFI boot for some reason (wrongly, as you suggest), but we still install the regular bootloader as well, so this is a non-issue. I suppose just be happy that you could technically switch to UEFI boot and everything should still work :)
 
  • Like
Reactions: killmasta93
Thanks for the reply, so its still uses legacy? because lets say one of the disks fails which has the grub would i just

Code:
pve-efiboot-tool format /dev/sde2 --force
 pve-efiboot-tool init /dev/sde2 --force

pve-efiboot-tool refresh

or as the normal legacy

Code:
grub-install /dev/sda

thank you
 
For failover you have to use UEFI boot, GRUB is only installed on the first disk. The pve-efiboot-tool only works for UEFI boots too. Keep in mind that in UEFI mode with a ZFS raid we use systemd-boot instead of GRUB. Just using grub-install on a ZFS disk is probably a bad idea.
 
Thanks for the reply, so these are the steps i normally take when a disks fails and i have to replace not sure if its the correct way? assuming the new disk is sda and sdh is the replicate


Code:
sgdisk --replicate=/dev/sda /dev/sdh

sgdisk --randomize-guids /dev/sda


grub-install /dev/sda


 

zpool replace -f rpool 13843703100769424298 /dev/sda2
 
Yes, that should work (though I'd still test it, anything related to desaster-recovery you should usually test on some lab system first).

I'd maybe only install grub *after* the replace (resilvering) is done though, otherwise if you reboot in between you might get stuck trying to boot from a half resilvered disk.
 
thanks for the reply, normally those steps i run when its legacy but when its UEFI i run these steps

but i feel like its using UEFI

Code:
sgdisk <healthy bootable device> -R <new device>
sgdisk -G <new device>
pve-efiboot-tool format /dev/sde2 --force
 pve-efiboot-tool init /dev/sde2 --force

pve-efiboot-tool refresh

then after that i normally get a warning so i need to remove the bad this

Code:
nano /etc/kernel/pve-efiboot-uuids

then replace

Code:
zpool replace -f rpool 4992978537232780967 /dev/sde2

thank you
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!