[SOLVED] No network anymore after upgrading RAM

MisterCyp

New Member
Apr 11, 2024
2
0
1
Hello everyone,

I installed proxmox VE few days ago. It was working fine but today I installed a second ram on the second slot and I don't have anymore network on it ...

The LEDs on the ethernet port are blinking on the boot but after the ramdisk loading the leds switched off forever.

You can find attached several result of commands I get.

My /etc/network/interfaces:
Code:
auto lo
iface lo inet loopback

iface enp3s0 inet manual

auto vmbr0
iface vmbr0 inet static
    address 192.168.1.100
    gateway 192.168.1.254
        netmask 255.255.255.0
    bridge-ports enp3s0
    bridge-stp off
    bridge-fd 0


#source /etc/network/interfaces.d/*

systemctl status networking.service:
Code:
● networking.service - Network initialization
     Loaded: loaded (/lib/systemd/system/networking.service; enabled; preset: enabled)
     Active: active (exited) since Thu 2024-04-11 22:24:42 CEST; 17min ago
       Docs: man:interfaces(5)
             man:ifup(8)
             man:ifdown(8)
    Process: 1663 ExecStart=/usr/share/ifupdown2/sbin/start-networking start (code=exited, status=0/SUCCESS)
   Main PID: 1663 (code=exited, status=0/SUCCESS)
        CPU: 2.279s

Apr 11 22:24:39 proxmox systemd[1]: Starting networking.service - Network initialization...
Apr 11 22:24:39 proxmox networking[1663]: networking: Configuring network interfaces
Apr 11 22:24:41 proxmox networking[1681]: error: vmbr0: bridge port enp3s0 does not exist
Apr 11 22:24:41 proxmox /usr/sbin/ifup[1681]: error: vmbr0: bridge port enp3s0 does not exist
Apr 11 22:24:41 proxmox networking[1681]: warning: vmbr0: apply bridge ports settings: bridge configuration failed (missing ports)
Apr 11 22:24:41 proxmox /usr/sbin/ifup[1681]: warning: vmbr0: apply bridge ports settings: bridge configuration failed (missing ports)
Apr 11 22:24:41 proxmox networking[1681]: error: >>> Full logs available in: /var/log/ifupdown2/network_config_ifupdown2_86_Apr-11-2024_22:24:40.658547 <<<
Apr 11 22:24:41 proxmox /usr/sbin/ifup[1681]: >>> Full logs available in: /var/log/ifupdown2/network_config_ifupdown2_86_Apr-11-2024_22:24:40.658547 <<<
Apr 11 22:24:42 proxmox systemd[1]: Finished networking.service - Network initialization.

I put the full log attached.

Thanks in advance for your help.
 

Attachments

  • dmesg.log
    66.1 KB · Views: 0
  • ifupdown2.debug.log
    24.9 KB · Views: 0
  • ipAddr.log
    1.6 KB · Views: 4
  • ipLinkShow.log
    1.2 KB · Views: 1
  • lspciV.log
    9.1 KB · Views: 0
  • status.log
    1.5 KB · Views: 0
According to "ip addr" there is eno1 (with altname enp3s0) and you used 2x "enp3s0" for your vmbr0 and NIC in the network config. Not sure if the altname can be used in the network config. I would try to change all the "enp3s0" occurrences to "eno1" in the /etc/network/interfaces and reboot to see if it helps.
At least the logs sound like PVE is expecting eno1 and not the altname.
 
Last edited:
  • Like
Reactions: MisterCyp
According to "ip addr" there is eno1 (with altname enp3s0) and you used 2x "enp3s0" for your vmbr0 and NIC in the network config. Not sure if the altname can be used in the network config. I would try to change all the "enp3s0" occurrences to "eno1" in the /etc/network/interfaces and reboot to see if it helps.
At least the logs sound like PVE is expecting eno1 and not the altname.
Thank you ! it works ! But I don't understand why it was working before ?
 

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!