[SOLVED] dpkg error code (1): Too many Errors while upgrading to PVE 7

MrMagier08

New Member
Mar 5, 2023
3
0
1
Hi everyone,
I recently 'reactivated' my old server and booted up into proxmox. I then wanted to upgrade to the newest version, so I added the needed depositories and followed the steps on the documentation. However, after some time, the process got stuck while running dpkg (I don't have the exact logs, but I could try to recreate it again if it helps), and the last output was scanning the lc's and vm's, and then it literally printed "done" and got stuck at like 50%. I didn't know how to solve the issue and rebooted the system, and now I can only boot into the older (I think Debian 5.7) kernel.

pve6to7 just gave warning: WARN: unexpected running and installed kernel '5.4.106-1-pve'.

If I try to run apt upgrade or apt dist-upgrade or anything else dpkg related, I always get this error message: link to pastebin (That particular command was apt full-upgrade)

Thanks for any ideas for the reason of this behaviour or any possible solutions!
If anyone needs other specific logs etc. just ask!

NOTE:
I have tried upgrading to the latest 6.x version, same issue
I couldn't find any solution anywhere on the web, but maybe I am just dumb?
If that's the only possibility, I am able to reinstall Proxmox and use a backup.
 
Last edited:
Hi,
Code:
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
what does fuser -v /var/cache/debconf/config.dat tell you?
 
  • Like
Reactions: Stoiko Ivanov
I ran it, cat /etc/cache/debconf/config.dat gave me this.

And, I don't know how, but somehow the system booted on the newest kernel... but the error still exists
 
Last edited:
Somehow, after rebooting the machine and letting it run for about 6 hours, then running apt update, apt upgrade, dpkg --configure -a in all possible ways on multiple ssh shells at the same time, I managed to clear all errors and get it upgraded to PVE 7.3-6...
Thanks for your help!
 
Somehow, after rebooting the machine and letting it run for about 6 hours, then running apt update, apt upgrade, dpkg --configure -a in all possible ways on multiple ssh shells at the same time, I managed to clear all errors and get it upgraded to PVE 7.3-6...
Thanks for your help!
Glad you were able to solve it :) Just to note, with Proxmox VE, you should always use apt dist-upgrade or apt full-upgrade, because only those ensure that the upgrade is properly done in certain situations (e.g. when a package needs to be removed for another one to be upgraded).
 

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!

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!