i recently upgraded to 10g fiber network so i dont need my 4 port network card i was using for 

IoT, Lan, DMZ, etc

i use my on board nic as Management port  and the fiber port  as for the others using them as  Vlans

10 cameras

20 IoT

etc

Oct 24 11:38:10 Tardis root: Fix Common Problems: Error: Multiple NICs on the same IPv4 network
Oct 24 11:38:10 Tardis root: Fix Common Problems: Error: Multiple NICs on the same IPv4 network
Oct 24 11:38:10 Tardis root: Fix Common Problems: Error: Multiple NICs on the same IPv4 network

but i getting error nows  I got multiple nics on the same nic.. i cant see nothing under network settings    they all seperated  ok

what can i do to fix that?

 

and i ran the fix common problems and all it does it hang  on the scanning part  sits there 15 min+    and nothing happens  just hangs

tardis-diagnostics-20241024-2056.zip

Edited October 25, 20241 yr by comet424

you may need to install the melnox plugin for the fiber network driver.

if you type lspci do you see the card?

i been using the 10gig for a bit...  but here is some screen  shots and i left the fix common issues running it still stuck more then 12 hours  on the screen

 

 

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:03.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream
03:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO
05:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
06:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller
08:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
09:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
09:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
09:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
0a:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
0b:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
0c:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Network Connection (rev 01)
0e:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05)
0f:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function
10:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
10:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP
10:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
10:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller

 

Edited October 25, 20241 yr by comet424

i did a new reboot and finally got fix common issues to work it didnt hang  and its giving this ip address issue...   but dunno how to fix it do u ignore it button  or is there a proper way to fix it?

 

 

 

i tried deleting this ip  under network settingss they the br1 - br5  but it wont let me delete this ip from the routing table

Edited October 25, 20241 yr by comet424

you have 3 interfaces with a ip conflict.

or otherwise set to static with no configuration... ?168.254.0.0? are these interfaces connected to a network?

Regardless, you will need to create a bridge interface. Assign the ip address to the BR# interface...
attached the 3 interfaces to the BR# created...

Example terminal commands.

ATM, per your pictures, as the data shows the same Ip asigined to the nics with the same ip.

Sadly interenet TCP ip rules:
1 nic per a different IP address.
the ip is unusable as there is no route for the defualt route to dev interface#. You can't have the same ip on mutiple nic. 

This is where bond vs bridge come in,

With the reboot it would help if you post another diag. as it seems more like the interfaces were assigned a 192.168.x.x address but not applying to the interfaces. and it appears that you have mutiple br assigned casuing issues...



Review forum post going over some basics in linux networks:

 

Edited October 25, 20241 yr by bmartino1

ill have to read the links later

but from the pics above.. show i only have 2 network interfaces i use

1 10gig 

1 1gig    

interfaces

i used bridge on  the 10gig to do that 3 Vlans

Lan (br) br0 or whatever you call main  192.168.0.0

br10 = Cameras Vlan   192.168.10.0

br.20 = IoT Vlan          192.168.20.0

br.40 = DMZ Vlan        192.168.40.0

 

and then 

on the 1 gig    is the management port 192.168.30.0

 

now the 169.  isnt that for when an ip address doesnt work anymore?

here is the diagnostic now

can you see if it still thinks the old card is in there? 

where would there be...  as there is br1 br2 br3 br4 br5   and maybe thos are pointing to the oild card

and the br.10 br.20  br.40   are pointing to the new 10 gig card?

 

tardis-diagnostics-20241025-1342.zip

That sounds right/correct.

As there is alot is going on there. you may need to delete or bridges that reflect to the older card that no longer have a connection.

Thank you for posting the diag as clearly some other data has changed between the two. And I will need to review them to better assist on potential commands and my recommendation regarding how to fix.

As it appears that you moved off too 2x nic with activate connections. so 1 network type to make your current state, and then to fix other  ip routes and other interface issues.

 

Edited October 25, 20241 yr by bmartino1

like i try clicking the garbage can to delete routes that does nothing...    i tried looking in the flash drive  under network.cfg to see if there was old card that i moved from  i didnt see   

i didnt get this error till after i unplug the card

