Unable to set IPv4 address in Unraid 6.9.2

[SteveJ]

Hello,

 

I've been trying to install Unraid 6.9.2 on a Gigabyte GA-890GPA-UD3H system.   Everything seems fine except that it does not allocate an IPv4 address and the server is invisible to the network.   The diagnostics file is attached.

 

As part of the many things i've tried, I also tried building a server based on version 6.8.3.   This is an excerpt from the log when I tried booting that:

 

Nov 12 08:58:22 Tower-UK dhcpcd[1460]: br0: soliciting a DHCP lease
Nov 12 08:58:27 Tower-UK dhcpcd[1460]: br0: probing for an IPv4LL address
Nov 12 08:58:29 Tower-UK dhcpcd[1460]: br0: offered 192.168.1.127 from 192.168.1.1
Nov 12 08:58:29 Tower-UK dhcpcd[1460]: br0: probing address 192.168.1.127/24
Nov 12 08:58:31 Tower-UK dhcpcd[1460]: br0: using IPv4LL address 169.254.51.148
Nov 12 08:58:31 Tower-UK dhcpcd[1460]: br0: adding route to 169.254.0.0/16
Nov 12 08:58:31 Tower-UK dhcpcd[1460]: br0: adding default route
Nov 12 08:58:31 Tower-UK dhcpcd[1460]: forked to background, child pid 1502
Nov 12 08:58:31 Tower-UK rc.inet1: ip link set br0 up

 

So, under 6.8.3 it's clearly communicating with the DHCP server and an IP address is being allocated, but for some reason Unraid decides to use a 169 address, or at least that's what it says.   However, the 192.168.1.127 address is indeed being used by the server.  It's visible on the network and I can access the management console from another PC.  So, this rules out any problems with the NIC, cable or DHCP server.

 

To summarise, in version 6.8.3, it it does obtain an IP address and uses it, even though it tells me that it's allocated a 169 address.  But in 6.9.2, its not able to obtain an IP address at all, or at least that's what it's suggesting in the log.

 

I'm on the verge of giving up right now, but does anyone have any ideas?   I've played around with the BIOS and disabled everything that I don't need.  I have a USB 2.0 Sandisk Cruzer booting off a USB 2.0 port.  This really seems like a 6.8.3 vs 6.9.2 issue though.

 

I don't really want to build a 6.8.3 server knowing that there are issues with a later version of the OS, or i'll never be able to upgrade.

 

Many thanks in anticipation for your help.

 

 

 

tower-uk-diagnostics-20211112-0935.zip

[JorgeB]

r8169 0000:03:00.0: no dedicated PHY driver found for PHY ID 0xc2077002, maybe realtek.ko needs to be added to initramfs?

 

Driver issue, you could try v6.10-rc2

[SteveJ]

Thanks for the reply, but sadly v6.10-rc2 didn't work either.  Diagnostics attached.   Still the same outcome. I got a few different messages though including "eth0 does not exist".

 

The network card is onboard.  I guess I could try a new card, but sadly I gave away all the cards I had a few months back and i'm not in the mood to buy another one.

 

It's strange that it kinda worked ok with 6.8.3 but not with later versions, which could be worrying for anyone planning an upgrade.

 

 

tower-diagnostics-20211112-1506.zip

[JorgeB]

Same issue, Realtek driver support has only been iffy with Linux, I would recommend getting an Intel NIC if possible.

[Frank1940]

@SteveJ, you could research and find out what RealTek Chip Set is being used on this board.  Then using Google, try to find if/when this chip set is going to be included into the Linux drivers.   You could then provide this Info to LimeTech via a Feature Request to include that driver set.  (There is often a delay between RealTek introduces a new chip set and when they release the working drivers for Linux.  The last I heard, LimeTech will not include the drivers that RealTek sometimes releases for Linux but instead waits until they are included in a Linux release.)

[Squid]

The board is 11+ years old.  The driver being used (RTL-8111 et al) is quite common, so I'd surmise that Realtek dropped support for the actual chipset being used in latter versions of the Kernel.  Spend $30 and grab an add-on Intel card.

 

(Although, there is an update to the BIOS available which states "Support Upgraded LAN")

[SteveJ]

Just to close the loop on this, updating to the latest BIOS (FD to FF) didn't fix the problem. 

 

I therefore bought a new Intel Pro 100/S PCI card and Unraid is now working perfectly.

 

Thanks everyone for your assistance.