I can't ping host after reboot

[bit_creepy]

After spending a few hours getting my Proxmox server setup the way I wanted from scratch, I wanted to test the VM/LXC startup order. Upon startup though I was unable to access the webui. I then found I was unable to ping the host. I've also tried connected with a USB to Ethernet adapter to test if it's the mobo Ethernet, but still it's not reachable in any way. I simply cannot work it out. Please help.

Below are my ip a and netwrok interface settings:







Update:
I noticed my enp4s0 adaptor is no longer listed in ip link.

Update 2:
I resolved the issue by reflashing my mobo BIOS using Gigabyte's Q-Flash feature (not an update, just re-flash). I hadn't even made an BIOS changes, so not happy with how unstable my new mobo is so far.

 

[Moayad]

Thank you for sharing your solution!

Update:
I noticed my enp4s0 adaptor is no longer listed in ip link.

After you changed the NIC name in the Proxmox VE, did you try `ifreload -a` command?

 

[bit_creepy]

I didn't change the NIC name. I just re-flashed the BIOS and it became available again. I've noticed this keeps happening upon a Proxmox VE reboot, which isn't ideal at all. I'm not sure if it's a mobo issue and something in Proxmox. I'm not sure 'ifreload -a' would resolve anything.

 

[aaron]

The name of the NIC depends on where on the PCI bus it is enumerated. Different BIOS versions, or changes to the PCI devices attached to the motherboard can cause changes in the NIC name.

 

[bit_creepy]

The name of the NIC depends on where on the PCI bus it is enumerated. Different BIOS versions, or changes to the PCI devices attached to the motherboard can cause changes in the NIC name.

Thanks Aaron. It seems to me the NIC is missing altogether according to my 'ip a' screenshot post above. If I'm wrong, which one of those interfaces listed in above screenshot is the NIC? And more crucially, how do I stop this from changing name?

I did some experimenting and found that by installing the following it seems to now behave when rebooting PVE:

apt-get install --reinstall ifupdown2

Then I ran

ifreload -a

I'll admit I don't really know what I'm doing though.