so what i did was i had the 4 port card in  that had  Iot Cameras Dmz  

and then i made the vlans on the 10gig  made sure it got that working... and then i  i modified the network cfg  to point from the network 4 card   to point to the 10gig to fix the bridge issues i had... and no issues   but now i decided to pull the 4 port card out to use it in another comp...   and when i boot up  thats how i noticed  now  i getting this error

 

and i not able to delete any routes  from that routing table 

 

hope that helps  

Thank you for that additional information. Since that server is experiencing this, I would recommend an network config purge. This means deleting the netwrok.cfg files from the boot device, rebbot. Then unraid at boot would then recreate the entire network config at boot..., booting into dhcp at first boot and you would need to reset up any vlans, bridges, ip route, configurations.

It is werid that your unable to delete. But some routes are made by default due to the exisitence of other bridges.

My Working Theroy atm:
When you pulled the previous nic card the PCI IRQ and pcie device names changed, sometimes that change will also change the name of interface names. 

You have a lot of exisitng br# interface calling eth1 to conect to eth3/4/etc that no longer exist. But without the abilty to remove the bridge / route I think a netwrok reset would be best.

Use the forum as you saved quite a bit already.
So heree are my recommend steps.

Step 1 make a falsh drive backup:
Main Tab > Flash > Flash backup
*This is a backup that you can restore to the current USB to recover form

Step 2:
shutdown all dockers, VM, LXC...
*Turn off autostart of any VM/LXC/Docker
*Stop all vm, lxc, dockers
-setting docker > enable no... apply
-settings VM Manger > Enabled No... apply

Step 3 Delete some config files.
open terminal / web ttd
cd /boot/config

