For the past couple years my server has been running without issue; working smoothly through many changes, updates, and hardware swaps. Two days ago I decided to update UNRAID after a steady uptime of ~5 months, but after rebooting I was unable to access the GUI. I attempted to ping the server from within my network, but the IP was unreachable. On the KVM console I have connected to my server, I could see that the correct IPv4 address is being displayed, but within the start-up text I noticed a line midway through that said "device eth0 does not exist." This persisted across multiple restarts of the system, changing the switch, cat6 cable, and directly connecting my PC to the ethernet port. I was still able to login to the server's interface directly through the KVM console with no issue. This led me to believe that my motherboard's cheap onboard Realtek network interface chipset had died, so I ordered a Broadcom PCIe network interface card (BCM5751) to replace it, which should arrive by the end of the week.

 

However, today I restarted my system again, just to see what happens, and I noticed that the read-out "device eth0 does not exist" was no longer present. I still am unable to access the GUI, but when I ping the server's IPv4 address now, instead of returning as "unreachable," the request instead times out each time.

 

I really am not sure what is happening now as this seems to exceed my scope of knowledge and Googling ability. I'm hoping that this is just simply a problem with the mobo's network port giving out, and the NIC I have arriving in a few days will solve the problem, but if anybody has a better answer, I would greatly appreciate it.

 

Thank you in advance.

unraid-diagnostics-20241028-2112.zip

Reviewing diagnostics

you may need to pull the flash drive and reset the network config..

see forum post:

 

You may need to install driver plugin:
 

 

per diag:
your using a realtek nic. and there have been some known issues with that lately with the new kerneal.
driver: r8169
version: 6.1.106-Unraid
firmware-version: rtl8168g-2_0.0.1 02/06/13
expansion-rom-version: 
bus-info: 0000:03:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no

why eth0 is down idk, but arcodign to your diag it is off
lo               UNKNOWN        127.0.0.1/8 ::1/128 
tunl0@NONE       DOWN           
eth0             DOWN           
bond0            DOWN           
br0              DOWN           192.168.1.4/24 metric 1 

run:
 

ifconfig eth0 up

you may need to make a user script to auto do this if this is happening at boot. otherwsie somtheing ran or erroer and teh deivce is now down.
Also double check ethernet cord is securly pluged in. that you see link lights on the port / switch-router...

per syslog:
Oct 28 21:10:38 BigNASty kernel: r8169 0000:03:00.0 eth0: RTL8168g/8111g, 40:8d:5c:75:6b:7c, XID 4c0, IRQ 27
Oct 28 21:10:38 BigNASty kernel: r8169 0000:03:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]

the driver is loading... jumbo frames is 10 GB netowrks please check unraid network settings and mtu are st to 1 gb settins so mtu 1500 no jumbo frames

Alright, I will try those solutions that next. I just reset the network config and rebooted, with no change (still timing out on ping.) I have read about Realtek NICs causing problems with UNRAID, so that's why I am hoping that a new NIC will fix this if nothing else.

 

I appreciate the help, my man.

The NIC should work with the default driver, but no link is being detected:

 

Link detected: no

 

I was going through these steps to attempt to troubleshoot why the network port was no longer active when my new Broadcom NIC came in toady. As soon as I installed it everything was immediately back to normal and working smoothly. I do now remember a few times after shutting down the server temporarily I have had to power cycle it a couple times to get it to connect back to the network; not sure why the on-board NIC started causing problems, but a $20 PCI card and 2 minutes of installation time solved all the problems and I am fine with that.

Edited October 30, 20241 yr by Subsgood