Slik

You fixed this by deleteing your network config file on the flash drive?

Nov 28 14:16:51 TheFang kernel: ------------[ cut here ]------------ Nov 28 14:16:51 TheFang kernel: WARNING: CPU: 28 PID: 24859 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Nov 28 14:16:51 TheFang kernel: Modules linked in: xt_nat xt_tcpudp veth nvidia_uvm(PO) macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs dm_crypt dm_mod md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ipmi_devintf hwmon_vid wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc e1000e igb intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp nvidia_drm(PO) nvidia_modeset(PO) kvm_intel kvm nvidia(PO) crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd cryptd mgag200 video drm_shmem_helper drm_kms_helper ipmi_ssif rapl intel_cstate drm isci nvme mpt3sas Nov 28 14:16:51 TheFang kernel: i2c_i801 mei_me i2c_smbus i2c_algo_bit backlight ahci syscopyarea input_leds sysfillrect sysimgblt intel_uncore libsas libahci mei nvme_core joydev led_class fb_sys_fops i2c_core raid_class scsi_transport_sas acpi_ipmi wmi ipmi_si button unix [last unloaded: e1000e] Nov 28 14:16:51 TheFang kernel: CPU: 28 PID: 24859 Comm: kworker/u66:12 Tainted: P O 6.1.49-Unraid #1 Nov 28 14:16:51 TheFang kernel: Hardware name: Supermicro X9DR7/E-(J)LN4F/X9DR7/E-(J)LN4F, BIOS 3.2 05/22/2015 Nov 28 14:16:51 TheFang kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan] Nov 28 14:16:51 TheFang kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Nov 28 14:16:51 TheFang kernel: Code: 44 24 10 e8 e2 e1 ff ff 8b 7c 24 04 89 ea 89 c6 89 04 24 e8 7e e6 ff ff 84 c0 75 a2 48 89 df e8 9b e2 ff ff 85 c0 89 c5 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 18 dd ff ff e8 93 e3 ff ff e9 72 01 Nov 28 14:16:51 TheFang kernel: RSP: 0018:ffffc90006a74d98 EFLAGS: 00010202 Nov 28 14:16:51 TheFang kernel: RAX: 0000000000000001 RBX: ffff8890cc1caf00 RCX: fcef0fb0d649d41c Nov 28 14:16:51 TheFang kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8890cc1caf00 Nov 28 14:16:51 TheFang kernel: RBP: 0000000000000001 R08: d7eb5924399a04f2 R09: 64236f1799c3fd26 Nov 28 14:16:51 TheFang kernel: R10: 5ea7889a28d29ef2 R11: ffffc90006a74d60 R12: ffffffff82a11d00 Nov 28 14:16:51 TheFang kernel: R13: 000000000000885c R14: ffff88908a2bfc00 R15: 0000000000000000 Nov 28 14:16:51 TheFang kernel: FS: 0000000000000000(0000) GS:ffff88a03fd00000(0000) knlGS:0000000000000000 Nov 28 14:16:51 TheFang kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 28 14:16:51 TheFang kernel: CR2: 000015284d3ad000 CR3: 000000000220a001 CR4: 00000000001706e0 Nov 28 14:16:51 TheFang kernel: Call Trace: Nov 28 14:16:51 TheFang kernel: <IRQ> Nov 28 14:16:51 TheFang kernel: ? __warn+0xab/0x122 Nov 28 14:16:51 TheFang kernel: ? report_bug+0x109/0x17e Nov 28 14:16:51 TheFang kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Nov 28 14:16:51 TheFang kernel: ? handle_bug+0x41/0x6f Nov 28 14:16:51 TheFang kernel: ? exc_invalid_op+0x13/0x60 Nov 28 14:16:51 TheFang kernel: ? asm_exc_invalid_op+0x16/0x20 Nov 28 14:16:51 TheFang kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Nov 28 14:16:51 TheFang kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack] Nov 28 14:16:51 TheFang kernel: ? nf_nat_inet_fn+0xc0/0x1a8 [nf_nat] Nov 28 14:16:51 TheFang kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Nov 28 14:16:51 TheFang kernel: nf_hook_slow+0x3d/0x96 Nov 28 14:16:51 TheFang kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Nov 28 14:16:51 TheFang kernel: NF_HOOK.constprop.0+0x79/0xd9 Nov 28 14:16:51 TheFang kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Nov 28 14:16:51 TheFang kernel: __netif_receive_skb_one_core+0x77/0x9c Nov 28 14:16:51 TheFang kernel: process_backlog+0x8c/0x116 Nov 28 14:16:51 TheFang kernel: __napi_poll.constprop.0+0x2b/0x124 Nov 28 14:16:51 TheFang kernel: net_rx_action+0x159/0x24f Nov 28 14:16:51 TheFang kernel: __do_softirq+0x129/0x288 Nov 28 14:16:51 TheFang kernel: do_softirq+0x7f/0xab Nov 28 14:16:51 TheFang kernel: </IRQ> Nov 28 14:16:51 TheFang kernel: <TASK> Nov 28 14:16:51 TheFang kernel: __local_bh_enable_ip+0x4c/0x6b Nov 28 14:16:51 TheFang kernel: netif_rx+0x52/0x5a Nov 28 14:16:51 TheFang kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Nov 28 14:16:51 TheFang kernel: ? _raw_spin_unlock+0x14/0x29 Nov 28 14:16:51 TheFang kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Nov 28 14:16:51 TheFang kernel: process_one_work+0x1ab/0x295 Nov 28 14:16:51 TheFang kernel: worker_thread+0x18b/0x244 Nov 28 14:16:51 TheFang kernel: ? rescuer_thread+0x281/0x281 Nov 28 14:16:51 TheFang kernel: kthread+0xe7/0xef Nov 28 14:16:51 TheFang kernel: ? kthread_complete_and_exit+0x1b/0x1b Nov 28 14:16:51 TheFang kernel: ret_from_fork+0x22/0x30 Nov 28 14:16:51 TheFang kernel: </TASK> Nov 28 14:16:51 TheFang kernel: ---[ end trace 0000000000000000 ]---Nov 28 14:16:51 TheFang kernel: ------------[ cut here ]------------ Having a similar issue... switching to IPVlan does not fix this... Ever since the update, I have not be able to get my reverse proxy (SWAG) to work. Everything was running smooth for years until approximately two weeks ago.

