Unraid install and incompatible network interface hardware?

[TheLinuxGuy]

On a fresh unraid install on my hardware it looks like the network interfaces are not working at all, I have tried both static IP and DHCP settings - this seems to be a driver issue within unraid. What's the best way to troubleshoot or add new drivers?
 

- My motherboard has Intel I219-V and it doesn't work: https://www.asrock.com/MB/Intel/B660M Pro RS/index.asp

- My additional 10G network card on this system: Solarflare dual-SFP+

 

This is from same hardware just booted into Proxmox (running unraid as a VM but want to get it running natively):

root@pgn:~# lshw -class network
  *-network:0
       description: Ethernet interface
       product: SFC9120 10G Ethernet Controller
       vendor: Solarflare Communications
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: enp1s0f0np0
       version: 01
       serial: xxxx
       size: 10Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical fibre 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=sfc driverversion=5.19.7-1-pve duplex=full firmware=6.2.7.1001 rx1 tx1 latency=0 link=yes multicast=yes port=fibre slave=yes speed=10Gbit/s
       resources: irq:16 ioport:5100(size=256) memory:71000000-717fffff memory:71884000-71887fff memory:71840000-7187ffff
  *-network:1
       description: Ethernet interface
       product: SFC9120 10G Ethernet Controller
       vendor: Solarflare Communications
       physical id: 0.1
       bus info: pci@0000:01:00.1
       logical name: enp1s0f1np1
       version: 01
       serial: xxxx
       size: 10Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical fibre 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=sfc driverversion=5.19.7-1-pve duplex=full firmware=6.2.7.1001 rx1 tx1 latency=0 link=yes multicast=yes port=fibre slave=yes speed=10Gbit/s
       resources: irq:17 ioport:5000(size=256) memory:70800000-70ffffff memory:71880000-71883fff memory:71800000-7183ffff
  *-network DISABLED
       description: Ethernet interface
       product: Ethernet Connection (17) I219-V
       vendor: Intel Corporation
       physical id: 1f.6
       bus info: pci@0000:00:1f.6
       logical name: enp0s31f6
       version: 11
       serial: xxx
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=5.19.7-1-pve firmware=0.21-4 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:126 memory:71d00000-71d1ffff

 

[TheLinuxGuy]

21 minutes ago, BRiT said:

Someone is likely going to ask you to post the full diagnostics zip file from an unraid boot up to your next post.

thanks for suggesting.

Here it is.

tower-diagnostics-20221002-1820.zip

[JorgeB]

All NICs are being detected, the 10GbE is unable to get an IP address:

 

Oct  2 18:19:29 Tower  dhcpcd[1201]: br0: probing for an IPv4LL address
Oct  2 18:19:34 Tower  dhcpcd[1201]: br0: using IPv4LL address 169.254.173.54

 

It it connected to a DHCP server?

 

The gigabit link is reporting link down, if that's the main internet NIC make sure a cable is connected and set it as eth0 (Settings -> Network Settings -> Interface Rules) then reboot (you can access the GUI buy booting into GUI mode).

[TheLinuxGuy]

20 hours ago, JorgeB said:

All NICs are being detected, the 10GbE is unable to get an IP address:

 

Oct  2 18:19:29 Tower  dhcpcd[1201]: br0: probing for an IPv4LL address
Oct  2 18:19:34 Tower  dhcpcd[1201]: br0: using IPv4LL address 169.254.173.54

 

It it connected to a DHCP server?

 

The gigabit link is reporting link down, if that's the main internet NIC make sure a cable is connected and set it as eth0 (Settings -> Network Settings -> Interface Rules) then reboot (you can access the GUI buy booting into GUI mode).

Thanks for the hint. I think the default install or file /boot/config/network.cfg randomly selected one of the NICs to use at boot.

I ended up solving this issue by renaming that file and rebooting. Also the NIC it had picked was the 10GB which was configured for LACP/Link aggregation and I think this is why it didn't work out of the box at first. 

After I rebooted with a blank config file for the network it selected eth0 as the 1Gb link and was able to get an IP address.