Hi, I am building a new system and all of a sudden unraid has stopped connecting to my network. At first it booted fine and I was able to buy a license and set up cache disks. But when I shutdown to add a couple of drives and restarted it has stopped connecting and uses a 169.x address every time.

 

I have tried a fresh install of unraid, connecting to a couple of different routers (virgin, google etc) to rule out any issue with the routers. I have also tried static and dynamic Ips. I've also tried assigning a static ip at the router instead of within the unraid config. Finally, I have also tried deleting network.cfg and rebooting as suggested in other threads. None of this has worked for me.

 

There are no obvious errors in the logs (to my eyes atleast). Attached are the diagnostics and syslogs.

 

I can see that the router offers a IP, but instead of accepting it, dhcpcd probes for a IPv4LL address and proceeds with a 169.x address

 

Nov 29 00:50:31 Tower dhcpcd[2103]: br0: soliciting a DHCP lease
Nov 29 00:50:31 Tower dhcpcd[2103]: br0: offered 192.168.3.35 from 192.168.3.1
Nov 29 00:50:36 Tower dhcpcd[2103]: br0: probing for an IPv4LL address
Nov 29 00:50:41 Tower dhcpcd[2103]: br0: using IPv4LL address 169.254.50.59
Nov 29 00:50:41 Tower dhcpcd[2103]: br0: adding route to 169.254.0.0/16

Appreciate any help

tower-diagnostics-20201129-0051.zip syslog-2020-11-29-00-52.txt

8 hours ago, krthk said:

At first it booted fine and I was able to buy a license and set up cache disks.

Surprised it ever worked, you need to use the latest beta for that NIC to be correctly supported, you can download it from here:

https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.9.0-beta35-x86_64.zip

Thank you, that has worked for me 😊. Wish I had asked this on day 1 rather than wasting a week on my own