July 24, 20196 yr Hello All, Hope you are all ok and in the mood to help me. I have an issue with my Unraid box that has gone haywire completely. I have 3 nic on that box : 1969:e091]02:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 13) -> This is the onboard one [10ec:8168]03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) -> PCIe [10ec:8168]04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) -> PCIe The problem am having is that the box seems to detect more than 3 on the UI. I have : eth0 eth2 eth115 eth116 The funny part is that the interface rules shows only eth0 and eth2 but both are showing with the same MAC address.🤯 I don't know what to do with this. Can someone help me ? Attached is the diagnostic from the UI. Let me know if you need more information. Chris omega-diagnostics-20190724-0717.zip Edited July 24, 20196 yr by PerniciousDuck Issue Solved
July 24, 20196 yr Author I think the problem comes from the config/network-rules.cfg file, but I tried deleting it and it just recreates itself with the same MAC on all ports.
July 24, 20196 yr Community Expert Delete both config/network.cg and config/network-rules.cfg, then reboot, but I've seen myself sometimes extra NICs being detected, it happens it 2 of my servers, where a NIC is detected as eth3 and then eth4, but for now it remains working as eth4
July 24, 20196 yr 4 hours ago, PerniciousDuck said: The problem am having is that the box seems to detect more than 3 on the UI. I have : eth0 eth2 eth115 eth116 Then, in network setting page bottom, adjust the NIC order by pull down selection, place the management NIC be eth0. Edited July 24, 20196 yr by Benson
July 24, 20196 yr Author Hello Johnnie, Benson, @johnnie.black I did that and still have the same look on the UI. @Benson I don't undestand what you mean. If you are talking about the Interface Rules section, then I can't because all Nics have the same MAC Edited July 24, 20196 yr by PerniciousDuck
July 24, 20196 yr Author I made a PDF of the whole page for you to see the it. Omega_NetworkSettings.pdf
July 24, 20196 yr 16 minutes ago, PerniciousDuck said: Hello Johnnie, Benson, @johnnie.black I did that and still have the same look on the UI. @Benson I don't undestand what you mean. If you are talking about the Interface Rules section, then I can't because all Nics have the same MAC Yes, this setion, wried all same MAC and only 2 NIC. Also the 3rd and 4th NIC was eth115 eth116 not usual eth3 eth4. Could you check BIOS too ? Does in teaming ? Edited July 24, 20196 yr by Benson
July 24, 20196 yr Author 9 minutes ago, Benson said: Yes, this setion, wried all same MAC and only 2 NIC. Also the 3rd and 4th NIC was eth115 eth116 not usual eth3 eth4. Could you check BIOS too ? Does in teaming ? Do you mean there could be an option in my BIOS for teaming cards? Never thought about that. I'll check
July 24, 20196 yr 15 minutes ago, PerniciousDuck said: Do you mean there could be an option in my BIOS for teaming cards? Never thought about that. I'll check May be, also pls try disable IOMMU ( Intel VT-d, AMD IOMMU ) in BIOS.
July 24, 20196 yr Author Luckly for you ... and unfortunately for me... My CPU does not support IOMMU
July 24, 20196 yr Community Expert Looking at the syslog both NICs have the same MAC address, so it's not an Unraid problem: Jul 24 09:05:34 Omega kernel: r8169 0000:03:00.0 eth1: RTL8168e/8111e, 50:3e:aa:07:34:fa, XID 2c200000, IRQ 27 Jul 24 09:05:34 Omega kernel: r8169 0000:03:00.0 eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko] Jul 24 09:05:34 Omega kernel: r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control Jul 24 09:05:34 Omega kernel: r8169 0000:04:00.0: enabling device (0000 -> 0003) Jul 24 09:05:34 Omega kernel: libphy: r8169: probed Jul 24 09:05:34 Omega kernel: r8169 0000:04:00.0 eth2: RTL8168e/8111e, 50:3e:aa:07:34:fa, XID 2c200000, IRQ 28 Jul 24 09:05:34 Omega kernel: r8169 0000:04:00.0 eth2: jumbo features [frames: 9200 bytes, tx checksumming: ko] Jul 24 09:05:34 Omega kernel: cryptd: max_cpu_qlen set to 1000
July 24, 20196 yr Author I can understand both R8169 having the same MAC, that happens more that I care to say... but why the Atheros has it too? Am I the unluckyest guy in the planet? 😫
July 24, 20196 yr Community Expert Just now, PerniciousDuck said: but why the Atheros has it too? Yeah, didn't notice that, very weird, not possible the 3 have the same MAC.
July 24, 20196 yr That MAC is from the TP-Link block, not realtek or atheros. Something is VERY screwy here. Do you have a TP-Link router?
July 24, 20196 yr Author I used to have a D-Link managed switch, Now all network is Ubiquiti. I'll check that command when I get home. Imight have some unamanaged tplink switches in the sitting room, but it's not nowhere near the Unraid box. I can disconnect that as well.
July 24, 20196 yr Author 1 hour ago, jonathanm said: What is the output of ethtool -P eth0 ? Run it against eth1 and eth2 as well. There is definitly something wrong with my box : Linux 4.19.56-Unraid. root@Omega:~# ethtool -P eth0 Cannot read permanent address: No such device root@Omega:~# ethtool -P eth1 Cannot read permanent address: No such device root@Omega:~# ethtool -P eth2 Permanent address: 50:3e:aa:07:34:fa root@Omega:~# ethtool -P eth115 Permanent address: 50:3e:aa:07:34:fa root@Omega:~# ethtool -P eth116 Permanent address: 50:3e:aa:07:34:fa root@Omega:~# This is the output of "ip a" root@Omega:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN group default qlen 1000 link/gre 0.0.0.0 brd 0.0.0.0 4: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 6: ip_vti0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 11: eth2: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq master br2 state UP group default qlen 1000 link/ether 50:3e:aa:07:34:fa brd ff:ff:ff:ff:ff:ff inet6 fe80::523e:aaff:fe07:34fa/64 scope link valid_lft forever preferred_lft forever 12: eth116: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 50:3e:aa:07:34:fa brd ff:ff:ff:ff:ff:ff 13: eth115: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 50:3e:aa:07:34:fa brd ff:ff:ff:ff:ff:ff 14: br2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 50:3e:aa:07:34:fa brd ff:ff:ff:ff:ff:ff inet 192.168.1.254/24 brd 192.168.1.255 scope global noprefixroute br2 valid_lft forever preferred_lft forever inet6 fe80::90c8:3bff:fe8a:b6a4/64 scope link valid_lft forever preferred_lft forever
July 24, 20196 yr At this point, I think it's time to branch out a little. See what results you get with other live distro's, add NIC's to the slots and see what address they show, see if there are updates to your BIOS, reset CMOS settings, etc. This is something I have never seen before, and my google-fu is failing to find other examples to compare.
July 24, 20196 yr Author Yeah my white belt google-fu did not find anything that's why I resorted to the forum I'll test several things and get back to you. Thanks for all the help
July 24, 20196 yr Author Hello Guys ! Thank you all for your help. I was able to bring the configuration back online. If anybody stumbles on this post, this is what I did : Reset the mobo CMOS Delete the network.cfg and network-rules.cfg Now the UI shows everything as expected :
July 24, 20196 yr That is so strange. Now I'm wondering, did you, at any point during troubleshooting, cut power completely? I realize you probably cut power when you reset CMOS, I'm wondering if the power cut was all that was necessary. My hypothesis is that the WOL functionality that keeps the NIC's functional and watching for magic packets was keeping the NIC's from getting properly reset when you rebooted or powered down.
July 24, 20196 yr Author Not at all. I have a button on the Mobo for reseting the CMOS. So except if that button does power recycle, I did not at all Edited July 24, 20196 yr by PerniciousDuck Typos
Archived
This topic is now archived and is closed to further replies.