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

推荐订阅源

G
Google Developers Blog
Apple Machine Learning Research
Apple Machine Learning Research
小众软件
小众软件
Recent Announcements
Recent Announcements
阮一峰的网络日志
阮一峰的网络日志
IT之家
IT之家
A
About on SuperTechFans
量子位
Engineering at Meta
Engineering at Meta
B
Blog
The Cloudflare Blog
博客园 - 【当耐特】
Hugging Face - Blog
Hugging Face - Blog
Y
Y Combinator Blog
J
Java Code Geeks
D
DataBreaches.Net
aimingoo的专栏
aimingoo的专栏
T
Tailwind CSS Blog
H
Help Net Security
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
V2EX
Stack Overflow Blog
Stack Overflow Blog
C
Check Point Blog
酷 壳 – CoolShell
酷 壳 – CoolShell

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
[SOLVED] - Issue booting into GRUB after upgrade from Pro...
invalid@exam · 2026-06-18 · via Proxmox Support Forum

Hello,

I recently upgraded my main Proxmox node from version 8 to 9, following carefully all prerequisites and steps listed in the official guide: Upgrade from 8 to 9.

After the upgrade, upon reboot, I was dropped to the GRUB prompt (grub>), instead of the normal boot menu. Attempting ls showed my LVM volumes correctly, but insmod normal failed to load, and the menu never appeared.

To regain access, I used the manual kernel boot method: I set the root to my LVM volume, loaded the latest kernel (6.17), loaded the corresponding initramfs, and booted successfully. This allowed me to start the Proxmox node and access the system.

I have not yet performed any permanent GRUB repair. Now that I can boot, what is the recommended procedure to permanently fix GRUB after such an upgrade?

Thanks!

Proxmox VE 8 → 9 Upgrade – GRUB fails to boot on UEFI + LVM

After upgrading a Proxmox VE node from PVE 8 to PVE 9 in UEFI mode with root on LVM, the system dropped to a grub> prompt on reboot. This is a known issue.

------------------------------------------
Temporary boot from GRUB

At the grub> prompt:

Bash:

set root=(lvm/pve-root)
ls /boot
linux /boot/vmlinuz-6.17.4-1-pve root=/dev/mapper/pve-root ro quiet
initrd /boot/initrd.img-6.17.4-1-pve
boot

This boots the node successfully.

------------------------------------------
Permanent fix

Once booted, run:

Bash:

[ -d /sys/firmware/efi ] && echo "UEFI OK"

grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=proxmox --recheck
update-grub
shutdown -r now

After reboot, GRUB loads normally and the node boots automatically.

------------------------------------------
Verification

Bash:

uname -r            # latest kernel
efibootmgr -v       # BootCurrent points to \EFI\proxmox\grubx64.efi
pveversion -v       # confirms PVE 9 running

------------------------------------------
Cause: The correct GRUB package was installed, but the UEFI firmware was still booting an old/incorrect GRUB entry. grub-install ensures the fixed version is used.

Hello,

I have the same issue and the fix proposed by @Carizoeuf partially solved my issue:

  • I don't have the grub prompt but I am able to boot on proxmox by using the "rescue boot" via the installation iso
  • Then I pass both command:
    • grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=proxmox --recheck
    • update-grub
  • and then I have to go in the BIOS to change the BBS priorities and select proxmox
  • Everything is then solved until I power off the server (and remove the power plug) and I have to redo all the steps

I am a bit lost on how to fix this and any help would be greatly appreciated.

Thanks!

Hello,

I have the same issue and the fix proposed by @Carizoeuf partially solved my issue:

  • I don't have the grub prompt but I am able to boot on proxmox by using the "rescue boot" via the installation iso
  • Then I pass both command:
    • grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=proxmox --recheck
    • update-grub
  • and then I have to go in the BIOS to change the BBS priorities and select proxmox
  • Everything is then solved until I power off the server (and remove the power plug) and I have to redo all the steps

I am a bit lost on how to fix this and any help would be greatly appreciated.

Thanks!

Same issue