Broken the upgrade from 7 to 8. Setting up pve-manager (8.0.4) hangs

[promok]

Hello,
There was an erroneous reboot while upgrading from 7 to 8. After running something like dpkg --reconfigure it kind of finished the upgrade, but the node is unusable, the VMs don't start. So, when i do apt upgrade it hangs at
Setting up pve-manager (8.0.4) ...
I have deleted /var/lib/pve-manager/pve-replication-state.json, and now when i do
apt install --reinstall pve-manager
it spits
E: Internal Error, No file name for pve-manager:amd64

Is it completely broken? What to do in such situation?

 

[Chris]

apt upgrade

you should never upgrade a Proxmox VE and any other Proxmox product like this, always use apt dist-upgrade to correctly resolve all dependencies.

Please share the full output of apt update && apt dist-upgrade

 

[Nuke Bloodaxe]

Please ensure you have your VMs backed up; I hope you did so before this upgrade.
As a tip to others who read this, and to add to Chris above, running

apt dist-upgrade --download-only

to download all the packages in advance, then performing the

apt dist-upgrade

can avoid some potential headaches when doing a full system upgrade.

For the future, following the directions precisely at PVE7to8 is the way to go to avoid a good chunk of common problems.

 

[promok]

you should never upgrade a Proxmox VE and any other Proxmox product like this, always use apt dist-upgrade to correctly resolve all dependencies.

Please share the full output of apt update && apt dist-upgrade

Yes, i have started the upgrade with
apt update
apt dist-upgrade
then in the middle the server was rebooted, and no ip active. So, i finished the upgrade with errors via local terminal.
Then i tried different ways to upgrade again including dpkg configure and dist-upgrade --> the same problem: it hanged at Setting up pve-manager (8.0.4) ...
Then i found this thing
https://askubuntu.com/questions/266450/how-to-fix-e-internal-error-no-file-name-for-libc6
and last advice did not work, so i have done
sudo dpkg -r --force-depends pve-manager
then apt install pve-manager and it worked.
The node now seems to be in working condition.
Thanks to all.

 

[promok]

No, actually, not in working condition. It hangs in a matter of hours.
And what i see in syslog:
2023-09-30T19:05:10.087259+02:00 proxmox2 pvescheduler[562380]: jobs: cfs-lock 'file-jobs_cfg' error: no quorum!
2023-09-30T19:05:10.091531+02:00 proxmox2 pvescheduler[562379]: replication: cfs-lock 'file-replication_cfg' error: no quorum!
2023-09-30T19:05:11.602210+02:00 proxmox2 pvestatd[1005]: storage 'proxmox.backup' is not online
2023-09-30T19:05:23.890288+02:00 proxmox2 pvestatd[1005]: storage 'proxmox.backup' is not online
2023-09-30T19:05:33.106346+02:00 proxmox2 pvestatd[1005]: storage 'proxmox.backup' is not online
2023-09-30T19:05:42.322239+02:00 proxmox2 pvestatd[1005]: storage 'proxmox.backup' is not online
2023-09-30T19:05:45.935895+02:00 proxmox2 kernel: [98952.203759] net_ratelimit: 9 callbacks suppressed
2023-09-30T19:05:45.935908+02:00 proxmox2 kernel: [98952.203763] r8169 0000:02:00.0 enp2s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
2023-09-30T19:05:45.935908+02:00 proxmox2 kernel: [98952.205159] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
2023-09-30T19:05:45.939896+02:00 proxmox2 kernel: [98952.206582] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
2023-09-30T19:05:45.939907+02:00 proxmox2 kernel: [98952.207985] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
2023-09-30T19:05:45.939908+02:00 proxmox2 kernel: [98952.209319] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
2023-09-30T19:05:45.943921+02:00 proxmox2 kernel: [98952.210715] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
2023-09-30T19:05:45.943929+02:00 proxmox2 kernel: [98952.212060] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
2023-09-30T19:05:45.967933+02:00 proxmox2 kernel: [98952.235318] r8169 0000:02:00.0 enp2s0: rtl_eriar_cond == 1 (loop: 100, delay: 100).
2023-09-30T19:05:45.991897+02:00 proxmox2 kernel: [98952.259633] r8169 0000:02:00.0 enp2s0: rtl_eriar_cond == 1 (loop: 100, delay: 100).
2023-09-30T19:05:46.015923+02:00 proxmox2 kernel: [98952.283788] r8169 0000:02:00.0 enp2s0: rtl_eriar_cond == 1 (loop: 100, delay: 100).
2023-09-30T19:05:51.538314+02:00 proxmox2 pvestatd[1005]: storage 'proxmox.backup' is not online
2023-09-30T19:06:03.826246+02:00 proxmox2 pvestatd[1005]: storage 'proxmox.backup' is not online
2023-09-30T19:06:10.102102+02:00 proxmox2 pvescheduler[562711]: jobs: cfs-lock 'file-jobs_cfg' error: no quorum!
2023-09-30T19:06:10.106827+02:00 proxmox2 pvescheduler[562710]: replication: cfs-lock 'file-replication_cfg' error: no quorum!

I have to shutdown it with power button and power it up again for a few hours...
What could be wrong with it?

 

[leesteken]

2023-09-30T19:05:45.935908+02:00 proxmox2 kernel: [98952.203763] r8169 0000:02:00.0 enp2s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
2023-09-30T19:05:45.935908+02:00 proxmox2 kernel: [98952.205159] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
2023-09-30T19:05:45.939896+02:00 proxmox2 kernel: [98952.206582] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
2023-09-30T19:05:45.939907+02:00 proxmox2 kernel: [98952.207985] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
2023-09-30T19:05:45.939908+02:00 proxmox2 kernel: [98952.209319] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
2023-09-30T19:05:45.943921+02:00 proxmox2 kernel: [98952.210715] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
2023-09-30T19:05:45.943929+02:00 proxmox2 kernel: [98952.212060] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
2023-09-30T19:05:45.967933+02:00 proxmox2 kernel: [98952.235318] r8169 0000:02:00.0 enp2s0: rtl_eriar_cond == 1 (loop: 100, delay: 100).
2023-09-30T19:05:45.991897+02:00 proxmox2 kernel: [98952.259633] r8169 0000:02:00.0 enp2s0: rtl_eriar_cond == 1 (loop: 100, delay: 100).
2023-09-30T19:05:46.015923+02:00 proxmox2 kernel: [98952.283788] r8169 0000:02:00.0 enp2s0: rtl_eriar_cond == 1 (loop: 100, delay: 100).

There have been reports on this forum of problems with the r8169 driver. Maybe you can look at some of the threads and see if there is a known work-around?