[SOLVED] Proxmox refusing to boot after update/upgrade

[Keyinator]

Today I wanted to update/upgrade my lxcs and proxmox itself. I did the following:
I used this script to update all lxc instances
Afterwards I used the gui's update button to update proxmox.

This is the full output of the upgrade: https://hastebin.com/ruzixoquti.sql
I noticed the following error gzip: stdout: No space left on device

Now the server won't even start and is not pingable.
I booted it into hetzner's rescue mode and was able to chroot into it.
From there I did apt update && apt upgrade -y which updated some packages
Here is a partial excerpt of the log: https://hastebin.com/umupizavub.apache

However, after exiting rescue mode the server is still unresponsible.
This is the space (using df) shown while in rescuemode:


I also noticed that there's no new information on syslog.
The last entry is from 00:33. It is now 2:08 and I have been trying to reboot at least 3 times in this timespan.

Anything I can do in this dire situation?

 

[Dunuin]

According to log your boot partition ran out of space so the new initramfs couldn't be written. You should run an apt autoremove to delete some old kernels and try the apt dist-upgrade again.

 

[Keyinator]

According to log your boot partition ran out of space so the new initramfs couldn't be written. You should run an apt autoremove to delete some old kernels and try the apt dist-upgrade again.

Thanks a lot for the fast reply
But doing that did not download/reinstall any new packages, sadly.

---

About the disk space problem:
I have enough space on my hard drives to extend the volumes.
My partitions look like this: https://hastebin.com/qixuguluve.sql (The screenshot is from after the update mentioned next. So vg0-root had 128G)
What I tried to do first was increase vg0-root space so I did lvextend -L +128G /dev/mapper/vg0-root on the rescue system which worked.

Now I tried reinstalling the package that threw the original distro-error: apt install --reinstall pve-kernel-5.15.39-3-pve which yielded this: https://hastebin.com/ilicilupil.yaml
I find E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device) odd but don't know what to make of it.

Now I rebooted and am still not able to ping the machine
Any more ideas?

Edit: E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device) seems to be an issue because of chroot and is unlikely to be the cause of my issue.
Edit2: Since the current cause seems to be running out of space I want to add one more weird detail: Before updating the storage on the gui showed half full which would be 64G in this case. Imo this would not be enough to run out of space during an update.

---

I FIXED IT

I ordered a kvm on the machine and used the GRUB Loaded to load into an old kernel.
Everything worked from there but I was still unable to install/reinstall dist-upgrade.
With df -h I found that /boot was full. I deleted unused files and the update was working.