From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: applied: [RFC kernel-helper] proxmox-boot: find root dev for grub default entry as update-grub does
Date: Tue, 20 Oct 2026 20:50:43 +0200 [thread overview]
Message-ID: <179252224008.23374.11078416506300426282.b4-ty@b4> (raw)
In-Reply-To: <20261012201501.977578-1-s.ivanov@proxmox.com>
On Mon, 12 Oct 2026 22:11:08 +0200, Stoiko Ivanov wrote:
> Reading the ID that update-grub/grub-mkconfig uses for generating
> unique ids for boot-entries from the existing grub.cfg breaks if the
> following update-grub call changes the device id, effectively
> rendering the pin setting useless.
>
> Reported in our community-forum in context of renamed /dev/nvmeXnYpZ:
> https://forum.proxmox.com/threads/186882/
>
> [...]
Applied with some smaller fixups folded in (see commit message trailer),
thanks!
[1/1] proxmox-boot: find root dev for grub default entry as update-grub does
commit: dd37f595127f9c48b7140100dae8f794a026a14b
prev parent reply other threads:[~2026-10-20 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 20:11 [RFC kernel-helper] proxmox-boot: find root dev for grub default entry as update-grub does Stoiko Ivanov
2026-10-20 18:50 ` Thomas Lamprecht [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=179252224008.23374.11078416506300426282.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@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