Hi all,

 

I have spent a while looking through forum posts, etc.  I recently upgraded to 6.11.14.  I have been doing some minor changes to my network and moved the Ethernet cable unraid was plugged in to.  When I plugged it back in I noticed nothing was working - checked cables, etc. all seemed OK.

I tried a reboot, and since then, I can boot in to Unraid (CLI via Monitor), but there is no network connectivity.  I have DHCP configured, which my router has a DHCP reservation for Unraid.  Looking in the logs, unraid gets the IP address, sets up the routes, but no network traffic.  Looking through, I can't see anything too obvious in the logs.  

 

This happens in Safe Mode (No Plugins) as well.  I tried Gui mode, but that boots in to a flashing cursor, with no networking appearing to work.  I can ping the local address, but nothing else on the network.  

I have attached the latest diagnostics I pulled from the CLI by running `diagnostics`.  The one below is from Safe Mode, but can easily post more.  Is there anyone that can provide some support to get me going again?  I am going to look at finding a backup of the flash drive and try that, but I am unsure if that will make a difference.

I have no SSH, no web gui, etc.  

 

tower-diagnostics-20240618-1636.zip

Edited December 11, 20241 yr by damaar

Havent looked into your diags... but sounds like you have a number of network ports on you setup... Its been a min since I have used the GUI or UI but... likely I would use the UI to set all the the network interfaces to use DHCP and carry on from there... 

 

this helps??!?? hope the best for you

 

I wanted to make sure there wasn't any other networking issue going on.  I have spun up an ubuntu live USB on the same device, and found that I get an IP address served from the router, but no network traffic.  Move the cable to another box and everything is fine.  I have removed the DHCP reservation and get assigned a different IP, and still no traffic.  I can't see anything in the the logs to show that the MAC of the NIC in the unraid server is blocked somehow...

 

This is a ASUS PRIME Z790-A WIFI-CSM  which I believe has an Intel 2.5 Gbps NIC, which I am now wondering about whether it is impacted by the disconnects or issues that chipset has...  I226-V

Edited December 11, 20241 yr by damaar

6 minutes ago, mathomas3 said:

Havent looked into your diags... but sounds like you have a number of network ports on you setup... Its been a min since I have used the GUI or UI but... likely I would use the UI to set all the the network interfaces to use DHCP and carry on from there... 

 

this helps??!?? hope the best for you

 

Hey thanks!  I only have one network port on this box.  DHCP configured all fine and appears to be working.  

Try disabling SSL, type in the CLI

use_ssl no

and retest.

Thanks @JorgeB I will give this a go. 

 

I ended up doing a few things last night.  I had myself wondering if it was an issue with my router, so ended up replacing that as a test, but also found the same issue occurred.   I did manage to get it connected again after moving some hardware around, but haven't managed to explain why that worked (I have PFsense router in to Juniper EX2200, then in to unraid.  I have now put a mikrotik in the way between unraid and juniper.).  Looking at switch and router logs and getting a network engineer to have a chat with me at work still doesn't make sense so far, so more troubleshooting required (looked at spanning tree, etc.)

 

While at work today - my Unraid box appears to have stopped some services.  WebGui, SSH and Samba all not working, but docker, vms, etc. all fine.  Looking at the logs, I can't see anything (lots of docker errors):

 

 

Dec 12 06:02:19 Tower kernel: overlayfs: upper fs does not support RENAME_WHITEOUT.
Dec 12 06:02:19 Tower kernel: overlayfs: upper fs does not support RENAME_WHITEOUT.
Dec 12 06:02:19 Tower kernel: overlayfs: upper fs does not support RENAME_WHITEOUT.
Dec 12 06:02:19 Tower kernel: docker0: port 1(vethc823a10) entered blocking state
Dec 12 06:02:19 Tower kernel: docker0: port 1(vethc823a10) entered disabled state
Dec 12 06:02:19 Tower kernel: device vethc823a10 entered promiscuous mode
Dec 12 06:02:19 Tower kernel: eth0: renamed from veth53b4f57
Dec 12 06:02:19 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethc823a10: link becomes ready
Dec 12 06:02:19 Tower kernel: docker0: port 1(vethc823a10) entered blocking state
Dec 12 06:02:19 Tower kernel: docker0: port 1(vethc823a10) entered forwarding state
Dec 12 06:02:19 Tower kernel: docker0: port 1(vethc823a10) entered disabled state
Dec 12 06:02:19 Tower kernel: veth53b4f57: renamed from eth0
Dec 12 06:02:19 Tower kernel: docker0: port 1(vethc823a10) entered disabled state
Dec 12 06:02:19 Tower kernel: device vethc823a10 left promiscuous mode
Dec 12 06:02:19 Tower kernel: docker0: port 1(vethc823a10) entered disabled state

 

Latest diagnostics attached.   Just rebooting the server now, which appears to have come back OK.  Will review logs and look to run another test using the

use_ssl: no

suggestion.  Thanks all!  

 

What might be of interest.  I have run Unraid for years across a few different hardwares (upgrading and migrating each time).  I recently purchased new server hardware and migrated to that.  I did this because I was having a bunch of stability issues (service dying, much like this - not the weird DHCP issue though) so thought I was pushing it a bit too hard (IO_WAIT errors, etc.) so upgraded hardware.  Could be some underlying config issues in my Unraid settings that I have migrated over hardwares?

tower-diagnostics-20241212-1812.zip

Edited December 12, 20241 yr by damaar

I still haven't sorted this issue properly - appears to be some strange networking issue.  I removed the Juniper from my network and will troubleshoot more.

Thanks for the help all.