[SOLVED] Network drops on boot

[hockpunk426]

I had Proxmox up and running and everything was working fine. I ran an update and everything was still working great. I shut down the computer to remove my raid card to connect the hard drives directly to the mobo. After I booted up I noticed that I wasn't showing any activity light on the ethernet jack after boot.

If I boot into the bios the ethernet jack goes active and I can ping the IP. However, after Proxmox VE loads, the port goes dark again and I can't hit the IP anymore.

On load it displays the normal screen with the IP address and everything but I don't see it on the network and the port on the computer is dark. I have tried other ports on the switch and other cables as well to cover my bases before I posted here.

I am running 6.1-3/37248ce6
kernal 5.3.10-1-pve

I am new to proxmox. Any help is appreciated.

 

[aaron]

Sounds like removing the RAID card changed the order on the PCI bus and thus the name of the NIC.

Try to run ip a on the CLI which should list all NICs available and their IP addresses if configured.

It's possible that you will have to replace all occurrences of the old name in the /etc/network/interfaces file.

 

[hockpunk426]

ok so I have

1. lo
2. enp5s0 which was the raid card showing state down.
3. vmbr0 this is the network

I tried to delete enp5s0 and reboot but it is still there. Do I just need to change the vmbr0 name to eno1?

I have been referencing here https://pve.proxmox.com/wiki/Network_Configuration

Thank you for the help.

 

[aaron]

Keep the vmbr0, that is the first bridge. It is using the physical NIC as bridge_ports.

As an example:

auto lo
iface lo inet loopback

iface enp4s0 inet manual

auto vmbr0
iface vmbr0 inet static
    address  192.168.x.y
    netmask  255.255.240.0
    gateway  192.168.x.1
    bridge-ports enp4s0
    bridge-stp off
    bridge-fd 0

Notice how I have the enp4s0 interface configured and set in bridge_ports.

Do you have your enp5s0 configured in these places? If my assumption about the renamed interface is correct, you should have some other name.
Change that to enp5s0 and reboot the machine.

 

[hockpunk426]

This is what mine shows currently.

Looks like it is set correctly.

 

[aaron]

But ip a only shows an enp5s0 and no enp6s0 right?

Try replacing the enp6s0 in your config with enp5s0 and reboot.

 

[hockpunk426]

But ip a only shows an enp5s0 and no enp6s0 right?

Try replacing the enp6s0 in your config with enp5s0 and reboot.

That was it, it's up and running again! thank you for the assistance!

 

[littlebighuman]

I had this EXACT issue, after adding a NVME SSD. Took me a while to find this post, but glad I did

 

[itswoolfy]

I had this issue, and this helped me thank you

 

[pete25r]

I second littlebighuman. Installed NVME SSD, network dropped during boot. This helped a lot. Thanks!

 

[mickyears]

Thank you for your effort in advising us on this problem, I had it to and have resolved it

kind regards

 

[newbonthefly]

Thank you for this, very quick fix that got me back online quickly! I struggled through a couple of reboots until I realized I needed to change the name on the top line AND the bridge-ports line.

 

[J0hn_ion]

I added a new PCIe card for NVMe SSD storage and had the same issue. This post helped a lot!
For me it was possible to revert the changes by removing the card and change BIOS setting back the ones before installing the card. With this I was able to reach my pve again through the web interface and (temporarily) change my root password to an easier one to be actually able to enter it during physical access to the server. Then I did the hardware and BIOS changes again and applied the above mentioned changes to the interfaces config.