Something on your system is blocking. What is the output from clicking the install proxmox kernel button again?
Maybe the GUI is the problem if you have OMV on rpi?
Something on your system is blocking. What is the output from clicking the install proxmox kernel button again?
Maybe the GUI is the problem if you have OMV on rpi?
I re-ran the install, it upgraded it to Debian GNU/Linux, with Linux 5.15.27-1-pve and got rid of some of the packages waiting to install but I still have the following two which appear to be outdated anyways.
pve-headers-5.13 7.1-9
pve-headers-5.13.19-6-pve 5.13.19-14
I tried apt autoremove from putty and it doesn't remove them.
This is not on a pi, it's running on a server class motherboard with a xeon processor and 16GB ECC memory.
Thanks,
Can you show the output of
sudo apt-get upgradeI re-ran the install,
No output?
two which appear to be outdated anyways.
The 5.13 kernel is actually the stable proxmox kernel.
I tried apt autoremove from putty and it doesn't remove them.
The zfs plugin depends on the pve-headers package which is still pointing to the stable pve-headers-5.13 package. They don't hurt anything.
No output?
The 5.13 kernel is actually the stable proxmox kernel.
The zfs plugin depends on the pve-headers package which is still pointing to the stable pve-headers-5.13 package. They don't hurt anything.
I clicked on the install proxmox kernel button again as you initially suggested. This appears to have upgraded the proxmox kernel from 5.13 to 5.15.
Is this how you have to upgrade the proxmox kernal vs. through the Upgrade Management page in the GUI?
If that is the case, why are the 5.13 headers still pending to be installed under Update Management in the GUI?
I've run apt autoremove and it does not remove them.
Here's the output from the initial run of the re-install/upgrade of proxmox, followed by the output of apt autoremove:
Supported kernel found
Get:1 file:/var/cache/openmediavault/archives InRelease
Ign:1 file:/var/cache/openmediavault/archives InRelease
Get:2 file:/var/cache/openmediavault/archives Release
Ign:2 file:/var/cache/openmediavault/archives Release
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Hit:5 http://deb.debian.org/debian bullseye InRelease
Hit:6 https://openmediavault-plugin-…github.io/packages/debian shaitan InRelease
Hit:7 http://security.debian.org/debian-security bullseye-security InRelease
Hit:8 https://openmediavault.github.io/packages shaitan InRelease
Hit:9 http://deb.debian.org/debian bullseye-updates InRelease
Hit:10 https://download.docker.com/linux/debian bullseye InRelease
Hit:11 http://download.proxmox.com/debian/pve bullseye InRelease
Hit:12 http://packages.openmediavault.org/public shaitan InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
pve-headers is already the newest version (7.1-1).
The following packages were automatically installed and are no longer required:
pve-headers-5.15.19-1-pve pve-kernel-5.15.19-1-pve
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
pve-headers-5.15.27-1-pve pve-kernel-5.15.27-1-pve
The following NEW packages will be installed:
pve-headers-5.15.27-1-pve pve-kernel-5.15.27-1-pve
The following packages will be upgraded:
pve-headers-5.15 pve-kernel-5.15
2 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/86.6 MB of archives.
After this operation, 466 MB of additional disk space will be used.
Selecting previously unselected package pve-headers-5.15.27-1-pve.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 88102 files and directories currently installed.)
Preparing to unpack .../pve-headers-5.15.27-1-pve_5.15.27-1_amd64.deb ...
Unpacking pve-headers-5.15.27-1-pve (5.15.27-1) ...
Preparing to unpack .../pve-headers-5.15_7.1-13_all.deb ...
Unpacking pve-headers-5.15 (7.1-13) over (7.1-10) ...
Selecting previously unselected package pve-kernel-5.15.27-1-pve.
Preparing to unpack .../pve-kernel-5.15.27-1-pve_5.15.27-1_amd64.deb ...
Unpacking pve-kernel-5.15.27-1-pve (5.15.27-1) ...
Preparing to unpack .../pve-kernel-5.15_7.1-13_all.deb ...
Unpacking pve-kernel-5.15 (7.1-13) over (7.1-10) ...
Setting up pve-kernel-5.15.27-1-pve (5.15.27-1) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.15.27-1-pve /boot/vmlinuz-5.15.27-1-pve
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.15.27-1-pve /boot/vmlinuz-5.15.27-1-pve
update-initramfs: Generating /boot/initrd.img-5.15.27-1-pve
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 5.15.27-1-pve /boot/vmlinuz-5.15.27-1-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.27-1-pve
Found initrd image: /boot/initrd.img-5.15.27-1-pve
Found linux image: /boot/vmlinuz-5.15.19-1-pve
Found initrd image: /boot/initrd.img-5.15.19-1-pve
done
Setting up pve-kernel-5.15 (7.1-13) ...
Setting up pve-headers-5.15.27-1-pve (5.15.27-1) ...
Setting up pve-headers-5.15 (7.1-13) ...
Set 5.15.27-1-pve' as default... 0
Please reboot to use the new kernel.
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be REMOVED:
pve-headers-5.15.19-1-pve pve-kernel-5.15.19-1-pve
The following packages have been kept back:
pve-headers-5.13
0 upgraded, 0 newly installed, 2 to remove and 1 not upgraded.
After this operation, 464 MB disk space will be freed.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 118936 files and directories currently installed.)
Removing pve-headers-5.15.19-1-pve (5.15.19-1) ...
Removing pve-kernel-5.15.19-1-pve (5.15.19-1) ...
Examining /etc/kernel/postrm.d.
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 5.15.19-1-pve /boot/vmlinuz-5.15.19-1-pve
update-initramfs: Deleting /boot/initrd.img-5.15.19-1-pve
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 5.15.19-1-pve /boot/vmlinuz-5.15.19-1-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.27-1-pve
Found initrd image: /boot/initrd.img-5.15.27-1-pve
done
END OF LINE
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages have been kept back:
pve-headers-5.13
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
END OF LINE
Thanks,
Something on your system is blocking. What is the output from clicking the install proxmox kernel button again
This happened to me, there were new proxmox kernels to install, but whereas with V5 it would install via update management with V6 it does not, I read a thread (can't find it now) where something similar was happening to another user.
The solution was to run apt dist-upgrade from the cli to deploy new kernels, I have done this twice now and it works fine
whereas with V5 it would install via update management with V6 it does not
Both v5 and v6 add the proxmox repo and install the kernel in the exact same way. There is just something in a weird state on your systems that require dist-upgrade. I haven't run into this on my systems running the proxmox kernel but I don't think I ever upgrade from the Updates tab. And there is nothing I can add to the plugin to change this behavior - it is apt causing it.
Both v5 and v6 add the proxmox repo and install the kernel in the exact same way. There is just something in a weird state on your systems that require dist-upgrade. I haven't run into this on my systems running the proxmox kernel but I don't think I ever upgrade from the Updates tab. And there is nothing I can add to the plugin to change this behavior - it is apt causing it.
So you do an apt upgrade from the command line vs using the GUI?
So you do an apt upgrade from the command line vs using the GUI?
I never use apt. Always apt-get dist-upgrade. And yes, I prefer the command line for most things. I like to be prompted for things that change.
There is just something in a weird state on your systems that require dist-upgrade
Don't know what that is, but the behavior for a kernel install for me is different on V6 to V5, this is not an issue, but the kernel updates will not install from update management, they remain in the list until installed/deployed from the cli
the behavior for a kernel install for me is different on V6 to V5,
The install is not different.
v6 https://github.com/OpenMediaVa…in/omv-installproxmox#L45
v5 https://github.com/OpenMediaVa…in/omv-installproxmox#L49
Upgrades might be because of a package dependency. The proxmox kernel for 6.x is still in a weird state since the plugin is installing 5.15 but pve-headers is still pointing at pve-headers-5.13. So, if you are using something that depends on kernel headers, the system might not want to upgrade from the Updates tab - https://github.com/openmediava…/engined/rpc/apt.inc#L206
I don't know what else people want me to say. The proxmox kernel is not made for OMV. If there is a slight oddity about it and you have to upgrade from the command line, that is just what you will have to do if you want to use the proxmox kernel.
So, if you are using something that depends on kernel headers, the system might not want to upgrade from the Updates tab
The only thing I'm using is zfs, apart from that my system is very basic, I have no problem running the upgrade from the cli, that works fine
The only thing I'm using is zfs
And zfs is the biggest offender since the plugin has to have strange dependencies to support the proxmox kernel and the backports kernel - https://github.com/OpenMediaVa…master/debian/control#L13
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
