[SOLVED] Ran into a dependency problem with the latest pve updates

O

Ovidiu

Renowned Member
Proxmox Subscriber
Apr 27, 2014
326
12
83
I'm on PVE 8.0.4 and and this server is using the pve-no-subscription repo.
I had switched top the pve 6.2 kernel as I had some issues with my AMD Ryzen.
It ran fine since, until the last updates appeared (I think last night or within the last 48 hours I'd say)

Any hints? Can you spot the problem? Btw. kdump-tools have long been uninstalled, no idea why tis stil lshowing up here.

Code: 
apt -f install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
5 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up proxmox-kernel-6.2.16-6-pve (6.2.16-7) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.2.16-6-pve /boot/vmlinuz-6.2.16-6-pve
update-initramfs: Generating /boot/initrd.img-6.2.16-6-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/8B8E-0EE8
        Copying kernel and creating boot-entry for 6.2.16-5-pve
        Copying kernel and creating boot-entry for 6.2.16-6-pve
run-parts: executing /etc/kernel/postinst.d/kdump-tools 6.2.16-6-pve /boot/vmlinuz-6.2.16-6-pve
kdump-tools: Generating /var/lib/kdump/initrd.img-6.2.16-6-pve
mkinitramfs: failed to determine device for /
mkinitramfs: workaround is MODULES=most, check:
grep -r MODULES /var/lib/kdump/initramfs-tools


Error please report bug on initramfs-tools
Include the output of 'mount' and 'cat /proc/mounts'
update-initramfs: failed for /var/lib/kdump/initrd.img-6.2.16-6-pve with 1.
run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.2.16-6-pve.postinst line 20.
dpkg: error processing package proxmox-kernel-6.2.16-6-pve (--configure):
 installed proxmox-kernel-6.2.16-6-pve package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.2:
 proxmox-kernel-6.2 depends on proxmox-kernel-6.2.16-6-pve; however:
  Package proxmox-kernel-6.2.16-6-pve is not configured yet.


dpkg: error processing package proxmox-kernel-6.2 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
 proxmox-default-kernel depends on proxmox-kernel-6.2; however:
  Package proxmox-kernel-6.2 is not configured yet.


dpkg: error processing package proxmox-default-kernel (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-kernel-6.2:
 pve-kernel-6.2 depends on proxmox-kernel-6.2; however:
  Package proxmox-kernel-6.2 is not configured yet.


dpkg: error processing package pve-kernel-6.2 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on proxmox-default-kernel; however:
  Package proxmox-default-kernel is not configured yet.


dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proxmox-kernel-6.2.16-6-pve
 proxmox-kernel-6.2
 proxmox-default-kernel
 pve-kernel-6.2
 proxmox-ve
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
 
  • Like
Reactions: fidecastro
I managed to fix the problem after I found this thread: https://forum.proxmox.com/threads/problem-after-updating-kernel.103293/ although the solution differed a little as the "sed" command mentioned there is no longer present in "/etc/kernel/postinst.d/kdump-tools" - I had to comment an entire "if" statement which checks if modules = most and then changes it to modules = dep (sorry I can't give the exat solution but I removed kdump-tools and forgot to copy the exact changes.
 
Ovidiu said:
I'm on PVE 8.0.4 and and this server is using the pve-no-subscription repo.
I had switched top the pve 6.2 kernel as I had some issues with my AMD Ryzen.
It ran fine since, until the last updates appeared (I think last night or within the last 48 hours I'd say)

Any hints? Can you spot the problem? Btw. kdump-tools have long been uninstalled, no idea why tis stil lshowing up here.

Code: 
apt -f install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
5 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up proxmox-kernel-6.2.16-6-pve (6.2.16-7) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.2.16-6-pve /boot/vmlinuz-6.2.16-6-pve
update-initramfs: Generating /boot/initrd.img-6.2.16-6-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/8B8E-0EE8
        Copying kernel and creating boot-entry for 6.2.16-5-pve
        Copying kernel and creating boot-entry for 6.2.16-6-pve
run-parts: executing /etc/kernel/postinst.d/kdump-tools 6.2.16-6-pve /boot/vmlinuz-6.2.16-6-pve
kdump-tools: Generating /var/lib/kdump/initrd.img-6.2.16-6-pve
mkinitramfs: failed to determine device for /
mkinitramfs: workaround is MODULES=most, check:
grep -r MODULES /var/lib/kdump/initramfs-tools


Error please report bug on initramfs-tools
Include the output of 'mount' and 'cat /proc/mounts'
update-initramfs: failed for /var/lib/kdump/initrd.img-6.2.16-6-pve with 1.
run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.2.16-6-pve.postinst line 20.
dpkg: error processing package proxmox-kernel-6.2.16-6-pve (--configure):
 installed proxmox-kernel-6.2.16-6-pve package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.2:
 proxmox-kernel-6.2 depends on proxmox-kernel-6.2.16-6-pve; however:
  Package proxmox-kernel-6.2.16-6-pve is not configured yet.


dpkg: error processing package proxmox-kernel-6.2 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
 proxmox-default-kernel depends on proxmox-kernel-6.2; however:
  Package proxmox-kernel-6.2 is not configured yet.


dpkg: error processing package proxmox-default-kernel (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-kernel-6.2:
 pve-kernel-6.2 depends on proxmox-kernel-6.2; however:
  Package proxmox-kernel-6.2 is not configured yet.


dpkg: error processing package pve-kernel-6.2 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on proxmox-default-kernel; however:
  Package proxmox-default-kernel is not configured yet.


dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proxmox-kernel-6.2.16-6-pve
 proxmox-kernel-6.2
 proxmox-default-kernel
 pve-kernel-6.2
 proxmox-ve
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Click to expand...
Having the same issue on a fresh Proxmox 8.0.4 install. No ZFS or kdump-tools in the system. Did you manage to find a solution, Ovidiu?
 
Actually I did find a solution. Inspired by this post here (https://forum.proxmox.com/threads/pveupgrade-error-processing-kernel.129494/) I ran the following command to check on the grub config file:

Code: 
cat /etc/default/grub

Here's the output:

Code: 
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction nofb nomodeset video=vesafb:off,efifb:off""
GRUB_CMDLINE_LINUX="consoleblank=20"

# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
#GRUB_DISABLE_OS_PROBER=false

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

The offending lines were these two below. The first line is wrongly using ` instead of "; the second one had two " in the end instead of only one:
Code: 
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction nofb nomodeset video=vesafb:off,efifb:off""

I fixed these quotes, ran update-grub, then apt update && apt upgrade, and all worked well.
 
fidecastro said:
The first line is wrongly using `
Click to expand...
Backticks are used to specify that its content is to be RUN instead of being taken verbatim.

Basically this tells grub to execute "lsb_release". It drops error messages into nirvana (with "2>/dev/null") and shows the short version of the "distributor id". If - and only if - this execution fails completely it reports so by setting an error level. In that case the verbatim string "Debian" is given by the trailing "echo Debian".

At the end this is cosmetic - you/we know already that Proxmox runs on Debian ;-)

Best regards
 
Hello, I am facing issues with my Proxmox server. I am encountering dependency failures for the following files: media-vz.mount, local-fs.target, and systemd-fsck@dev-proxvg-proxvg.service. I am unable to connect to my server using SSH. Please help me resolve these issues.
 

Attachments

  • Image20230905210611.jpg
    Image20230905210611.jpg
    241.5 KB · Views: 14
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom