captainfeeny Posted January 10, 2021 Share Posted January 10, 2021 (edited) Hi all, I'm having a difficult time with connecting to my server. Sometimes I get an IP and I can connect to it for ~5 minutes before it goes down, sometimes I get the 169 ip that means it wasn't assigned an IP at all. Gigabyte B450i Aorus Pro Wifi Ryzen 5 3600 UNRAID 6.8.3 **DIAGNOSTICS ATTACHED** What I've tried: * deleting config/network.cfg * disabling bonding in config/network.cfg * using a different port on my router * using a known-good ethernet cable * reseating the ethernet cable * updating my bios * looking in the bios for anything related to the LAN connection. There's nothing. * rebooting many times * pinging the router (Destination Unreachable) * pinging from another device to my server (Destination Unreachable) If I get an IP, the ~5 minute disconnection is pretty reliable. Then it showns eth0 down in the UNRAID GUI. If I run ifconfig in the terminal, it shows the correct IP despite there being no connection. One other thing I noticed is that my router (Netgear R6400v2) will show 1000Mbps in the 'Ethernet port state' when the server has a connection, but after the connection drops, it shows the UNRAID ethernet port at 10Mbps. I have two Raspberry Pis connected via ethernet to the router that have been running trouble-free for months. Would anyone have any suggestions of what to try? Thanks! tower-diagnostics-20210110-1600.zip Edited January 30, 2021 by captainfeeny solved Quote Link to comment
Squid Posted January 10, 2021 Share Posted January 10, 2021 Are you able to grab diagnostics after it loses the connection? Quote Link to comment
captainfeeny Posted January 10, 2021 Author Share Posted January 10, 2021 Yep. It's attached to the first post. Quote Link to comment
captainfeeny Posted January 10, 2021 Author Share Posted January 10, 2021 In case, here are other recent diagnostics I ran after network problems. tower-diagnostics-20210109-0908.zip tower-diagnostics-20210109-0639.zip Quote Link to comment
Squid Posted January 10, 2021 Share Posted January 10, 2021 The 2nd one above is the failed one where the router didn't respond to the DHCP request. Have you tried assigning a static IP address within Network settings (and the gateway set to the router)? Quote Link to comment
captainfeeny Posted January 10, 2021 Author Share Posted January 10, 2021 I have a static IP set on the router, but I didn't yet set a static IP or the gateway within UNRAID. I'll give that a shot. Quote Link to comment
captainfeeny Posted January 10, 2021 Author Share Posted January 10, 2021 No luck. I set the static IP and gateway within unraid and the connection died again. Diagnostics attached. tower-diagnostics-20210110-1850.zip Quote Link to comment
Vr2Io Posted January 10, 2021 Share Posted January 10, 2021 3 hours ago, captainfeeny said: show 1000Mbps in the 'Ethernet port state' when the server has a connection, but after the connection drops, it shows the UNRAID ethernet port at 10Mbps. It is physical issue, may be try different router port, ethernet cable (whole path) or mainboard network port issue. Quote Link to comment
captainfeeny Posted January 10, 2021 Author Share Posted January 10, 2021 Ok. It seems it must be the motherboard / lan port then, as I've tried the other options already. Thanks for your help. Quote Link to comment
captainfeeny Posted January 12, 2021 Author Share Posted January 12, 2021 An update: I reset my CMOS and booted Windows from a USB stick. The NIC works fine in Windows 10. I updated to the latest driver and all continues to work. However, when I boot into UNRAID, I'm told I have an IP, ifconfig confirms I have an IP, but the router says the LAN port that UNRAID is attached to is unplugged. (Before it said plugged in but 10Mbps connection.) And I can't ping anything inside or outside the network. What's interesting is that the router says I have a 1000Mbps connection to that port while the motherboard logo is showing, but as soon as UNRAID gets past loading bzroot, the router says that port is unplugged again. It seems something is turning off the NIC during the boot process? Quote Link to comment
Vr2Io Posted January 12, 2021 Share Posted January 12, 2021 (edited) Pls check does wrongly passthrough it or try boot in safe mode. I have same mainboard, but it in standby and not serve for Unraid previously. I could try some test during another new board setup in few days later. Edited January 12, 2021 by Vr2Io Quote Link to comment
captainfeeny Posted January 13, 2021 Author Share Posted January 13, 2021 I solved it by just getting a USB->Ethernet cable. Most probably, my motherboard's NIC is broken. Thanks for your help, though! Quote Link to comment
Vr2Io Posted January 13, 2021 Share Posted January 13, 2021 (edited) Good and thanks update. Gigabyte B450i Aorus Pro Wifi was a good motherboard, it serve well as Windows desktop, surprise it have problem with Unraid. those NIC controller also common in many platform. Edited January 13, 2021 by Vr2Io Quote Link to comment
captainfeeny Posted January 23, 2021 Author Share Posted January 23, 2021 Well, it turns out the USB->Ethernet cable didn't solve anything. I still lose network regularly, and only a reboot brings it back. Sometimes the network goes down after minutes, sometimes after several hours. I finally caught this in my syslog following the latest network drop. If it means anything I was downloading a Windows ISO at the time, so maybe the connection was flooded? It's probably coincidence. Would anyone know what might be causing this? kernel: ------------[ cut here ]------------ Jan 23 18:26:37 potzdorf kernel: NETDEV WATCHDOG: eth0 (ax88179_178a): transmit queue 0 timed out Jan 23 18:26:37 potzdorf kernel: WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:465 dev_watchdog+0x161/0x1bb Jan 23 18:26:37 potzdorf kernel: Modules linked in: xt_nat vhost_net tun vhost tap kvm_amd ccp kvm veth md_mod xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs nfsd lockd grace sunrpc k10temp it87 hwmon_vid edac_mce_amd btusb btrtl btbcm ax88179_178a btintel bluetooth usbnet crct10dif_pclmul crc32_pclmul crc32c_intel i2c_piix4 ghash_clmulni_intel wmi_bmof i2c_core pcbc aesni_intel aes_x86_64 crypto_simd mii ahci ecdh_generic cryptd nvme glue_helper nvme_core libahci wmi button [last unloaded: md_mod] Jan 23 18:26:37 potzdorf kernel: CPU: 4 PID: 0 Comm: swapper/4 Not tainted 4.19.107-Unraid #1 Jan 23 18:26:37 potzdorf kernel: Hardware name: Gigabyte Technology Co., Ltd. B450 I AORUS PRO WIFI/B450 I AORUS PRO WIFI-CF, BIOS F60e 12/09/2020 Jan 23 18:26:37 potzdorf kernel: RIP: 0010:dev_watchdog+0x161/0x1bb Jan 23 18:26:37 potzdorf kernel: Code: 5f 94 00 00 75 39 48 89 ef c6 05 4e 5f 94 00 01 e8 a1 a8 fd ff 44 89 e9 48 89 ee 48 c7 c7 57 2a da 81 48 89 c2 e8 cd 0b af ff <0f> 0b eb 11 41 ff c5 48 81 c2 40 01 00 00 41 39 cd 75 95 eb 13 48 Jan 23 18:26:37 potzdorf kernel: RSP: 0018:ffff88881e703ea0 EFLAGS: 00010286 Jan 23 18:26:37 potzdorf kernel: RAX: 0000000000000000 RBX: ffff88881aa53438 RCX: 000000000000047a Jan 23 18:26:37 potzdorf kernel: RDX: 0000000000000001 RSI: 0000000000000002 RDI: 0000000000000247 Jan 23 18:26:37 potzdorf kernel: RBP: ffff88881aa53000 R08: 0000000000000003 R09: 0000000000015800 Jan 23 18:26:37 potzdorf kernel: R10: 0000000000000000 R11: 0000000000000060 R12: ffff88881aa5341c Jan 23 18:26:37 potzdorf kernel: R13: 0000000000000000 R14: ffff888819a32280 R15: 0000000000000004 Jan 23 18:26:37 potzdorf kernel: FS: 0000000000000000(0000) GS:ffff88881e700000(0000) knlGS:0000000000000000 Jan 23 18:26:37 potzdorf kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 23 18:26:37 potzdorf kernel: CR2: 00000000006cb698 CR3: 00000007e58be000 CR4: 0000000000340ee0 Jan 23 18:26:37 potzdorf kernel: Call Trace: Jan 23 18:26:37 potzdorf kernel: <IRQ> Jan 23 18:26:37 potzdorf kernel: call_timer_fn+0x18/0x7b Jan 23 18:26:37 potzdorf kernel: ? qdisc_reset+0xc0/0xc0 Jan 23 18:26:37 potzdorf kernel: expire_timers+0x7e/0x8d Jan 23 18:26:37 potzdorf kernel: run_timer_softirq+0x72/0x120 Jan 23 18:26:37 potzdorf kernel: ? __hrtimer_run_queues+0xc3/0x10b Jan 23 18:26:37 potzdorf kernel: ? ktime_get+0x44/0x95 Jan 23 18:26:37 potzdorf kernel: __do_softirq+0xc9/0x1d7 Jan 23 18:26:37 potzdorf kernel: irq_exit+0x5e/0x9d Jan 23 18:26:37 potzdorf kernel: smp_apic_timer_interrupt+0x80/0x93 Jan 23 18:26:37 potzdorf kernel: apic_timer_interrupt+0xf/0x20 Jan 23 18:26:37 potzdorf kernel: </IRQ> Jan 23 18:26:37 potzdorf kernel: RIP: 0010:native_safe_halt+0xe/0xf Jan 23 18:26:37 potzdorf kernel: Code: 60 02 df f0 83 44 24 fc 00 48 8b 00 a8 08 74 0b 65 81 25 55 a9 98 7e ff ff ff 7f c3 e9 07 00 00 00 0f 00 2d fa c4 57 00 fb f4 <c3> e9 07 00 00 00 0f 00 2d eb c4 57 00 f4 c3 53 e8 44 0f a1 ff 65 Jan 23 18:26:37 potzdorf kernel: RSP: 0018:ffffc9000326bec8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13 Jan 23 18:26:37 potzdorf kernel: RAX: 0000000000000004 RBX: ffff88881af95100 RCX: 0000000000000020 Jan 23 18:26:37 potzdorf kernel: RDX: 000000000462cbe6 RSI: 0000000000000083 RDI: ffff88881e7207c0 Jan 23 18:26:37 potzdorf kernel: RBP: 0000000000000000 R08: ffff88881e71cb00 R09: 0000000000000000 Jan 23 18:26:37 potzdorf kernel: R10: 0000000000000004 R11: ffff88881e71fb40 R12: 0000000000000000 Jan 23 18:26:37 potzdorf kernel: R13: 0000000000000004 R14: 0000000000000000 R15: 0000000000000000 Jan 23 18:26:37 potzdorf kernel: default_idle+0xc/0x16 Jan 23 18:26:37 potzdorf kernel: do_idle+0xdb/0x1fc Jan 23 18:26:37 potzdorf kernel: cpu_startup_entry+0x6a/0x6c Jan 23 18:26:37 potzdorf kernel: start_secondary+0x197/0x1b2 Jan 23 18:26:37 potzdorf kernel: secondary_startup_64+0xa4/0xb0 Jan 23 18:26:37 potzdorf kernel: ---[ end trace 11126c867701d57a ]--- Quote Link to comment
JorgeB Posted January 24, 2021 Share Posted January 24, 2021 That looks like a NIC/driver problem, don't remember seeing that NIC used with Unraid before, so not sure if it's reliable, try a different one if possible, Intel recommended. Quote Link to comment
captainfeeny Posted January 30, 2021 Author Share Posted January 30, 2021 For posterity: tldr; Change your motherboard. After USB ethernet proved unstable as well, I plugged in both the USB ethernet and the motherboard NIC and achieved stability. The motheboard NIC still didn't work, but simply having it plugged in did... something? In any case, it seemed to me the problem was with the motherboard. So I changed it out for an MSI B450i, which I've been running for a day without any of the issues I had with the Gigabyte B450i. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.