Web login and SSH broken after upgrade from 8.4 to 9.x

[therealivandrago]

Hi and thanks for the help!

Not sure where I went wrong. I was following __ the proxmox upgrade steps. Ran for about 20 minutes.

Last I recall was running `grub-update` then `reboot` then no more access.

Was smart enough to get a paste bin before I cleared the terminal. https://pastebin.com/mzgXdVbC the password is fsfXjjHAiq

Just want to know where I went wrong so I can fix it. all the VMs are worthless tbh except for the trueNAS install, that one I kinda need.

 

[readyspace]

It seems like the upgrade flipped your host to Debian 13 without a valid PVE repo/key, so APT removed proxmox-ve and friends; then a GRUB 2.12 update + update-grub finished the brick.

You might want to try this - Boot the PVE installer in “Rescue Shell”, mount your root, restore proper PVE 8/9 repos and the Proxmox keyring, then reinstall the bootloader (proxmox-boot-tool or GRUB) and pve-manager.

If your host boots from ZFS, ensure the correct PVE kernel/initramfs is selected before rebooting (avoid mixing generic Debian kernel + ZFS dkms here).

When back up, run pve8to9 and follow the official 8→9 steps end-to-end before another full-upgrade.

Your TrueNAS VM disks shouldn’t be touched by this; once the host boots and PVE stack returns, you should be able to re-start that VM.

All the best.

 

[therealivandrago]

It seems like the upgrade flipped your host to Debian 13 without a valid PVE repo/key, so APT removed proxmox-ve and friends; then a GRUB 2.12 update + update-grub finished the brick.

You might want to try this - Boot the PVE installer in “Rescue Shell”, mount your root, restore proper PVE 8/9 repos and the Proxmox keyring, then reinstall the bootloader (proxmox-boot-tool or GRUB) and pve-manager.

If your host boots from ZFS, ensure the correct PVE kernel/initramfs is selected before rebooting (avoid mixing generic Debian kernel + ZFS dkms here).

When back up, run pve8to9 and follow the official 8→9 steps end-to-end before another full-upgrade.

Your TrueNAS VM disks shouldn’t be touched by this; once the host boots and PVE stack returns, you should be able to re-start that VM.

All the best.

I know how to do maybe half of what you mentioned wish me luck!

p.s. Thank you for the guidance!

 

[therealivandrago]

It seems like the upgrade flipped your host to Debian 13 without a valid PVE repo/key, so APT removed proxmox-ve and friends; then a GRUB 2.12 update + update-grub finished the brick.

You might want to try this - Boot the PVE installer in “Rescue Shell”, mount your root, restore proper PVE 8/9 repos and the Proxmox keyring, then reinstall the bootloader (proxmox-boot-tool or GRUB) and pve-manager.

If your host boots from ZFS, ensure the correct PVE kernel/initramfs is selected before rebooting (avoid mixing generic Debian kernel + ZFS dkms here).

When back up, run pve8to9 and follow the official 8→9 steps end-to-end before another full-upgrade.

Your TrueNAS VM disks shouldn’t be touched by this; once the host boots and PVE stack returns, you should be able to re-start that VM.

All the best.

so far I created the repos based on the proxmox documentation.

I did check the directory where the keyring is and it still exists also.

I also managed to get the /boot/efi reattached to nvmeon1p2 using fstab, prior was seeting /boot not found. I booted into the PVE ISO and then grabbed the drive UUID (figured nvmeon1p2 was the EFI due to the 1G file size) I don't use ZFS to boot so i just ran the following commands to reinstall grub then update grub

I can log into the proxmox console locally only now, the web gui is still down. Also the network is completely not working right now, testing pinging google.com and a internal address both are failing :/

Not sure what next steps to take, funny enough I was doing the upgrade so it could be the same version as a new proxmox machine so I can join them and then setup my 1 - 2 - 3 backup

I also attached some of the journalctl output, seeing pveproxy.service is not found. not sure if that helps