September 13, 20223 yr I wonder if someone can help me troubleshoot this issue. What happens is when server starts the NIC eth0 (on MB) is working normally, judging by flashing lights on the Ethernet port. At some point during Unraid start-up the lights go off, and never come back. I tested it with another PCI NIC and the same happens, on both ports at the same time. After reboot, the port lights start normally again, until the very same point during boot so physical connections are all ok. This has happened during the day, no changes were made to the configuration. Server became unresponsive so I have rebooted it gracefully. Obviously I have no access to Web interface, nor to SSH. When booting into safemode or GUI mode, sometimes GUI will show eth0 as "interface down" and sometimes it will not list it at all in interfaces. IFCONFIG lists no such interface. I have tried reboots, different Ethernet cables, another NIC, different switch, static and DHCP assigned IP. Can someone help me to make sense of the logs (included) to troubleshoot? Thank you. kraken-diagnostics-20220912-2053.zip
September 13, 20223 yr ethtool is showing that there is no cable attached. Try a different one and a different port on the switch.
September 13, 20223 yr Community Expert No link is being detect on either NIC, also eth1 is missing from network rules, delete network-rules.cfg, reboot and post new diags.
September 13, 20223 yr Author 3 hours ago, Squid said: ethtool is showing that there is no cable attached. Try a different one and a different port on the switch. I did that. I tried different cables and switch. Also booted live Ubuntu, and it "sees" the port and communicates over it. When Unraid just starts to boot the port looks like this: [image]https://photos.app.goo.gl/GZ7ZbyeJHfnNfrn69[/image] A couple of seconds later (Unraid still booting) it looks like this: [image]https://photos.app.goo.gl/9Qu5pyVz7oZR1cEq6[/image] 3 hours ago, JorgeB said: No link is being detect on either NIC, also eth1 is missing from network rules, delete network-rules.cfg, reboot and post new diags. Done. New diagnostics attachedkraken-diagnostics-20220913-1824.zip
September 13, 20223 yr Community Expert Solution Still nothing, and the other Intel NIC is now also missing, upgrade to v6.10.3 since there were changes to the NIC rules script and post new diags, might also be a good idea to delete/rename network.cfg to use the default LAN settings.
September 13, 20223 yr Author 15 minutes ago, JorgeB said: Still nothing, and the other Intel NIC is now also missing, upgrade to v6.10.3 since there were changes to the NIC rules script and post new diags, might also be a good idea to delete/rename network.cfg to use the default LAN settings. How can I update it without it connected to network?
September 13, 20223 yr Community Expert Download the v6.10.3 zip and extract al the bz* files to the flash drive overwriting existing ones.
September 14, 20223 yr Author 19 hours ago, JorgeB said: Still nothing, and the other Intel NIC is now also missing, upgrade to v6.10.3 since there were changes to the NIC rules script and post new diags, might also be a good idea to delete/rename network.cfg to use the default LAN settings. Before upgrading I have deleted network.cfg just to test and VOILA, that fixed the problem, it works. For some reason the physical port is actually eth2, not eth0, and eth0 and eth2 are bridged together. Not sure why this is this way, but also not sure how was it initially, so I take it. It works, and that's all I need
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.