I have a 10gig nic in my system which I had previously been using for the main link between it and my desktop but after a reboot unraid stopped picking up the 10gig nic anymore. It still shows up under windows if I boot into that but I don't see it listed in the network interfaces. 

It shows up in system devices as 

[1fc9:4027] 05:00.0 Ethernet controller: Tehuti Networks Ltd. TN9710P 10GBase-T/NBASE-T Ethernet Adapter

It is possible its a hardware failure since I have had these cards fail before in other systems but since it seems to be working under windows this is at least somewhat ruled out. Additionaly if I do plug the interface into my network switch despite the system not recognizing it I loose internet connectivity on my network so maybe theres some kind of strange networking stuff going on too. 

Any assistance getting this sorted is much appreciated!

tower-diagnostics-20210610-0817.zip

The driver is crashing.  Since it was working, I'd go with hardware failure.

Oof time to buy a new NIC I guess... 

1 hour ago, Squid said:

The driver is crashing.  Since it was working, I'd go with hardware failure.

 

Could you show where that is happening in the logs so I can know what to look for if it comes up again?

Jun  8 21:25:20 Tower kernel: WARNING: CPU: 9 PID: 1956 at net/ethtool/common.c:375 ethtool_check_ops+0xe/0x16
Jun  8 21:25:20 Tower kernel: Modules linked in: edac_mce_amd btusb btrtl btbcm kvm_amd btintel bluetooth kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd ecdh_generic ecc cryptd mxm_wmi wmi_bmof igb nvme ahci glue_helper i2c_piix4 input_leds tn40xx(O+) ccp nvme_core i2c_algo_bit libahci wmi i2c_core led_class rapl k10temp thermal button acpi_cpufreq
Jun  8 21:25:20 Tower kernel: CPU: 9 PID: 1956 Comm: udevd Tainted: G           O      5.10.28-Unraid #1
Jun  8 21:25:20 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS MASTER/X570 AORUS MASTER, BIOS F22 08/20/2020
Jun  8 21:25:20 Tower kernel: RIP: 0010:ethtool_check_ops+0xe/0x16
Jun  8 21:25:20 Tower kernel: Code: 42 c2 eb ec 41 89 45 00 48 89 ef e8 da db b7 ff 5b 44 89 e0 5d 41 5c 41 5d 41 5e c3 31 c0 48 83 7f 78 00 74 0c 83 3f 00 75 07 <0f> 0b b8 ea ff ff ff c3 48 8b 97 48 08 00 00 31 c0 49 89 f8 b9 0b
Jun  8 21:25:20 Tower kernel: RSP: 0018:ffffc900010e7a58 EFLAGS: 00010246
Jun  8 21:25:20 Tower kernel: RAX: 0000000000000000 RBX: 00000000002b09ab RCX: ffff888102bfd490
Jun  8 21:25:20 Tower kernel: RDX: ffffffff8210d220 RSI: ffffc90000921270 RDI: ffffffffa0152000
Jun  8 21:25:20 Tower kernel: RBP: ffff888105aad000 R08: 0000000000000c00 R09: 000000000000025d
Jun  8 21:25:20 Tower kernel: R10: 0000000000001101 R11: ffff888ffea62400 R12: 00000000fffffffc
Jun  8 21:25:20 Tower kernel: R13: ffffffff8210b440 R14: 0000000000000000 R15: ffff888105aad000
Jun  8 21:25:20 Tower kernel: FS:  00001522cec1bbc0(0000) GS:ffff888ffea40000(0000) knlGS:0000000000000000
Jun  8 21:25:20 Tower kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun  8 21:25:20 Tower kernel: CR2: 00000000006706a8 CR3: 0000000136a4a000 CR4: 0000000000350ee0
Jun  8 21:25:20 Tower kernel: Call Trace:
Jun  8 21:25:20 Tower kernel: register_netdevice+0x84/0x47a
Jun  8 21:25:20 Tower kernel: ? MV88X3310_mdio_reset+0x766/0x7be [tn40xx]
Jun  8 21:25:20 Tower kernel: register_netdev+0x1f/0x2e
Jun  8 21:25:20 Tower kernel: bdx_probe+0x895/0xaad [tn40xx]
Jun  8 21:25:20 Tower kernel: local_pci_probe+0x3c/0x7a
Jun  8 21:25:20 Tower kernel: pci_device_probe+0x140/0x19a
Jun  8 21:25:20 Tower kernel: ? sysfs_do_create_link_sd.isra.0+0x6b/0x98
Jun  8 21:25:20 Tower kernel: really_probe+0x157/0x341
Jun  8 21:25:20 Tower kernel: driver_probe_device+0x63/0x92
Jun  8 21:25:20 Tower kernel: device_driver_attach+0x37/0x50
Jun  8 21:25:20 Tower kernel: __driver_attach+0x95/0x9d
Jun  8 21:25:20 Tower kernel: ? device_driver_attach+0x50/0x50
Jun  8 21:25:20 Tower kernel: bus_for_each_dev+0x70/0xa6
Jun  8 21:25:20 Tower kernel: bus_add_driver+0xfe/0x1af
Jun  8 21:25:20 Tower kernel: driver_register+0x99/0xd2
Jun  8 21:25:20 Tower kernel: ? bdx_tx_timeout+0x2c/0x2c [tn40xx]
Jun  8 21:25:20 Tower kernel: do_one_initcall+0x71/0x162
Jun  8 21:25:20 Tower kernel: ? do_init_module+0x19/0x1eb
Jun  8 21:25:20 Tower kernel: ? kmem_cache_alloc+0x108/0x130
Jun  8 21:25:20 Tower kernel: do_init_module+0x51/0x1eb
Jun  8 21:25:20 Tower kernel: load_module+0x1b18/0x20cf
Jun  8 21:25:20 Tower kernel: ? map_kernel_range_noflush+0xdf/0x255
Jun  8 21:25:20 Tower kernel: ? __do_sys_init_module+0xc4/0x105
Jun  8 21:25:20 Tower kernel: ? _cond_resched+0x1b/0x1e
Jun  8 21:25:20 Tower kernel: __do_sys_init_module+0xc4/0x105
Jun  8 21:25:20 Tower kernel: do_syscall_64+0x5d/0x6a
Jun  8 21:25:20 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jun  8 21:25:20 Tower kernel: RIP: 0033:0x1522cf27d09a
Jun  8 21:25:20 Tower kernel: Code: 48 8b 0d f9 7d 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c6 7d 0c 00 f7 d8 64 89 01 48
Jun  8 21:25:20 Tower kernel: RSP: 002b:00007ffc60311618 EFLAGS: 00000206 ORIG_RAX: 00000000000000af
Jun  8 21:25:20 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000663b40 RCX: 00001522cf27d09a
Jun  8 21:25:20 Tower kernel: RDX: 00001522cf35d97d RSI: 00000000000aed58 RDI: 00000000006d3910
Jun  8 21:25:20 Tower kernel: RBP: 00000000006d3910 R08: 000000000064701a R09: 0000000000000006
Jun  8 21:25:20 Tower kernel: R10: 0000000000647010 R11: 0000000000000206 R12: 00001522cf35d97d
Jun  8 21:25:20 Tower kernel: R13: 00007ffc60311b80 R14: 00000000006783a0 R15: 0000000000663b40
Jun  8 21:25:20 Tower kernel: ---[ end trace 09b2fc8fdb595ffd ]---
Jun  8 21:25:20 Tower kernel: tn40xx: register_netdev failed

 

Did it fail out of the blue or just after update to 6.9 ?

 

One driver from Tehuti is not integrated Tehuti Networks tn40xx (does not build)

Don't know if this is the same driver.

 

https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.9.0#Linux_Kernel

Yep that's almost certainly it ChatNoir, looks like Tehuti Networks went under mid 2020 so we can't exactly expect any updates from them. 
I did find this... but I assume I'd need the unraid team to implement it. https://github.com/acooks/tn40xx-driver