August 29, 20241 yr I need to remember the following details. It seems that the MAC hardware address has changed mysteriously. My usual NIC hardware address is CC:28:AA:45:6B:E0, but it changed to 88:d7:f6:b6:2f:00 for some reason. I couldn't access the UnRAID GUI from other computers, so I thought the server had crashed. When I went to check, it was still up. After examining the system logs, I noticed that the IP had changed from 192.168.11.110 to 192.168.11.113. This situation is unusual for two reasons: 1) As far as I know, I don't have a device with the hardware address 88:d7:f6:b6:2f:00, but a reverse MAC search shows that it belongs to my motherboard manufacturer (ASUS). 2) I'm still not sure why the MAC hardware address was changed, but 88:d7:f6:b6:2f:00 had claimed -110 in the past but couldn't keep its lease for some reason. I would appreciate any insight on this. Thank you! tower-diagnostics-20240829-0821.zip
August 30, 20241 yr Community Expert The culprit is elsewhere in you LAN: Aug 23 15:46:43 Tower dhcpcd[1680]: br0: 88:d7:f6:b6:2f:00(88:d7:f6:b6:2f:00) claims 192.168.11.110 when UNRAID asks for renewing this address, a different computer has already taken it. So UNRAID is denied the .110 and switches over to a different one. You need to seek your LAN for a device with the MAC 88:d7:f6:b6:2f:00 and check it up (yeah I know this can be very tricky and a pain in the ass). Easiest way usually is to look into the MAC table of the switch to see on which port this device is running on (or on the next switch if it is tunneled). If you only have unmanaged switches you are lost (at least with this method)... Besides a misconfiguration of that device it may also have a bad NIC that cannot receive correctly and therefor generates random requests... BTW your configuration puzzles me a bit... : * you have 2 Nics (one Atlantic, one Intel) but only 1 seems to be configured * both NICS have almost the same MACs, which is impossible when using differnt brands Edited August 30, 20241 yr by MAM59
August 30, 20241 yr Author Thank you MAM59. Yah, I noticed that line indicating that a device claimed the IP address. I found it strange because the device in question was an ASUS device, and I don't have any other computers with an ASUS motherboard (that's why I presumed it was the server itself). I don't have a managed switch, and when I checked the client list for that IP, I didn't find anything. Then it occurred to me that my router is also ASUS. I confirmed that the MAC address belonged to the router. However, I'm confused as to why the router would try to claim that IP since it has never happened before, and it has its own gateway address. Also, in my setup, unRAID is assigned 192.168.11.110 in both the GUI and on the router's DHCP server. Regarding the very similar MAC addresses for the NICs, both are on the motherboard itself, with one being a 10G and the other 2.5G. At the moment, only the 10G is connected. Any other thoughts welcome!
August 30, 20241 yr Community Expert It looks like you have communications problems between the server and the router. Make sure that cables are proper and Flow Control is enabled (and acknowledged) on both sides! check with: root@F:~# ethtool eth0 Settings for eth0: Supported ports: [ FIBRE ] Supported link modes: 1000baseX/Full 10000baseCR/Full 10000baseSR/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: 1000baseX/Full 10000baseCR/Full 10000baseSR/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: 10000Mb/s Duplex: Full Auto-negotiation: off Port: FIBRE PHYAD: 0 Transceiver: internal Supports Wake-on: d Wake-on: d Current message level: 0x00000014 (20) link ifdown Link detected: yes and look for a line "Supported pause frame use:" This should be "symmetric" if port speeds differ, or, like here "Symmetric Receive-only" if 10G speed is on both end. In case of "NO", this would be a bad sign, server and router wont talk within the same slots and there will be a lot of data losses and retries. Speed will be dramattically low when it comes to real transfers. But for now it looks like unseen transmission errors result in data corruption (randomly) So the router reads back its own MAC address from his answer packet. check the cables!!!
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.