Wrong kernel installed

[kaipee]

I've just had to restore some VMs on PVE due to power outage creating some corruption on my local-lvm array.

When I restored the PBS VM from a recent backup, I noticed a lot of breakages (since fixed), with apparmor not allowing dhclient, python being broken and upgrades not working.

But one of my primary concerns (and causing the package upgrade failures) was that plain linux-kernel was installed from the Debian repos (installing the proxmox-kernel fixed a lot of things).

I have no idea how this got installed, and still lists as an available package install / upgrade. This has been a long-running instance of PBS, installed originally via the PBS installer.

Any ideas how the wrong kernel got installed, and how I can prevent it from being captured in upcoming upgrades?

 

[Chris]

Hi,
most likely you did install PBS on top of a vanilla Debian installation? In that case the vanilla Debian kernel should be uninstalled, e.g via apt remove linux-image-amd64 'linux-image-6.1*'

 

[kaipee]

Huh, could be correct. Not sure why I would have installed this on plain Debian, I always deploy via ISO installers.

root@pbs:~# history | head -n15
    1  apt install sudo
    2  clear
    3  usermod -aG sudo kaipee
    4  clear
    5  wget https://enterprise.proxmox.com/debian/proxmox-release-bullseye.gpg -O /etc/apt/trusted.gpg.d/proxmox-release-bullseye.gpg
    6  vim /etc/apt/sources.list
    7  apt install vim
    8  vim /etc/apt/sources.list
    9  apt update
   10  clear
   11  apt install proxmox-backup
   12  ip a
   13  reboot now
   14  clear
   15  ip a

Was the ISO installer available 4 years ago? (2022)

root@pbs:~# sudo tune2fs -l $(findmnt / -no source) | grep 'Filesystem created:'

Filesystem created:       Sat Jan 22 07:26:56 2022

 

[Chris]

Was the ISO installer available 4 years ago? (2022)

Yes, at that time PBS v2.1 was available, which was provided as ISO installer image.