From: Alwin Antreich via pve-user <pve-user@lists.proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: Alwin Antreich <alwin@antreich.com>
Subject: Re: [PVE-User] ZFS Upgrade...
Date: Sat, 27 Sep 2025 17:32:13 +0200 [thread overview]
Message-ID: <mailman.451.1758987174.390.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <aNQZucwlcpq0wdlu@sv.lnf.it>
[-- Attachment #1: Type: message/rfc822, Size: 4473 bytes --]
From: Alwin Antreich <alwin@antreich.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] ZFS Upgrade...
Date: Sat, 27 Sep 2025 17:32:13 +0200
Message-ID: <A944F0D9-8F9A-4662-9D3E-AB1DF1EA7B2C@antreich.com>
>> If your system is running in EFI mode already, then consider converting to
>> systemd-boot.
>
>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.
Cheers,
Alwin
[0] https://pve.proxmox.com/wiki/Host_Bootloader
Hi,
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2025-09-27 15:33 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 [this message]
2025-09-30 16:37 ` Marco Gaiarin
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=mailman.451.1758987174.390.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=alwin@antreich.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