From: Marco Gaiarin <gaio@lilliput.linux.it>
To: Alwin Antreich via pve-user <pve-user@lists.proxmox.com>
Cc: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] ZFS Upgrade...
Date: Tue, 30 Sep 2025 18:37:44 +0200 [thread overview]
Message-ID: <mjdtql-h1n2.ln1@leia.lilliput.linux.it> (raw)
In-Reply-To: <mailman.451.1758987174.390.pve-user@lists.proxmox.com>; from SmartGate on Tue, Sep 30, 2025 at 22:06:10PM +0200
Mandi! Alwin Antreich via pve-user
In chel di` si favelave...
>>So, implicitly you confirm that it is GRUB that have some incompatibilities,
>>not GRUB in legacy mode... I've understood well?
> To my understanding, yes. Historically grub didn't (or still doesn't) support all features of a zfs pool on root. That's why the installer selects grub or systemd-boot [0] depending on system.
So, practically:
1) if i use systemd-boot i'm safe and i can safely upgrade boot zpool
2) if i use GRUB, both in:
2a) legacy
or
2b) UEFI
mode, i'm in danger and if i upgrade boot pool, system get unbootable.
Clearly, if i have a system taht boot in UEFI GRUB, i can upgrade bootloader
to systemd-boot (How?).
Correct? Thanks.
--
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2025-09-30 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 13:59 Marco Gaiarin
2025-09-22 14:21 ` Marco Gaiarin
2025-09-23 12:52 ` Alwin Antreich via pve-user
[not found] ` <58420306b884238ed47ae0a5b2c69913bd131ebb@antreich.com>
2025-09-24 16:18 ` Marco Gaiarin
2025-09-27 15:32 ` Alwin Antreich via pve-user
2025-09-30 16:37 ` Marco Gaiarin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mjdtql-h1n2.ln1@leia.lilliput.linux.it \
--to=gaio@lilliput.linux.it \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox