惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

GbyAI
GbyAI
Y
Y Combinator Blog
F
Fortinet All Blogs
H
Hackread – Cybersecurity News, Data Breaches, AI and More
N
Netflix TechBlog - Medium
T
Tailwind CSS Blog
aimingoo的专栏
aimingoo的专栏
博客园 - Franky
T
The Blog of Author Tim Ferriss
D
DataBreaches.Net
量子位
博客园 - 三生石上(FineUI控件)
I
InfoQ
Engineering at Meta
Engineering at Meta
WordPress大学
WordPress大学
阮一峰的网络日志
阮一峰的网络日志
爱范儿
爱范儿
D
Docker
美团技术团队
雷峰网
雷峰网
U
Unit 42
Stack Overflow Blog
Stack Overflow Blog
Recent Announcements
Recent Announcements
人人都是产品经理
人人都是产品经理

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
PVE8to9 systemd-boot error AFTER Upgrade
invalid@exam · 2026-06-19 · via Proxmox Support Forum

I decided to upgrade to PVE 9 and have made a mistake along the way.

My boot disk is running ZFS so the host is using systemd-boot and proxmox-boot-tool. I did not remove systemd-boot before the upgrade so after upgrading I am on PVE 9.2.3 with kernel 7.0.6-2-pve. I have rebooted since upgrading.

If I run pve8to9 I see:
FAIL: systemd-boot meta-package installed. This will cause problems on upgrades of other boot-related packages. Remove 'systemd-boot' See:
[URL]https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#sd-boot-warning[/URL]for more information.

Running efibootmgr -v I can see:
BootCurrent: 0016 and
Boot0016* Linux Boot Manager HD(2,GPT,6ef0129c-85a0-4a49-afba-76d18360cd61,0x800,0x200000)/File(\EFI\systemd\[B]systemd-bootx64[/B].efi)1400000049535048.

Running proxmox-boot-tool status:
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
7283-83DD is configured with: uefi (versions: 6.8.12-29-pve, 7.0.6-2-pve)

From every related post and information I have seen I haven't been able to figure out what I should do in this situation. I unfortunately don't have a snapshot of my rpool from before the upgrade (lesson learned).

I haven't been able to find an example with my specific circumstances, is it safe to run the following to get rid of the pve8to9 FAIL message?
apt install systemd-boot-efi systemd-boot-tools
apt remove systemd-boot
apt purge systemd-boot

Any and all input is appreciated :)