1. we did fix the issue we could reproduce quite fast
2. despite this long thread, only a (small!) subset of systems is affected, which is the reason why we haven't been able to reproduce the remaining issue at all so far, despite many hours spent by multiple team members on our end
3. rebooting...
its performance and reliablity are not on a level where I would consider using it directly as a datastore. the lock failures are likely (transient?) issues on their end, either ratelimiting or service interruptions.
from which kernel version to which kernel version? were other components/packages upgraded at the same time? do you see other symptoms described in this thread (connections stalling with tiny receive windows)?
I think your issue is that you are running inside a privileged container, which is (nowadays) a kind of exotic environment.. I will see if we can fix this up on the package side, but you might need to implement such a manual workaround.
"grub-install.real: error: cannot find EFI directory."
that sounds like you are missing a mount for the ESP. so yes, your steps look okay, please do them and then post "efibootmgr -v" and any output of the commands you did!
yes, I got a GH notification about it but it was too close to the cutoff for the next point release (this weekend) on the Debian side. I will get it included in unstable and then try to get it backported for Debian 13.4 (which will be cut in March).
is this running inside a container? which kind? if it's a PVE LXC container, could you post the config? the issue that it's not possible to mount the tmpfs:
Dec 26 14:50:29 pbs-vaduz systemd[1]: Mounting run-proxmox\x2dbackup.mount - Mount tmpfs at /run/proxmox-backup...<br>Dec 26 14:50:29...