No network after PCIe NVM disk plug

[albertfa]

I've got a NVMe disk in a PCIe support. After plug and reboot system starts but without no network. IP is assigned, but the lights on the adapter were out... Any idea? I'm running pve 5.4.73.
Thanks in advance!

 

[leesteken]

The name of the network device, in modern Linux systems (like the Debian underneath Proxmox) is based on its PCI ID. Adding an additional PCI device can cause some of the IDs of the other devices to shift by one. This can change the name of your network devices and cause it to be unconfigured and therefore not enabled.

 

[albertfa]

Thanks for the answer. I will check this, but the LAN is not a PCI device is the motherboard one... I think they have different ID

 

[leesteken]

Most onboard devices are also PCI(e) and therefore subject to this issue. Use journalctl -b 0 | grep renamed to check for a kernel message about renaming network devices (renamed from eth0, eth1, etc., not veth...). Then change /etc/network/interfaces to use the new name, which probably only differs in one digit from the old name in that configuration file.

 

[albertfa]

Hi, I'm again working on this. This is the output of

 journalctl -b 0 | grep renamed

according to your words the LAN has been renamed to eth0, as far as I can see the old name is enp2s0... Am I right?

Oct 24 19:32:38 pve kernel: r8169 0000:02:00.0 enp2s0: renamed from eth0

This is a cat from interfaces:

auto lo
iface lo inet loopback

iface enp2s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.84/24
        gateway 192.168.1.1
        bridge_ports enp2s0
        bridge_stp off
        bridge_fd 0

Thanks again for your help !!

 

[leesteken]

Hi, I'm again working on this. This is the output of

 journalctl -b 0 | grep renamed

according to your words the LAN has been renamed to eth0, as far as I can see the old name is enp2s0... Am I right?

Oct 24 19:32:38 pve kernel: r8169 0000:02:00.0 enp2s0: renamed from eth0

Actually, the other way around: a network device was renamed to enp2s0, which is the name that will show up in ip a and needs to be used in /etc/network/interfaces. My guess is that the old name, used in /etc/network/interfaces, was enp1s0?

 

[albertfa]

Hello, I was wrong, Sorry ! The copied text was the old one, previous to the PCI change. When I realize my mistake and repeated your suggestion, everything comes on the way. As you said, the old LAN adapter mutated the ID, once included in the networks everything goes as it has to go.
Thank you so much for your help.

 

[Joe Piler]

Most onboard devices are also PCI(e) and therefore subject to this issue. Use journalctl -b 0 | grep renamed to check for a kernel message about renaming network devices (renamed from eth0, eth1, etc., not veth...). Then change /etc/network/interfaces to use the new name, which probably only differs in one digit from the old name in that configuration file.

This helped me tremendously

 

[MinishMan]

Most onboard devices are also PCI(e) and therefore subject to this issue. Use journalctl -b 0 | grep renamed to check for a kernel message about renaming network devices (renamed from eth0, eth1, etc., not veth...). Then change /etc/network/interfaces to use the new name, which probably only differs in one digit from the old name in that configuration file.

This helped me triple tremendously when I added an NVMe drive to my setup.

My eth0 had gone from being enp1s0 to enp2s0.

I just had to rename it in two places in the /etc/network/interfaces file and restart networking with systemctl restart networking.service and I was back in business.

Thank you.

 

[hapklaar]

also much obliged @leesteken !