Problem
Running
Solution
I double checked that the correct / expected versions were installed, comparing against another system (they were).
I also checked to see which were marked as manual or automatic.
Since the running version obviously didn't match the supposedly installed version, I just reinstalled them.
And marked
I'm still not sure how this happened. I did check
Backstory
I'm on a system that, if I remember correctly, was fresh-installed with Proxmox VE 7 and then upgraded to 8 and just recently 9.
My reason for needing to run
On another system in the cluster, which as far as I can recall is identical and has gone through identical configuration and upgrade process (other than being a few days apart), I didn't have this problem, so that's what I used for comparison.
Running
update-initramfs resulted in an error from bootctl (as does running bootctl directly).
Code:
update-initramfs -u -k all
Code:
bootctl: error while loading shared libraries: libsystemd-shared-252.so: cannot open shared object file: No such file or directorySolution
I double checked that the correct / expected versions were installed, comparing against another system (they were).
Code:
dpkg -l | grep -E 'systemd|libsystemd'I also checked to see which were marked as manual or automatic.
Code:
apt-mark showauto | grep systemd
Code:
apt-mark showmanual | grep systemdSince the running version obviously didn't match the supposedly installed version, I just reinstalled them.
Code:
apt-get install --reinstall systemd-boot-tools
apt-get install --reinstall systemd-boot systemd-boot-efiAnd marked
systemd-boot-tools as auto again.
Code:
apt-mark auto systemd-boot-toolsI'm still not sure how this happened. I did check
/etc/apt/sources.list.d/ to make sure I didn't cross repos by mistake when upgrading. It all looked good - the same as on the working system, so I just deleted the backups to keep it tidy.Backstory
I'm on a system that, if I remember correctly, was fresh-installed with Proxmox VE 7 and then upgraded to 8 and just recently 9.
My reason for needing to run
update-initramfs manually was that I recently added ZFS storage and found that the RAM usage was very high, which turned out to be due to having started from v7 and retaining the old defaults, which I was fixing as per https://pve.proxmox.com/wiki/ZFS_on_Linux.On another system in the cluster, which as far as I can recall is identical and has gone through identical configuration and upgrade process (other than being a few days apart), I didn't have this problem, so that's what I used for comparison.