ls -a

 your mainly looking to find network.cfg ther are some other file we want to remove as well (theses fiels are backed up in the flash backup made earlier...



We want to remove any file that starts with network...

As This is the confg file that loads at boot that setups networking. 

 

rm -f network*

Then reboot.
This will reset unraids network configuration back to netwrok default.

ok that seemed to fix the issue...  i dont have that big list..  i had to google what a LXC is  not 100% sure what it is  some linux container or something but i blew out the network configs and re did  and adjusted the order  and thats seemed to fix it...  i still get this warning  and i not sure is there a way to fix it?

 

Oct 26 11:52:08 Tardis kernel: igb 0000:08:00.0: The NVM Checksum Is Not Valid
Oct 26 11:52:08 Tardis kernel: igb: probe of 0000:08:00.0 failed with error -5

ive seen this before i tried googling i never found how u fix it.. is there a way to fix this?

and these routes look better now least seem to be   i appreciate the help so far... as that was frustrating and didnt know what was going on

The error you're seeing—"NVM Checksum Is Not Valid"—indicates an issue with the Intel NIC's Non-Volatile Memory (NVM) checksum. This usually points to a problem with the NIC's firmware or configuration. Here are some steps to help troubleshoot and potentially resolve this:
 

1. Update the NIC Firmware: Intel periodically releases firmware updates for their network adapters. If an update is available, applying it might resolve the checksum error. You’ll need to download the firmware update from Intel’s support website and follow their instructions to apply it.
 

2. Update the Driver: Ensure that you’re using the latest version of the igb driver for your NIC. This can sometimes resolve compatibility or checksum validation issues.

3. Reset NVM: Some Intel NICs allow a reset of the NVM to reinitialize the configuration. Check Intel’s documentation on your specific NIC model to see if this is possible.

4. Re-seat the NIC: Power down your Unraid server and physically re-seat the NIC in its slot to ensure that the connection is secure.

5. BIOS Update: Sometimes, updating the motherboard BIOS can help with hardware compatibility issues, including NIC-related problems.


I would have you install and double check the firmware on the nic...


 

spoke too soon  got basiclly same error...  is it do do with the shim-br   what is a shim  in the routes?

Oct 26 13:21:20 Tardis root: Error response from daemon: network with name br0 already exists
Oct 26 13:21:21 Tardis root: Error response from daemon: network with name br0.10 already exists
Oct 26 13:21:21 Tardis root: Error response from daemon: network with name br0.20 already exists
Oct 26 13:21:21 Tardis root: Error response from daemon: network with name br0.40 already exists

 

tardis-diagnostics-20241027-1531.zip

and is the nvm non violioate memory what does that all do... is it a serious thing?  ill look that up  your steps  and try  i have updated the bios and that seems to keep coming up but ill try the other steps

there doesnt seem to be firmware updates for this nic   from googling etc  read about only has a ROM    and cant upgrade..  so i not sure???  only found drivers...  

and i installed  the mellanox  but dunno how to use it  as its command line  so far i only installed it

Hard to say. since bios/firmware/other are supposedly all uptodate, this may be a linux / Unraid kernel issues. Future release may fix this...

Is it safe to ignore. knda... This affects things like preomesic mode, tcp/ip, validation and other network packets...

Yes, this error can be ignored if the NIC is not critical for your setup or if you have other network interfaces handling traffic effectively.(which it appears you are) This could be casued by mtu/jumbo frames....

Since it’s a checksum issue, it doesn’t necessarily indicate immediate failure but rather a mismatch or validation error that may get resolved with a future Unraid kernel update....
 

However, if this NIC is your primary or only network connection, ignoring the error might impact network stability. You could wait to see if a kernel update resolves it, but if you experience network issues, consider trying the troubleshooting steps mentioned above... or temporarily using another NIC if available.

i would ask for another diag. as your network has changed and i wiould need to check some things such as cmdline, iommu otpions, psm power options...

We could potential add a syslinux line.

or do some things to reset teh drive on the nic such as:

Example:

# Unbind the device
echo "0000:08:00.0" | sudo tee /sys/bus/pci/devices/0000:08:00.0/driver/unbind

# Rebind the device
echo "0000:08:00.0" | sudo tee /sys/bus/pci/drivers/igb/bind

 

echo 1 | sudo tee /sys/bus/pci/rescan

and check system log to verify.

but if its working i would ignore it for now...

so the 10gig nic is my main  it routes all the traffic.. i only use the onboard nic  to be able to access unraid or wake on lan it...  but all traffic all  vms dockers all now go through the 10giger  so  is my 10 gig nic firmware up to date can you tell?

 

and i went to the plugin for the mellenox  it doesnt show any info about this intel card  probably cuz its not a mellenox card

 

as for the diagnostic  i did upload another diagnostic  with the error  where you see the error logs  but ill post a new diag   i took the diganostic like an hour ago

 

and u want me to try to unbind and bind now what does it do?

does that disconnect the network card  so should i connect to the 192.168.30.3  then  on my on board..

and does the shim-  go away that seems to be the duplicates  is that where the error for the duplicates  these shims where werever they came from

tardis-diagnostics-20241027-1716.zip

unbind bind is more a pcie pasthorugh to tell the host unraid to take back the device passed to a vm as example. What i was refering to there was an example of linux termianl comands to touch and mess with the device to atempte to restart it with out having to reboot the whole machine. To make sure drivers load etc... its be more 

The rescan command was the one i was refeing too at time of writing to confirm detection and is esentail the windwos equivalent of Plug and Play.
modprobe igb

This would caue a temp network outage if that nic was in use.

reviewing diag thank you

Based on the logs and system output, it looks like the system does indeed recognize and initialize all NICs, despite the initial NVM checksum error on the Intel NIC at PCI address 08:00.0. Since the network interface subsequently loads successfully and is able to negotiate settings, link detection, and IP assignment, this error appears non-critical, likely stemming from a transient or minor firmware issue. Here’s a breakdown and final analysis:

Key Observations

Driver Initialization: The Intel igb and ixgbe drivers load as expected, initializing both the Gigabit (I211) and 10 Gigabit (ixgbe) NICs without further errors.

Link and Speed: The interfaces are detected with appropriate link speeds (10Gbps for the ixgbe NIC and 1Gbps for the I211 NIC) and set to full duplex.

NVM Checksum Error Context: The "NVM Checksum Is Not Valid" warning from the igb driver appears early during PCIe device detection, but since the NIC successfully initializes afterward and functions as expected, it doesn’t seem to impact performance or stability.

Network Connectivity: The syslog confirms that network settings, including IP assignment and connectivity, are operational.

Conclusion

Since the NIC fully loads and functions as expected, you can likely ignore the checksum warning as a non-critical issue, especially if Unraid’s network performance is unaffected. This error is often resolved with a future firmware or driver update, and it shouldn’t hinder your system's stability or network operations in its current state. However, if you do encounter network connectivity issues down the line, you might consider a firmware update for the NIC if available.

Ok Lets review:
I see that you have a custom go config.

please confirm WOL command is correct interface:

#Enable Wake On Lan To Work
ethtool -s eth0 wol g

It is weird that you have a modprobe black list for the realtek driver and have the plugin installed.
Did you follow the forum or plugin regarding that?
"blacklist r8169"

Lets review your network per diag as Unraid defined:

Interface Ip and cdir Sumbnet:
br0 [192.168.0.3/24 ]
br0.10 [192.168.10.3/24 ]
br0.20 [192.168.20.3/24 ]
br0.40 [192.168.40.3/24 ]
eth1 [192.168.30.10/24 ]

Nic detected:
# PCI device 0x8086:0x1557 (ixgbe)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="98:b7:85:1f:9e:27", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8125 (r8125)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="f0:2f:74:20:c4:3e", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

Lets review the dmesg / syslog:

Micro code loads:
IRQ/PCIE Devices are scaned:
Nics are loaded:
Oct 26 13:18:27 Tardis kernel: r8125: loading out-of-tree module taints kernel.
Oct 26 13:18:27 Tardis kernel: r8125 Ethernet controller driver 9.013.02-NAPI-RSS loaded
Oct 26 13:18:27 Tardis kernel: igb: Intel(R) Gigabit Ethernet Network Driver
Oct 26 13:18:27 Tardis kernel: igb: Copyright (c) 2007-2014 Intel Corporation.
Oct 26 13:18:27 Tardis kernel: ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver
Oct 26 13:18:27 Tardis kernel: ixgbe: Copyright (c) 1999-2016 Intel Corporation.
Oct 26 13:18:27 Tardis kernel: r8125: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625.
Oct 26 13:18:27 Tardis kernel: r8125  Copyright (C) 2024 Realtek NIC software team <[email protected]> 
Oct 26 13:18:27 Tardis kernel: This program comes with ABSOLUTELY NO WARRANTY; for details, please see <http://www.gnu.org/licenses/>. 
Oct 26 13:18:27 Tardis kernel: This is free software, and you are welcome to redistribute it under certain conditions; see <http://www.gnu.org/licenses/>. 
>-Go file loads modprobe bluetooth..
Oct 26 13:18:27 Tardis kernel: Bluetooth: Core ver 2.22
Oct 26 13:18:27 Tardis kernel: NET: Registered PF_BLUETOOTH protocol family
Oct 26 13:18:27 Tardis kernel: Bluetooth: HCI device and connection manager initialized
Oct 26 13:18:27 Tardis kernel: Bluetooth: HCI socket layer initialized
Oct 26 13:18:27 Tardis kernel: Bluetooth: L2CAP socket layer initialized
Oct 26 13:18:27 Tardis kernel: Bluetooth: SCO socket layer initialized

Oct 26 13:18:27 Tardis kernel: igb 0000:08:00.0: The NVM Checksum Is Not Valid
Oct 26 13:18:27 Tardis kernel: igb: probe of 0000:08:00.0 failed with error -5
*First reported errors from intel nic.

Given where it loads and boots at for first initalization. it is safe to ignore as this was when irq / pcie scan came in to first detect the device. The device loads sucessfule per syslog.

Intell nic loads...
Oct 26 13:18:27 Tardis kernel: ixgbe 0000:0c:00.0: Multiqueue Enabled: Rx Queue count = 16, Tx Queue count = 16 XDP Queue count = 0
Oct 26 13:18:27 Tardis kernel: ixgbe 0000:0c:00.0: 32.000 Gb/s available PCIe bandwidth (5.0 GT/s PCIe x8 link)
Oct 26 13:18:27 Tardis kernel: ixgbe 0000:0c:00.0: MAC: 2, PHY: 17, SFP+: 5, PBA No: FFFFFF-0FF
Oct 26 13:18:27 Tardis kernel: ixgbe 0000:0c:00.0: 98:b7:85:1f:9e:27
Oct 26 13:18:27 Tardis kernel: ixgbe 0000:0c:00.0: Intel(R) 10 Gigabit Network Connection

Nics are fully loaded with out issue:
Oct 26 13:18:27 Tardis kernel: ixgbe 0000:0c:00.0: complete
Oct 26 13:18:27 Tardis kernel: r8125 Ethernet controller driver 9.013.02-NAPI-RSS loaded
Oct 26 13:18:27 Tardis kernel: r8125: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625.
Oct 26 13:18:27 Tardis kernel: r8125 0000:07:00.0 eth123: renamed from eth0
Oct 26 13:18:27 Tardis kernel: r8125  Copyright (C) 2024 Realtek NIC software team <[email protected]> 
Oct 26 13:18:27 Tardis kernel: This program comes with ABSOLUTELY NO WARRANTY; for details, please see <http://www.gnu.org/licenses/>. 
Oct 26 13:18:27 Tardis kernel: This is free software, and you are welcome to redistribute it under certain conditions; see <http://www.gnu.org/licenses/>. 

Oct 26 13:18:27 Tardis kernel: ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver
Oct 26 13:18:27 Tardis kernel: ixgbe: Copyright (c) 1999-2016 Intel Corporation.
Oct 26 13:18:27 Tardis kernel: r8125 0000:07:00.0 eth1: renamed from eth123
Oct 26 13:18:27 Tardis kernel: ixgbe 0000:0c:00.0: Multiqueue Enabled: Rx Queue count = 16, Tx Queue count = 16 XDP Queue count = 0
Oct 26 13:18:27 Tardis kernel: ixgbe 0000:0c:00.0: 32.000 Gb/s available PCIe bandwidth (5.0 GT/s PCIe x8 link)
Oct 26 13:18:27 Tardis kernel: ixgbe 0000:0c:00.0: MAC: 2, PHY: 17, SFP+: 5, PBA No: FFFFFF-0FF
Oct 26 13:18:27 Tardis kernel: ixgbe 0000:0c:00.0: 98:b7:85:1f:9e:27
Oct 26 13:18:27 Tardis kernel: ixgbe 0000:0c:00.0: Intel(R) 10 Gigabit Network Connection

net rc to get and assign ip address... ping is avalbe at this time... Network setting begins..
....

atm you do have a improper syslinux...
 

BOOT_IMAGE=/bzimage pcie_acs_override=downstream,multifunction vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot

since you have vm settings enabled and have set 
Please confirm you have theses options and want them:


The click Main > Flash  and fix the data for your grub/syslinux boot
example:

then your cmd line will read coreclty...
 

BOOT_IMAGE=/bzimage initrd=/bzroot pcie_acs_override=downstream,multifunction vfio_iommu_type1.allow_unsafe_interrupts=1 

Here is a addon you can/should run for other recommend options. lets disable pcie power managment and let softrware control this not hardware...

 

kernel /bzimage
append initrd=/bzroot pci=noaer pcie_aspm=off pcie_acs_override=downstream,multifunction vfio_iommu_type1.allow_unsafe_interrupts=1

Outside of fixing the syslinux / grub boot:

Your nic appears to be loading fine. 

08:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
    Subsystem: ASUSTeK Computer Inc. I211 Gigabit Network Connection [1043:85f0]
    Kernel modules: igb
 

Settings for eth0:
    Supported ports: [ FIBRE ]
    Supported link modes:   10000baseT/Full
    Supported pause frame use: Symmetric
    Supports auto-negotiation: No
    Supported FEC modes: Not reported
    Advertised link modes:  10000baseT/Full
    Advertised pause frame use: Symmetric
    Advertised auto-negotiation: No
    Advertised FEC modes: Not reported
    Speed: 10000Mb/s
    Duplex: Full
    Auto-negotiation: off
    Port: FIBRE
    PHYAD: 0
    Transceiver: internal
    Supports Wake-on: d
    Wake-on: d
        Current message level: 0x00000007 (7)
                               drv probe link
    Link detected: yes

driver: ixgbe
version: 6.1.106-Unraid
firmware-version: 0x80000707, 1.2074.0
expansion-rom-version: 
bus-info: 0000:0c:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

ok  so   a few things i fixed the go file.. to change the eth0  to eth1  for wake on   since i swapped that  in the network

 

as for blacklist r8169   you mention dunno what you mean.. i did have the 2 realtek drivers installed  i remember having that done cuz of the 4 card nic  but  i just uninstalled both..  

as for the modprobe nt sure  the modprobe  i have in the go file  was for temperature issues and the bluetooth...  but it doesnt seemed to helped

i rem'ed them both at at the moment

 

my pcie ac over ride   i have it set to BOTH   not multifunction..  its been set to both like 4 yrs ago  so unless something changed since i did all that stuff i dunno

dont have multi function i  did it per a space invader video long ago

 

and which line  do you change on the flash  gui page

for 

kernel /bzimage append initrd=/bzroot pci=noaer pcie_aspm=off pcie_acs_override=downstream,multifunction vfio_iommu_type1.allow_unsafe_interrupts=1

 

is it the Unraid OS GUI Mode   or Unraid OS

 

and where is this syslinux?

and where is the command line for BOOT_IMAGE=/bzimage initrd=/bzroot pcie_acs_override=downstream,multifunction vfio_iommu_type1.allow_unsafe_interrupts=1

 

you mentioned  do i save  under vm manager  from Both to Multi-Function?

 

also i notice  when i reboot  server.. if  i even  stop the array and reboot...  it boots up but like the /boot/  is not there the gui is not there i cant run the diagnostics  as it cant write to the boot...  this is me ssh'ing in.. i have to reboot a 2nd time   just to get it back up..  for whatever glitch  is going on

 

and u had helped me in summer for drivers for the bluetooth  but nerd tools and drivers never helped that i also uninstalled the drivers for the bluetooth  it still shows up a warning in the logs

 

 

this improper  syslinux  does that also glitch the boot ups too then  why now it takes 2 reboots to boot up once?

Theres a known graphical bug when setting VM settings for pcie overides, and allow unsafe. as this adss syslinux grub kernel otpions to the boot menu. This was notated but as it didn't realy casue any problesm they left it alone, but the line really should be fixed.

Main > click flash  > this pullls the grub/sysliunx that unraid uses to boot... Depends on if you default boot into unraid gui/ safe mode/ etc ... this is what grubs pulls when read from the flash drive to boot into unraid. Sometimes we add or change things to our kernel line to make sure xyz feature is set or unset. In my case, my solid green:



Is Unriad OS and is my default boot option. as I have secondary kernel options I want to use for my hardware I have to add the syslinux option to the grub boot menu to persist across boots its added to the syslinux configuration in the unriad web ui.

In your case, since you have enabled the vm settings for a option for pcie overrides, and allow unsafe. It is recommended to fix the boxes. Optional to add pcie no aer which helps and turns off aer spam in logs. also as power setting on some pcie devices. I turn off aspm which is power management. but that may break your WOL.(I don't want my pcie device to go into power states or power off. As other things are done that break when they do... so I turn their ability to do so off... especially for g-card passthorugh. (I'm not a fan of WOL / snmp on my network I'm old and have used other technologies and will stick to what I know...) Different use case and feature for each others network and there use cases...

Its not improper but better to be read correctly then what it was currently being read as. 

As for Bluetooth, that requires other libs and would need to be booted in the GUI Mode with a desktop environment. If your using Bluetooth its better to not try at unraid level, and add it or its driver but instead pass the bluetooth device in to the docker / vm via pci ID...

lsusb

lspci

you should see your bluetooth device as its own IOMMU gorup.

as for passing it to a Docker example, Plex as a extra parmeter: 
--device=/dev/dvb/
in this case i pass a dvb tuner to my plex for use....

For bluetooth since your using it to grab sensory temp data. That would be a bit harder and I would recommend a Debian VM and pass the device to it that way to then do xyz with the data collected over bluetooth... < That should be a separate post.

In terms of your networking based on your last post. I think your good to go.

You fixed your WOL go call, and fixed any other issues with older modprobe calls from a previous device. The Syslinux was just a quick catch should be fixed but doesn't need to be touched...
 

Edited October 28, 20241 yr by bmartino1
spelling