Search results

Cool, good to know!

I saw that one too and it looked great except it said it uses serial console by default unless you change some options (which weren't clear to me) and recompile.

I ended up using this: https://qlr.ro/fix-proxmox-zfs-boot-issues-grub-device-not-found/ I did it without using the iso they mentioned because the link is dead. Instead, I used the Proxmox USB's > Advanced Options > Install Proxmox VE (Terminal, Debug) and ctrl + d to a prompt. I had to set...

Not sure how I missed it originally, but esteemed and generous forum member @Kyle did a write up that seems to be exactly what I need. Will try this soon. Thanks Kyle! https://forum.proxmox.com/threads/switching-from-legacy-boot-when-there-is-no-space-for-esp-partition.139479/

This appears to be relevant and discusses moving the boot partition to another drive. Maybe I should do that, run a backup, then reinstall and restore. https://qlr.ro/fix-proxmox-zfs-boot-issues-grub-device-not-found/ Hard to know though because it's not clear to me what the original failure...

Please help me understand what happened and what the end goal is (at a lower level than "make it boot again"). I installed ZFS in my Debian live USB and scrubbed the rpool, which resulted in zero errors found. So, the pool and disks appear fine. Still, it seems there was some kind of...

Here's the result of fdisk -l:

To get an idea of what kind of partitions I'm dealing with according to @fabian's comment, I booted a live Debian from USB and ran lsblk: sda and sdb are my mirrored ZFS disks. sdc is the USB disk. ...from the partitions listed, I conclude that I do not have a big enough ESP for the...

Thanks. I will try that after work today. Is it clear what the problem is? I assumed disk failure but maybe not since theses were mirrored and known healthy as of a few weeks ago. Looks like maybe the "proxmox-boot-tool refresh" command is what I need.

Whoops, looks like I was actually using Proxmox VE 8.2.7.

I also tried the non-recovery image of zfsbootmenu, but to the same effect. I might be making my USB stick wrong. I give up for today.

Sorry, @Kingneutron, I tried zfsbootmenu's recovery image and I don't get it. I formatted a USB stick as FAT32 and dropped the EFI file in EFI/boot/Bootx64.efi, then ran that several different ways via my motherboard's boot menu. Best I can get is that it seems to run the efi file, but...

I am looking into how to boot from the EFI files provided by zfsbootmenu (thanks @Kingneutron)

I tried booting to the Proxmox VE 7.4 iso and found the Rescue Boot option. No success though, it's giving this error:

Hello, Today I rebooted my Proxmox 7 Proxmox VE 8.2.7 server and was greeted with the grub rescue prompt. I have (had?) a 2-disk ZFS mirror configuration, but now it's not booting. I am not experienced with troubleshooting boot issues with ZFS. What should I do? The screenshot shows the...

Thank you for posting your solution! I was backing up to a USB drive before potentially destructive changes and encountered this issue. It had the same solution as you posted.

Whoops, I should clarify that I am not using Proxmox Mail Gateway, but Proxmox VE. I just realized that my web search took me to the Mail Gateway forum and I mistook it for the Proxmox VE forum.

Welp, I just rebooted via ssh and that fixed it. The new password I set for root with passwd is now working to login to the web gui now, whereas it wasn't before. I guess the problem was not the password, but instead something in the login flow breaks over time and a reboot restores it.

Yes, you must tell us what the issue was. This issue just happened to me. Can't get into the web gui login all of a sudden. I still have ssh access so I used the passwd command to change the root password. But that new root password doesn't work either.

I'd like to set up an SSH key for root login. Can I just do this in the regular way by editing the `authorized_keys` file and setting the sshd_config file to not permit password? Or does this risk violating the expectations of the Proxmox engine and causing errors?