Network refuses to start after upgrade, worked perfectly before and currently works on Debian but refuses to on Proxmox.

David333Black

New Member
Jan 9, 2023
1
0
1
I have a small cluster with 3 machines - all Dell R720s.
Proxmox was running well. I updated the least used machine to the latest version and ever since the network has refused to start up.

I have been working at this for a week solid. I've read every post on the forum or the internet trying for a solution, (some make some sense, some seem close to a solution but no luck yet.) I'm an intermediate user, I know the basics and I'm keen to learn.

I believe the kernel went from 6.5.13-6-pve to 6.8.12-2-pve. If I choose the earlier 6.5.13-6 promox boots and runs normally, the newer one flashes up a few errors then arrives at the normal console screen, however the network, nor the bridges are setup. I can log in via idrac and the virtual console.
The networking.service won't start because the ifupdown2-pre.service won't run.
The ifupdown2-pre.service won't run because of an error in systemd-udev-settle.service
it seems the queue isn't empty and it times out (I think that this means all the devices haven't settled)

No network at all from the Proxmox host!!

I've tried masking or disabling services - no use
Most posts seem to suspect the Broadcom network adapter.
I've loaded the latest firmware - not easy
some people seem to think its the rdma-support on the NIC but as far as I can tell thats more recent NIC that use the bnx driver. Mine uses the tg3 driver, its the 4 port x 1 GB network daughter card in the Dell its based on a 5720 and I don't think it supports rdma.
Before you tell me to manually ifup the adapter it doesn't work! or the vmbr1- it doesn't work. The adapters haven't changed names. The network/interfaces file hasn't changed and is correct for the earlier version. systemctl restart networking service doesn't work, it just brings up the same error (for the 10 thousandth time !!)
The network and adapters work perfectly in the latest version of debian.
If anyone has a solution or at least can point me in the right direction, I'd be very grateful (this is my first post ever ... please be gentle)
 
Last edited:
Code:
dpkg-reconfigure ifupdown2

This fix my problem as it reconfigured the starting service of ifupdown2
 

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!