February 15, 20197 yr After about a year or so of not having my UNRAID running I just got around to reeplacing the MB and onboard NIC. Well its up and running but the network is not working. I did see an error at some point in the bootup about eth0. I am not sure if I needed to do something or if this should just work.
February 15, 20197 yr 53 minutes ago, Salmack said: After about a year or so of not having my UNRAID running I just got around to reeplacing the MB and onboard NIC. Well its up and running but the network is not working. I did see an error at some point in the bootup about eth0. I am not sure if I needed to do something or if this should just work. Post your diagnostics (Tools-->Diagnostics in GUI) If you cant get into the GUI because of network issues, type 'diagnostics' on the console. File is saved to the flash drive. Edited February 15, 20197 yr by Hoopster
February 15, 20197 yr Author sorry the second one is the correct file, I was doing testing of settings on the issue on that first log
February 15, 20197 yr 20 minutes ago, Salmack said: sorry the second one is the correct file, I was doing testing of settings on the issue on that first log According to your syslog a NIC is not found. Feb 15 23:00:51 Tower root: Device "eth0" does not exist. I assume this is an integrated NIC on your motherboard? Is it enabled in the BIOS?
February 15, 20197 yr Author It is enabled, if I look in TOOLS>Devices It does see the Ethernet Device and lists it with the other items.
February 15, 20197 yr Author ASRock Z390 Pro4 LGA 1151 (300 Series) Intel Z390 HDMI SATA 6Gb/s USB 3.1 ATX Intel Motherboard Lan Device is an Intel I219-V
February 15, 20197 yr 1 minute ago, Salmack said: It is enabled, if I look in TOOLS>Devices It does see the Ethernet Device and lists it with the other items. ifconfig from your diagnostics does not show eth0 either. From a Linux/unRAID perspective, you have no Ethernet NIC. docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 ether 02:42:d3:24:2f:8b txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gre0: flags=128<NOARP> mtu 1476 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gretap0: flags=4098<BROADCAST,MULTICAST> mtu 1462 ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ip_vti0: flags=128<NOARP> mtu 1364 tunnel txqueuelen 1 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.255.255.255 loop txqueuelen 1 (Local Loopback) RX packets 5589 bytes 1857896 (1.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5589 bytes 1857896 (1.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tunl0: flags=128<NOARP> mtu 1480 tunnel txqueuelen 1 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Your unRAID network settings are configured to connect via eth0 with a static IP of 192,168.0.222, but, it is not found on boot. # Generated settings: IFNAME[0]="eth0" DESCRIPTION[0]="onboard LAN" USE_DHCP[0]="no" IPADDR[0]="192.168.0.222" NETMASK[0]="255.255.255.0" GATEWAY="192.168.0.1" DHCP_KEEPRESOLV="yes" DNS_SERVER1="8.8.8.8" DNS_SERVER2="8.8.4.4" DNS_SERVER3="" MTU[0]="" SYSNICS="1" Usually, if the Ethernet cable is bad, the message will be something about no cable found. Not finding the NIC is a bit more serious. Are there any NIC activity lights at the router end of the cable as well as on the server?
February 15, 20197 yr There is no driver installed for your ethernet controller. From your syslog it looks like there is no controller found. Is there anything in your BIOS settings which relates to your LAN settings?
February 15, 20197 yr 30 minutes ago, Salmack said: ASRock Z390 Pro4 LGA 1151 (300 Series) Intel Z390 HDMI SATA 6Gb/s USB 3.1 ATX Intel Motherboard Lan Device is an Intel I219-V I have an ASRock MB with both an Intel i210 and Intel i219 NIC. Both work in unRAID (they are very common NICs), so, I know your NIC should work just fine. The only thing in my BIOS related to these NIC is an enable/disable setting. If you have it enabled (and there are no other LAN-related BIOS settings), the only thing I can think of is you got a board with a bad NIC.
February 15, 20197 yr Author The NIC is enabled. I know its working because it does the internetFLASH search of r new bios. I know the cables work because I use them on my main system I am on atm. This is bugging the hell out of me.
February 15, 20197 yr Author could it be my version of unRaid is outdated and does not have the driver for this nic
February 15, 20197 yr 2 minutes ago, Salmack said: could it be my version of unRaid is outdated and does not have the driver for this nic Possible, I guess. I think my system goes back to 6.3.5 with the i219 NIC, but, perhaps that is not the case. The i219-V was launched in Q2 2015. You should update unRAID anyway. With no NIC, you have to download it on another machine and do the update manually. Be sure to see this guide on how to update from 6.3.5 to 6.5.0+
February 16, 20197 yr 1 hour ago, Salmack said: Upgrading to the latest did the trick. Thanks for the help, Yeah, I did not notice you were still running 6.3.5 until you asked about upgrading and I checked your diagnostics for that info. Based on your first post, I thought you were current as of a year ago. Bad assumption, my bad.
Archived
This topic is now archived and is closed to further replies.