What now? - Please avoid using zpool upgrade on the "rpool" (root pool) itself, when upgrading to ZFS 2.0

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
7,199
1,134
164
It is sad to see that by default proxmox still doesnt put grub on both vdev mirror's meaning if disk 1 fails I dont think proxmox would boot,
You need to initialize and configure each ESP for booting from grub if you do this after first setting up the system (the PVE ISO since 6.4 does install grub on all disks used for rpool if you install on ZFS and boot with legacy bios)

`proxmox-boot-tool init /dev/disk/by-id/XXXX-XXXX`

I hope this helps
 

chrcoluk

Member
Oct 7, 2018
127
18
23
43
You need to initialize and configure each ESP for booting from grub if you do this after first setting up the system (the PVE ISO since 6.4 does install grub on all disks used for rpool if you install on ZFS and boot with legacy bios)

`proxmox-boot-tool init /dev/disk/by-id/XXXX-XXXX`

I hope this helps

Thank you for confirming the grub problem is fixed in newer versions of proxmox.
 
  • Like
Reactions: Stoiko Ivanov

His.Dudeness

Member
Mar 8, 2020
45
2
13
Hi! I am still nor sure if I can upgrade my zfs pool safely. I think my PVE was initially installed with 6.0 but not 100% sure.

"efibootmgr -v" shows the following:

Code:
BootCurrent: 000E
Timeout: 1 seconds
BootOrder: 0005,000E,000A,000F,0010,0011,0012,000C,0006,0004,0001,0003,0002,0000,000B,0009
Boot0000* XCP-ng        VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0001* Linux Boot Manager    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0002* Linux Boot Manager    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0003* Linux Boot Manager    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0004* Linux Boot Manager    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0005* UEFI: Built-in EFI Shell      VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0006* Linux Boot Manager    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0009* Linux Boot Manager    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot000A* Linux Boot Manager    HD(2,GPT,da5b9a46-70d2-4862-b3f6-d53da88c311e,0x800,0x100000)/File(\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI)
Boot000B* Linux Boot Manager    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot000C* Linux Boot Manager    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot000E* Linux Boot Manager    HD(2,GPT,c171f481-a291-4acd-8827-ebc90b57cb0f,0x800,0x100000)/File(\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI)
Boot000F* UEFI OS       HD(2,GPT,da5b9a46-70d2-4862-b3f6-d53da88c311e,0x800,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0010* UEFI OS       HD(2,GPT,c171f481-a291-4acd-8827-ebc90b57cb0f,0x800,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0011* Hard Drive    BBS(HD,,0x0)..GO..NO........u.H.i.t.a.c.h.i. .H.C.C.5.4.3.2.1.6.A.7.A.3.8.0....................A.................................>..Gd-.;.A..MQ..L. . . . . . .2.E.1.0.2.4.1.4.4.G.V.T.D.X........BO..NO........u.H.i.t.a.c.h.i. .H.C.C.5.4.3.2.1.6.A.7.A.3.8.0....................A.................................>..Gd-.;.A..MQ..L. . . . . . .2.E.2.0.2.4.2.4.S.C.6.V.J.A........BO..NO........u.M.i.c.r.o.n._.5.2.0.0._.M.T.F.D.D.A.K.9.6.0.T.D.D....................A.................................>..Gd-.;.A..MQ..L. . . . . . . . .9.1.4.4.5.2.7.1.6.A.3.8........BO..NO........u.M.i.c.r.o.n._.5.2.0.0._.M.T.F.D.D.A.K.9.6.0.T.D.D....................A.................................>..Gd-.;.A..MQ..L. . . . . . . . .9.1.4.4.5.2.7.1.7.A.0.2........BO
Boot0012* USB   BBS(USB,,0x0)..GO..NO........i.A.M.I. .V.i.r.t.u.a.l. .C.D.R.O.M.0. .1...0.0....................A...................................0..Gd-.;.A..MQ..L.A.A.A.A.B.B.B.B.C.C.C.C.1........BO..NO........i.A.M.I. .V.i.r.t.u.a.l. .F.l.o.p.p.y.0. .1...0.0....................A...................................0..Gd-.;.A..MQ..L.A.A.A.A.B.B.B.B.C.C.C.C.2........BO..NO........i.A.M.I. .V.i.r.t.u.a.l. .H.D.i.s.k.0. .1...0.0....................A...................................0..Gd-.;.A..MQ..L.A.A.A.A.B.B.B.B.C.C.C.C.3........BO

"proxmox-boot-tool status" shows:

Code:
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
979B-0C57 is configured with: uefi (versions: 5.4.128-1-pve, 5.4.78-1-pve)
979C-2F35 is configured with: uefi (versions: 5.4.128-1-pve, 5.4.78-1-pve)

Is it safe to issue a "zpool upgrade" or will my PVE explode ? :eek:

cheers and thanks a lot
Michael
 

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
7,199
1,134
164
"proxmox-boot-tool status" shows:

Code:
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
979B-0C57 is configured with: uefi (versions: 5.4.128-1-pve, 5.4.78-1-pve)
979C-2F35 is configured with: uefi (versions: 5.4.128-1-pve, 5.4.78-1-pve)
this looks on the first glance as if the system is correctly configured to boot with systemd-boot (and thus not affected of the grub-compatibility issues, which prevent the zpool upgrade in the first place)

As always - make sure you have a working backup before trying to reconfigure stuff which might render your system unbootable)
once you have that - I'd say - happy upgrading :)
 

His.Dudeness

Member
Mar 8, 2020
45
2
13
this looks on the first glance as if the system is correctly configured to boot with systemd-boot (and thus not affected of the grub-compatibility issues, which prevent the zpool upgrade in the first place)

As always - make sure you have a working backup before trying to reconfigure stuff which might render your system unbootable)
once you have that - I'd say - happy upgrading :)

Just upgraded rpool and my data pool for the VMs everything worked fine :cool:

Thanks you very much !! :)
 
  • Like
Reactions: Stoiko Ivanov

Tim Hörnle - UJAM

New Member
Jul 26, 2021
9
0
1
27
So what is the final recommendation here? Should I try to switch to EFI boot or is everything working fine now on the newest version?

I installed Proxmox via legacy boot and before version 6.4. Now I successfully updated to 7.1 and the "Legacy Boot Tool". So is that safe to upgrade?
 

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
7,199
1,134
164
So what is the final recommendation here? Should I try to switch to EFI boot or is everything working fine now on the newest version?
As described in the wiki-page:
https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool

check with `proxmox-boot-tool status` what's the current situation with your system
if you're not using proxmox-boot-tool, you should not upgrade your rpool with `zpool upgrade` as this might render the system unbootable - the conditions are laid out in:
https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#Background

I hope this explains it
 

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 your own in 60 seconds.

Buy now!