I recently ran into trouble where grub broke on me, no longer showing the boot menu and dropping to a
I was able to get it working after fixing the missing
I really like the proxmox-boot-tool CLI interface, as it seems simpler and more reliable. So that got me wondering:
grub> prompt. After some troubleshooting, I found https://pve.proxmox.com/wiki/ZFS:_S...iring_a_System_Stuck_in_the_GRUB_Rescue_Shell and decided to switch.I was able to get it working after fixing the missing
/etc/kernel/cmdline file and setting the root and boot parameters (thanks @Stoiko Ivanov !): https://forum.proxmox.com/threads/z...s-no-root-device-specified.64147/#post-290914I really like the proxmox-boot-tool CLI interface, as it seems simpler and more reliable. So that got me wondering:
- Should the install on Debian guides such as https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm be updated to recommend switching to proxmox-boot-tool? Should that recommendation specifically focus on ZFS users?
- I'm assuming a normal proxmox install creates /etc/kernel/cmdline and this isn't a bug. In that case, should https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool be updated to mention creating that file, and https://pve.proxmox.com/wiki/Host_Bootloader updated with an example cmdline for ZFS?
Last edited: