Pve Kernel Dependencies Unmet

gawkk

Active Member
Apr 2, 2018
4
0
41
36
Hi,

I'm using Proxmox VE 5.1-46, and I'm trying to upgrade the host system.

I tried apt-get upgrade -f, and I'm getting the following error:

Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.13.13-5-pve
Found initrd image: /boot/initrd.img-4.13.13-5-pve
Found linux image: /boot/vmlinuz-4.13.13-4-pve
Found initrd image: /boot/initrd.img-4.13.13-4-pve
Found linux image: /boot/vmlinuz-4.13.13-2-pve
Found initrd image: /boot/initrd.img-4.13.13-2-pve
Found linux image: /boot/vmlinuz-4.10.15-1-pve
Found initrd image: /boot/initrd.img-4.10.15-1-pve
done
Preparing to unpack .../bsdutils_1%3a2.29.2-1+deb9u1_amd64.deb ...
Unpacking bsdutils (1:2.29.2-1+deb9u1) over (1:2.29.2-1) ...
Errors were encountered while processing:
/var/cache/apt/archives/pve-kernel-4.13.16-1-pve_4.13.16-43_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

This is the error from dist-upgrade:

root@sd-59944:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
pve-kernel-4.13 : Depends: pve-kernel-4.13.16-1-pve but it is not installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

And this happens with apt --fix-broken install:

Errors were encountered while processing:
/var/cache/apt/archives/pve-kernel-4.13.16-1-pve_4.13.16-43_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any ideas how to fix this?
 
What are you using in this location?
Code:
root@home:/etc/apt/sources.list.d# cat pve-enterprise.list

Personally I don't have the extra money to pay for subscription so i use the community version to test it and play with things.. So this is what i have in that location

Code:
root@home:/etc/apt/sources.list.d# cat pve-enterprise.list
#deb https://enterprise.proxmox.com/debian/pve stretch pve-enterprise
deb http://download.proxmox.com/debian/pve stretch pve-no-subscription

I hope this helps


I updated this because I also failed to mention that apt-get update and apt-get upgrade should be re run then log into the proxmox via yourdomain.com:8006 click on the node then search for the section Updates after you do this click refresh then upgrade this should update your pve kernel to the latest..

Here is what uname -a is on my new installation with fresh updates

Code:
root@home:~# uname -a
Linux home 4.13.16-1-pve #1 SMP PVE 4.13.16-43 (Fri, 16 Mar 2018 19:41:43 +0100) x86_64 GNU/Linux
root@home:~#

Here is an example screenshot. Ignore all subscription boxes.

how-to-update-proxmox-kernel-vesions.png



I seen this posted from some one else's post I think this is also useful information in case you are having troubles.

https://pve.proxmox.com/wiki/Package_Repositories
 
Last edited:
  • Like
Reactions: gawkk
I checked the sources.list and pve-enterprise.list, and they are set to default. I've commented out the repo in pve-enterprise since I don't have a subscription.

---

I tried the apt-get update and upgrade, and then accesses the Proxmox GUI-based update method (like in your screenshot), and I get the same error message:

Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
pve-kernel-4.13 : Depends: pve-kernel-4.13.16-1-pve but it is not installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

The command apt --fix-broken install doesn't fix the error, I've supplied the output from that in my original post.
 
Last edited:
Found a solution!

My boot partition was almost completely used up (checked with dh -f), and I deleted 4 old kernels.

The command apt-get remove didn't work in this instance due to the full partition, but dpkg -P worked fine (example: dpkg -P pve-kernel-4.13.13-4-pve).

After that, I installed all the latest Proxmox/Debian updates.

If anyone is having a similar problem, make sure you have space in /boot.
 
Last edited:
Found a solution!

My boot partition was almost completely used up (checked with dh -f), and I deleted 4 old kernels.

The command apt-get remove didn't work in this instance due to the full partition, but dpkg -P worked fine (example: dpkg -P pve-kernel-4.13.13-4-pve).

After that, I installed all the latest Proxmox/Debian updates.

If anyone is having a similar problem, make sure you have space in /boot.

the actual problem was that you used "apt-get upgrade" instead of "apt-get dist-upgrade". you always need to use "apt-get dist-upgrade" with PVE, because we do introduce new dependencies from time to time which "apt-get upgrade" does not handle.

edit: or it was a combination of both (PVE does not setup a separate /boot partition since quite a long time btw - is this an installation on top of Debian?)
 
  • Like
Reactions: gawkk
the actual problem was that you used "apt-get upgrade" instead of "apt-get dist-upgrade". you always need to use "apt-get dist-upgrade" with PVE, because we do introduce new dependencies from time to time which "apt-get upgrade" does not handle.

edit: or it was a combination of both (PVE does not setup a separate /boot partition since quite a long time btw - is this an installation on top of Debian?)

Yes, it is a Debian install, with Proxmox added afterwards. I used the default install from Online.net, which I guess they customized to suit their networking needs, and left a small /boot partition.