Issue Fixed - How to fix: Stop you VM, go to the drop down and update the network driver to the new virto-net driver. I was unable to manually change it in the XML, as it would fail to connect to the internet. I had to update it from the drop down box for it to work. Thanks,

Current Version: 6.9.0 Beta 35 Setup: Dual 2667 V2's 256Gb Ram 30TB VM: 4 Cores + 12 Gb RAM + GTX 1080 TI + 120Gb VDisk on NVME (New Pool / single hardware xfs pool). Currently set to qemu / raw. Moved Domains, Iso and Libvert on the NVME (Libvert direct / Domains & Iso via Shares). Fresh install of Windows 10 Pro and keep getting the follow speeds. I know it will not be as good as direct hardware due to it being a vdisk, but the extremely slow speeds is what bothers me. I have tired changing cache=writeback to none, but still get the slower speeds. I found a thread from 2018 referencing upcoming changes to fix it, but couldnt find any direct fixes during my googling. Any ways around this currently? Or is this even a problem? Thanks a bunch!

I’m pretty new to Linux, but dam Unraid makes it’s easy! I didn’t even know what Linux was two months ago! I would like to see the second array option. Being able to be security cameras on another array with parity, even is small, would be amazing.

I have recently attempted to get HW transcoding working but have hit an error that I can not figure out. I am currently running Unraid RC5, have downloaded the plug in, typed in the extra parameters, GPU GUID and GPU Capabilities. I have a working Nvidia-SMI screen but keep getting the error below when trying to transcode over hardware. I have tried googling with no luck. I am currently using the LinuxSevers IO Plex App and do have Plex Pass (I watch on my phone all the time with CPU transcode). This is tested on multiple 1080p, 264, .mkv files. Thank you,

I am pretty new to unraid, had it up and running for a few weeks now on my current setup. I noticed I am starting to get this error in my system log: The only reference I can find for this, is a single post from 2014 talking about this error and it possibly being the network adapter on the motherboard (Here). I have ordered a new Intel NIC to see if this would solve it, just curious if anyone has any ideas about this error? Current Setup: Mobo: EVGA E672 Micro CPU: 2600K @ 4.5 Ghz Ram: Mushkin unRaid Build: 6.7.2 (Have never had any other build) Thank you,