sonic6

i think hostaccess isn't possible with this "solution",... so in my eyes this isn't a real "solution" for the whole "macvlan issue". maybe it also should't be named as that.

Don't get me wrong, but i don't really get what you mean. This isn't the first one of this errors which was reported? This isn't the first error in my syslogs? (I know, there were 6 one befor, the posted one was just an example) Do i have to be worried about, and/or is the device broken, or misconfigured?

i missed the Diagnstic.

With a random look in my Syslog i found the following from time to time when i got heavy load on my nvme cache drive: May 15 00:52:59 Unraid-1 kernel: nvme0n1: I/O Cmd(0x2) @ LBA 551285192, 512 blocks, I/O Error (sct 0x2 / sc 0x81) MORE May 15 00:52:59 Unraid-1 kernel: critical medium error, dev nvme0n1, sector 551285192 op 0x0:(READ) flags 0x84700 phys_seg 64 prio class 0 May 15 00:52:59 Unraid-1 kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 914 off 81920 (dev /dev/nvme0n1p1 sector 551282632) nvme: https://jp.transcend-info.com/products/images/modelpic/991/Transcend-PCIeSSD220S.pdf Diagnostic is attaced. i use two of this in a btrfs-raid1 as a cache drive for appdata, docker and VMs. i got the same message when i did a scrub. both nvme's are connected to the onboard M.2 slot. (more details in my signature) should i be worried about that? the drive is just 2 month old with a runtime of 977 hours. should i do a RMA? i didn't saw the same for nvme1n1 (second drive from btrfs-raid1). thank you, for helping me unraid-1-diagnostics-20230516-1345.zip

i can confirm this, after downgrade my server runs for 3 days without any traces.

my server crashed 4 times in the last two day, so i had to go back back to 6.11.5. if there is something more to try/test, let me know.

Looks like it will stay with this single trace for a long time. But, when you look here there was first a single trace when the server starts: May 2 06:56:23 Unraid-1 kernel: ------------[ cut here ]------------ May 2 06:56:23 Unraid-1 kernel: WARNING: CPU: 5 PID: 30624 at net/netfilter/nf_conntrack_core.c:1211 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] May 2 06:56:23 Unraid-1 kernel: Modules linked in: cmac cifs asn1_decoder cifs_arc4 cifs_md4 dns_resolver tls nft_chain_nat xt_owner nft_compat nf_tables macvlan xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_nat xt_tcpudp ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat xt_addrtype br_netfilter veth xfs xt_MASQUERADE ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod tcp_diag inet_diag af_packet kvmgt mdev i915 iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nct6775 nct6775_core hwmon_vid efivarfs 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 8021q garp mrp bridge stp llc x86_pkg_temp_thermal intel_powerclamp May 2 06:56:23 Unraid-1 kernel: coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd cryptd mei_hdcp mei_pxp rapl intel_cstate i2c_i801 nvme mei_me wmi_bmof i2c_smbus mpt3sas e1000e intel_uncore nvme_core i2c_core cp210x mei intel_pch_thermal raid_class usbserial joydev scsi_transport_sas tpm_crb video tpm_tis tpm_tis_core wmi tpm backlight intel_pmc_core acpi_pad acpi_tad button unix May 2 06:56:23 Unraid-1 kernel: CPU: 5 PID: 30624 Comm: core Tainted: G U 6.1.27-Unraid #1 May 2 06:56:23 Unraid-1 kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H470M-ITX/ac, BIOS L1.22 12/07/2020 May 2 06:56:23 Unraid-1 kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] May 2 06:56:23 Unraid-1 kernel: Code: 44 24 10 e8 f4 e1 ff ff 8b 7c 24 04 89 ea 89 c6 89 04 24 e8 76 e6 ff ff 84 c0 75 a2 48 89 df e8 ad e2 ff ff 85 c0 89 c5 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 2a dd ff ff e8 8b e3 ff ff e9 72 01 May 2 06:56:23 Unraid-1 kernel: RSP: 0000:ffffc90006117808 EFLAGS: 00010202 May 2 06:56:23 Unraid-1 kernel: RAX: 0000000000000001 RBX: ffff88836f618500 RCX: 75b9cb1795d9325b May 2 06:56:23 Unraid-1 kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88836f618500 May 2 06:56:23 Unraid-1 kernel: RBP: 0000000000000001 R08: 892664b1afc23242 R09: 4dfe4a4532a4deda May 2 06:56:23 Unraid-1 kernel: R10: a2013e3c290bb2d9 R11: ffffc900061177d0 R12: ffffffff82a0e440 May 2 06:56:23 Unraid-1 kernel: R13: 0000000000003edb R14: ffff88836f604c00 R15: 0000000000000000 May 2 06:56:23 Unraid-1 kernel: FS: 0000153394d3e3c0(0000) GS:ffff88883f740000(0000) knlGS:0000000000000000 May 2 06:56:23 Unraid-1 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 2 06:56:23 Unraid-1 kernel: CR2: 0000557163404014 CR3: 0000000350120004 CR4: 00000000007706e0 May 2 06:56:23 Unraid-1 kernel: PKRU: 55555554 May 2 06:56:23 Unraid-1 kernel: Call Trace: May 2 06:56:23 Unraid-1 kernel: <TASK> May 2 06:56:23 Unraid-1 kernel: ? nf_nat_inet_fn+0x60/0x1a8 [nf_nat] May 2 06:56:23 Unraid-1 kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] May 2 06:56:23 Unraid-1 kernel: nf_hook_slow+0x3a/0x96 May 2 06:56:23 Unraid-1 kernel: ? ip_protocol_deliver_rcu+0x164/0x164 May 2 06:56:23 Unraid-1 kernel: NF_HOOK.constprop.0+0x79/0xd9 May 2 06:56:23 Unraid-1 kernel: ? ip_protocol_deliver_rcu+0x164/0x164 May 2 06:56:23 Unraid-1 kernel: ip_sabotage_in+0x4f/0x60 [br_netfilter] May 2 06:56:23 Unraid-1 kernel: nf_hook_slow+0x3a/0x96 May 2 06:56:23 Unraid-1 kernel: ? ip_rcv_finish_core.constprop.0+0x3e8/0x3e8 May 2 06:56:23 Unraid-1 kernel: NF_HOOK.constprop.0+0x79/0xd9 May 2 06:56:23 Unraid-1 kernel: ? ip_rcv_finish_core.constprop.0+0x3e8/0x3e8 May 2 06:56:23 Unraid-1 kernel: __netif_receive_skb_one_core+0x77/0x9c May 2 06:56:23 Unraid-1 kernel: netif_receive_skb+0xbf/0x127 May 2 06:56:23 Unraid-1 kernel: br_handle_frame_finish+0x438/0x472 [bridge] May 2 06:56:23 Unraid-1 kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] May 2 06:56:23 Unraid-1 kernel: br_nf_hook_thresh+0xe2/0x109 [br_netfilter] May 2 06:56:23 Unraid-1 kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] May 2 06:56:23 Unraid-1 kernel: br_nf_pre_routing_finish+0x2c1/0x2ec [br_netfilter] May 2 06:56:23 Unraid-1 kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] May 2 06:56:23 Unraid-1 kernel: ? NF_HOOK.isra.0+0xe4/0x140 [br_netfilter] May 2 06:56:23 Unraid-1 kernel: ? br_nf_hook_thresh+0x109/0x109 [br_netfilter] May 2 06:56:23 Unraid-1 kernel: br_nf_pre_routing+0x236/0x24a [br_netfilter] May 2 06:56:23 Unraid-1 kernel: ? br_nf_hook_thresh+0x109/0x109 [br_netfilter] May 2 06:56:23 Unraid-1 kernel: br_handle_frame+0x277/0x2e0 [bridge] May 2 06:56:23 Unraid-1 kernel: ? kernel_restart_prepare+0x2a/0x32 May 2 06:56:23 Unraid-1 kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] May 2 06:56:23 Unraid-1 kernel: __netif_receive_skb_core.constprop.0+0x4fa/0x6e9 May 2 06:56:23 Unraid-1 kernel: ? place_entity+0x6e/0xae May 2 06:56:23 Unraid-1 kernel: ? paravirt_write_msr+0xb/0x11 May 2 06:56:23 Unraid-1 kernel: ? check_preempt_wakeup+0x174/0x1f2 May 2 06:56:23 Unraid-1 kernel: __netif_receive_skb_list_core+0x8a/0x11e May 2 06:56:23 Unraid-1 kernel: netif_receive_skb_list_internal+0x1d2/0x20b May 2 06:56:23 Unraid-1 kernel: gro_normal_list+0x1d/0x3f May 2 06:56:23 Unraid-1 kernel: napi_complete_done+0x7b/0x11a May 2 06:56:23 Unraid-1 kernel: e1000e_poll+0x9e/0x23e [e1000e] May 2 06:56:23 Unraid-1 kernel: __napi_poll.constprop.0+0x28/0x124 May 2 06:56:23 Unraid-1 kernel: net_rx_action+0x159/0x24f May 2 06:56:23 Unraid-1 kernel: ? e1000_intr_msi+0x118/0x124 [e1000e] May 2 06:56:23 Unraid-1 kernel: __do_softirq+0x126/0x288 May 2 06:56:23 Unraid-1 kernel: __irq_exit_rcu+0x5e/0xb8 May 2 06:56:23 Unraid-1 kernel: common_interrupt+0x3b/0xc1 May 2 06:56:23 Unraid-1 kernel: asm_common_interrupt+0x22/0x40 May 2 06:56:23 Unraid-1 kernel: RIP: 0033:0x1533844d49f6 May 2 06:56:23 Unraid-1 kernel: Code: 1f 44 00 00 48 8b 54 24 18 48 8b fa e8 03 67 ff ff 90 49 3b c6 0f 84 d7 fe ff ff 48 8b 78 18 49 8d 0c 3e 48 3b 4c 24 20 74 9a <48> 85 ff 0f 84 19 00 00 00 48 8b 7c 24 20 48 8b f1 48 8b 44 24 30 May 2 06:56:23 Unraid-1 kernel: RSP: 002b:00007ffc1826be40 EFLAGS: 00000212 May 2 06:56:23 Unraid-1 kernel: RAX: 000015337f823618 RBX: 000015337ed4b838 RCX: 000015337e555810 May 2 06:56:23 Unraid-1 kernel: RDX: 0000000000000400 RSI: 0000000003b23618 RDI: 0000000002855810 May 2 06:56:23 Unraid-1 kernel: RBP: 000015337f823618 R08: 00000000145c7530 R09: 000015336bcdf7b0 May 2 06:56:23 Unraid-1 kernel: R10: 000015336a28cc10 R11: 000015336bcd0ad8 R12: 000015336bcdf7b0 May 2 06:56:23 Unraid-1 kernel: R13: 000015337fc7f6a8 R14: 000015337bd00000 R15: 0000153394c6d300 May 2 06:56:23 Unraid-1 kernel: </TASK> May 2 06:56:23 Unraid-1 kernel: ---[ end trace 0000000000000000 ]--- May 2 06:56:25 Unraid-1 kernel: process '4a104bf4d9746c31192addd040baa60c09299ac6cc5fba22a56231040e70ff26/usr/bin/par2' started with executable stack May 2 06:59:56 Unraid-1 ntpd[1331]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized and a second and third one in the logs from syslog server: 2023-05-05T22:13:09+02:00 Unraid-1 kernel: ------------[ cut here ]------------ 2023-05-05T22:13:09+02:00 Unraid-1 kernel: refcount_t: addition on 0; use-after-free. 2023-05-05T22:13:09+02:00 Unraid-1 kernel: WARNING: CPU: 9 PID: 152 at lib/refcount.c:25 refcount_warn_saturate+0x90/0x100 2023-05-05T22:13:09+02:00 Unraid-1 kernel: Modules linked in: cmac cifs asn1_decoder cifs_arc4 cifs_md4 dns_resolver tls nft_chain_nat xt_owner nft_compat nf_tables xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_nat xt_tcpudp ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat xt_addrtype br_netfilter veth xfs xt_MASQUERADE ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod tcp_diag inet_diag af_packet kvmgt mdev i915 iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nct6775 nct6775_core hwmon_vid efivarfs 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 8021q garp mrp bridge stp llc x86_pkg_temp_thermal intel_powerclamp 2023-05-05T22:13:09+02:00 Unraid-1 kernel: coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd cryptd rapl intel_cstate mei_hdcp mei_pxp wmi_bmof i2c_i801 nvme mpt3sas intel_uncore e1000e mei_me i2c_smbus nvme_core cp210x intel_pch_thermal mei i2c_core joydev usbserial raid_class scsi_transport_sas tpm_crb video tpm_tis tpm_tis_core wmi backlight tpm intel_pmc_core acpi_pad acpi_tad button unix 2023-05-05T22:13:09+02:00 Unraid-1 kernel: CPU: 9 PID: 152 Comm: kswapd0 Tainted: G U W 6.1.27-Unraid #1 2023-05-05T22:13:09+02:00 Unraid-1 kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H470M-ITX/ac, BIOS L1.22 12/07/2020 2023-05-05T22:13:09+02:00 Unraid-1 kernel: RIP: 0010:refcount_warn_saturate+0x90/0x100 2023-05-05T22:13:09+02:00 Unraid-1 kernel: Code: 00 01 e8 85 94 c3 ff 0f 0b c3 cc cc cc cc 80 3d 6e bc f5 00 00 75 7e 48 c7 c7 bb 8f 0b 82 c6 05 5e bc f5 00 01 e8 62 94 c3 ff <0f> 0b c3 cc cc cc cc 80 3d 4a bc f5 00 00 75 5b 48 c7 c7 e7 8f 0b 2023-05-05T22:13:09+02:00 Unraid-1 kernel: RSP: 0018:ffffc900005e79d8 EFLAGS: 00010282 2023-05-05T22:13:09+02:00 Unraid-1 kernel: RAX: 0000000000000000 RBX: ffff888107fe0b88 RCX: 0000000000000027 2023-05-05T22:13:09+02:00 Unraid-1 kernel: RDX: 0000000000000003 RSI: ffffffff8208f7cd RDI: 00000000ffffffff 2023-05-05T22:13:09+02:00 Unraid-1 kernel: RBP: ffff8881630b1de0 R08: 0000000000000000 R09: ffffffff82245e30 2023-05-05T22:13:09+02:00 Unraid-1 kernel: R10: 00007fffffffffff R11: 0000000000000000 R12: 0000000000000000 2023-05-05T22:13:09+02:00 Unraid-1 kernel: R13: ffff8881de978d98 R14: 0000000000000000 R15: 0000000000000000 2023-05-05T22:13:09+02:00 Unraid-1 kernel: FS: 0000000000000000(0000) GS:ffff88883f840000(0000) knlGS:0000000000000000 2023-05-05T22:13:09+02:00 Unraid-1 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2023-05-05T22:13:09+02:00 Unraid-1 kernel: CR2: 00001480936e2000 CR3: 00000001dc554002 CR4: 00000000007706e0 2023-05-05T22:13:09+02:00 Unraid-1 kernel: PKRU: 55555554 2023-05-05T22:13:09+02:00 Unraid-1 kernel: Call Trace: 2023-05-05T22:13:09+02:00 Unraid-1 kernel: <TASK> 2023-05-05T22:13:09+02:00 Unraid-1 kernel: __set_extent_bit+0x27f/0x499 2023-05-05T22:13:09+02:00 Unraid-1 kernel: ? btrfs_drop_extent_map_range+0x78/0x453 2023-05-05T22:13:09+02:00 Unraid-1 kernel: lock_extent+0x46/0xcf 2023-05-05T22:13:09+02:00 Unraid-1 kernel: btrfs_evict_inode+0x114/0x340 2023-05-05T22:13:09+02:00 Unraid-1 kernel: ? autoremove_wake_function+0x33/0x33 2023-05-05T22:13:09+02:00 Unraid-1 kernel: evict+0xb9/0x150 2023-05-05T22:13:09+02:00 Unraid-1 kernel: dispose_list+0x35/0x42 2023-05-05T22:13:09+02:00 Unraid-1 kernel: prune_icache_sb+0x51/0x73 2023-05-05T22:13:09+02:00 Unraid-1 kernel: super_cache_scan+0x123/0x17c 2023-05-05T22:13:09+02:00 Unraid-1 kernel: do_shrink_slab+0x188/0x2a1 2023-05-05T22:13:09+02:00 Unraid-1 kernel: shrink_slab+0x1f9/0x267 2023-05-05T22:13:09+02:00 Unraid-1 kernel: shrink_node+0x318/0x549 2023-05-05T22:13:09+02:00 Unraid-1 kernel: balance_pgdat+0x4e9/0x6a2 2023-05-05T22:13:09+02:00 Unraid-1 kernel: ? newidle_balance+0x289/0x30a 2023-05-05T22:13:09+02:00 Unraid-1 kernel: ? _raw_spin_unlock+0x14/0x29 2023-05-05T22:13:09+02:00 Unraid-1 kernel: ? raw_spin_rq_unlock_irq+0x5/0x10 2023-05-05T22:13:09+02:00 Unraid-1 kernel: ? finish_task_switch.isra.0+0x140/0x218 2023-05-05T22:13:09+02:00 Unraid-1 kernel: kswapd+0x2f0/0x333 2023-05-05T22:13:09+02:00 Unraid-1 kernel: ? _raw_spin_rq_lock_irqsave+0x20/0x20 2023-05-05T22:13:09+02:00 Unraid-1 kernel: ? balance_pgdat+0x6a2/0x6a2 2023-05-05T22:13:09+02:00 Unraid-1 kernel: kthread+0xe4/0xef 2023-05-05T22:13:09+02:00 Unraid-1 kernel: ? kthread_complete_and_exit+0x1b/0x1b 2023-05-05T22:13:09+02:00 Unraid-1 kernel: ret_from_fork+0x1f/0x30 2023-05-05T22:13:09+02:00 Unraid-1 kernel: </TASK> 2023-05-05T22:13:09+02:00 Unraid-1 kernel: ---[ end trace 0000000000000000 ]--- 2023-05-05T22:13:09+02:00 Unraid-1 kernel: ------------[ cut here ]------------ 2023-05-05T22:13:09+02:00 Unraid-1 kernel: refcount_t: underflow; use-after-free. 2023-05-05T22:13:09+02:00 Unraid-1 kernel: WARNING: CPU: 9 PID: 152 at lib/refcount.c:28 refcount_warn_saturate+0xb3/0x100 2023-05-05T22:13:09+02:00 Unraid-1 kernel: Modules linked in: cmac cifs asn1_decoder cifs_arc4 cifs_md4 dns_resolver tls nft_chain_nat xt_owner nft_compat nf_tables xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_nat xt_tcpudp ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat xt_addrtype br_netfilter veth xfs xt_MASQUERADE ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod tcp_diag inet_diag af_packet kvmgt mdev i915 iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nct6775 nct6775_core hwmon_vid efivarfs 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 8021q garp mrp bridge stp llc x86_pkg_temp_thermal intel_powerclamp 2023-05-05T22:13:09+02:00 Unraid-1 kernel: coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd cryptd rapl intel_cstate mei_hdcp mei_pxp wmi_bmof i2c_i801 nvme mpt3sas intel_uncore e1000e mei_me i2c_smbus nvme_core cp210x intel_pch_thermal mei i2c_core joydev usbserial raid_class scsi_transport_sas tpm_crb video tpm_tis tpm_tis_core wmi backlight tpm intel_pmc_core acpi_pad acpi_tad button unix 2023-05-05T22:13:09+02:00 Unraid-1 kernel: CPU: 9 PID: 152 Comm: kswapd0 Tainted: G U W 6.1.27-Unraid #1 2023-05-05T22:13:09+02:00 Unraid-1 kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H470M-ITX/ac, BIOS L1.22 12/07/2020 2023-05-05T22:13:09+02:00 Unraid-1 kernel: RIP: 0010:refcount_warn_saturate+0xb3/0x100 2023-05-05T22:13:09+02:00 Unraid-1 kernel: Code: 00 01 e8 62 94 c3 ff 0f 0b c3 cc cc cc cc 80 3d 4a bc f5 00 00 75 5b 48 c7 c7 e7 8f 0b 82 c6 05 3a bc f5 00 01 e8 3f 94 c3 ff <0f> 0b c3 cc cc cc cc 80 3d 26 bc f5 00 00 75 38 48 c7 c7 0f 90 0b 2023-05-05T22:13:09+02:00 Unraid-1 kernel: RSP: 0018:ffffc900005e7a38 EFLAGS: 00010282 2023-05-05T22:13:09+02:00 Unraid-1 kernel: RAX: 0000000000000000 RBX: ffff888107fe0b88 RCX: 0000000000000027 2023-05-05T22:13:09+02:00 Unraid-1 kernel: RDX: 0000000000000003 RSI: ffffffff8208f7cd RDI: 00000000ffffffff 2023-05-05T22:13:09+02:00 Unraid-1 kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffff82245e30 2023-05-05T22:13:09+02:00 Unraid-1 kernel: R10: 00007fffffffffff R11: 0000000000000000 R12: 00000000ffff7fff 2023-05-05T22:13:09+02:00 Unraid-1 kernel: R13: ffff8881630b1de0 R14: 0000000000000000 R15: ffffc900005e7ad0 2023-05-05T22:13:09+02:00 Unraid-1 kernel: FS: 0000000000000000(0000) GS:ffff88883f840000(0000) knlGS:0000000000000000 2023-05-05T22:13:09+02:00 Unraid-1 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2023-05-05T22:22:46+02:00 Unraid-1 kernel: mdcmd (93): set md_write_method 0 2023-05-05T22:22:46+02:00 Unraid-1 kernel: 2023-05-05T22:42:46+02:00 Unraid-1 kernel: mdcmd (94): set md_write_method 1 2023-05-05T22:42:46+02:00 Unraid-1 kernel: 2023-05-05T23:52:46+02:00 Unraid-1 kernel: mdcmd (95): set md_write_method 0 2023-05-05T23:52:46+02:00 Unraid-1 kernel: 2023-05-06T00:02:46+02:00 Unraid-1 kernel: mdcmd (96): set md_write_method 1 2023-05-06T00:02:46+02:00 Unraid-1 kernel: two hours before the server crashed at 2023-05-06T00:02:46+02:00 this happend when i was sleeping. I checked my schedules, crons, userscript, and container, but i didn't found anything which kicked in on 00:00 AM.

No, Server is still working, but will crash in a few days, like before.

Here we are again: May 6 07:25:01 Unraid-1 kernel: ------------[ cut here ]------------ May 6 07:25:01 Unraid-1 kernel: WARNING: CPU: 7 PID: 93 at net/netfilter/nf_conntrack_core.c:1211 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] May 6 07:25:01 Unraid-1 kernel: Modules linked in: cmac cifs asn1_decoder cifs_arc4 cifs_md4 dns_resolver tls nft_chain_nat xt_owner nft_compat nf_tables xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat xt_addrtype br_netfilter veth xfs xt_MASQUERADE ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod tcp_diag inet_diag af_packet kvmgt mdev i915 iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nct6775 nct6775_core hwmon_vid efivarfs 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 8021q garp mrp bridge stp llc x86_pkg_temp_thermal intel_powerclamp May 6 07:25:01 Unraid-1 kernel: coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd mei_hdcp mei_pxp i2c_i801 cryptd rapl intel_cstate nvme i2c_smbus wmi_bmof mei_me mpt3sas cp210x intel_uncore e1000e nvme_core i2c_core intel_pch_thermal mei joydev usbserial raid_class scsi_transport_sas tpm_crb video tpm_tis tpm_tis_core wmi tpm backlight intel_pmc_core acpi_pad acpi_tad button unix May 6 07:25:01 Unraid-1 kernel: CPU: 7 PID: 93 Comm: kworker/u24:3 Tainted: G U 6.1.27-Unraid #1 May 6 07:25:01 Unraid-1 kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H470M-ITX/ac, BIOS L1.22 12/07/2020 May 6 07:25:01 Unraid-1 kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan] May 6 07:25:01 Unraid-1 kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] May 6 07:25:01 Unraid-1 kernel: Code: 44 24 10 e8 f4 e1 ff ff 8b 7c 24 04 89 ea 89 c6 89 04 24 e8 76 e6 ff ff 84 c0 75 a2 48 89 df e8 ad e2 ff ff 85 c0 89 c5 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 2a dd ff ff e8 8b e3 ff ff e9 72 01 May 6 07:25:01 Unraid-1 kernel: RSP: 0018:ffffc900002a0d98 EFLAGS: 00010202 May 6 07:25:01 Unraid-1 kernel: RAX: 0000000000000001 RBX: ffff8881cb970700 RCX: da30c29a3d7bac1d May 6 07:25:01 Unraid-1 kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881cb970700 May 6 07:25:01 Unraid-1 kernel: RBP: 0000000000000001 R08: 581d1522fa78d77e R09: bdb524e053fbe669 May 6 07:25:01 Unraid-1 kernel: R10: 1d850690a35a977f R11: ffffc900002a0d60 R12: ffffffff82a0e440 May 6 07:25:01 Unraid-1 kernel: R13: 00000000000021ac R14: ffff888102d85000 R15: 0000000000000000 May 6 07:25:01 Unraid-1 kernel: FS: 0000000000000000(0000) GS:ffff88883f7c0000(0000) knlGS:0000000000000000 May 6 07:25:01 Unraid-1 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 6 07:25:01 Unraid-1 kernel: CR2: 000000c004f76000 CR3: 000000000420a005 CR4: 00000000007706e0 May 6 07:25:01 Unraid-1 kernel: PKRU: 55555554 May 6 07:25:01 Unraid-1 kernel: Call Trace: May 6 07:25:01 Unraid-1 kernel: <IRQ> May 6 07:25:01 Unraid-1 kernel: ? nf_nat_inet_fn+0x123/0x1a8 [nf_nat] May 6 07:25:01 Unraid-1 kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] May 6 07:25:01 Unraid-1 kernel: nf_hook_slow+0x3a/0x96 May 6 07:25:01 Unraid-1 kernel: ? ip_protocol_deliver_rcu+0x164/0x164 May 6 07:25:01 Unraid-1 kernel: NF_HOOK.constprop.0+0x79/0xd9 May 6 07:25:01 Unraid-1 kernel: ? ip_protocol_deliver_rcu+0x164/0x164 May 6 07:25:01 Unraid-1 kernel: __netif_receive_skb_one_core+0x77/0x9c May 6 07:25:01 Unraid-1 kernel: process_backlog+0x8c/0x116 May 6 07:25:01 Unraid-1 kernel: __napi_poll.constprop.0+0x28/0x124 May 6 07:25:01 Unraid-1 kernel: net_rx_action+0x159/0x24f May 6 07:25:01 Unraid-1 kernel: __do_softirq+0x126/0x288 May 6 07:25:01 Unraid-1 kernel: do_softirq+0x7f/0xab May 6 07:25:01 Unraid-1 kernel: </IRQ> May 6 07:25:01 Unraid-1 kernel: <TASK> May 6 07:25:01 Unraid-1 kernel: __local_bh_enable_ip+0x4c/0x6b May 6 07:25:01 Unraid-1 kernel: netif_rx+0x52/0x5a May 6 07:25:01 Unraid-1 kernel: macvlan_broadcast+0x10a/0x150 [macvlan] May 6 07:25:01 Unraid-1 kernel: ? _raw_spin_unlock+0x14/0x29 May 6 07:25:01 Unraid-1 kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] May 6 07:25:01 Unraid-1 kernel: process_one_work+0x1a8/0x295 May 6 07:25:01 Unraid-1 kernel: worker_thread+0x18b/0x244 May 6 07:25:01 Unraid-1 kernel: ? rescuer_thread+0x281/0x281 May 6 07:25:01 Unraid-1 kernel: kthread+0xe4/0xef May 6 07:25:01 Unraid-1 kernel: ? kthread_complete_and_exit+0x1b/0x1b May 6 07:25:01 Unraid-1 kernel: ret_from_fork+0x1f/0x30 May 6 07:25:01 Unraid-1 kernel: </TASK> May 6 07:25:01 Unraid-1 kernel: ---[ end trace 0000000000000000 ]--- unraid-1-diagnostics-20230506-0727.zip

So, Server was running round about 4 Days. Last reboot was on Tuesday 7:14 AM . Logs from syslog server are attached. Pulling a diagnostic wasn't possible, Web and SSH are not reachable. I will now install RC5.3 and see what happen. download-2023.5.6_6.48.56-pi-(pi-3b).tar.gz

So, DHCP for IPv6 is deactivated and router should use SLAAC. Unraid used IPv4+IPv6, br0 and host access: unraid-1-diagnostics-20230502-2137.zip

Looks like it should: My pihole is reachable on ipv6 over fd00::99

I am not sure. To be fair, i am not a IPv6 Professional But if i'm right, it should be enough deactivating the DHCPv6 function in my router: https://en.avm.de/service/knowledge-base/dok/FRITZ-Box-7590/573_Configuring-IPv6-in-the-FRITZ-Box/ Should i use no DHCPv6 Server, or using the M- and/or O- Flag? I need br0 for IP-Based traffic- and port-management. And i'm using a Debian Container for remote access. When i disable host access, i can't reach all my containers from the Debian Container.

In this Case i used the "IPv4 only" mode, like you suggested. But my LXC Container was pingable over IPv6... i was just wondering. I am using both in my setup, br0 and host access.

oh damn... geoblock. sorry. nevermind it is only kernel cut off from syslog. must be also in the diagnostic, right?

so, after enabling "host access" on 16:13:44 it comes again: https://pastebin.cloud-becker.de/900ba9bc266a unraid-1-diagnostics-20230502-1626.zip

Okay, this time IPv4 without Host Access. But what i noticed: Unraid itself and Dockers aren't pingable with ipv6, but the LXC Container is: PS C:\Users\domib> ping [fd00::99] Ping wird ausgeführt für fd00::99 mit 32 Bytes Daten: Antwort von fd00::99: Zeit<1ms Antwort von fd00::99: Zeit<1ms Antwort von fd00::99: Zeit<1ms Antwort von fd00::99: Zeit<1ms Ping-Statistik für fd00::99: Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust), Ca. Zeitangaben in Millisek.: Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms PS C:\Users\domib> ping wpad.fritz.box -6 Ping wird ausgeführt für wpad.fritz.box [fd00::99] mit 32 Bytes Daten: Antwort von fd00::99: Zeit<1ms Antwort von fd00::99: Zeit<1ms Antwort von fd00::99: Zeit<1ms Antwort von fd00::99: Zeit<1ms Ping-Statistik für fd00::99: Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust), Ca. Zeitangaben in Millisek.: Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms PS C:\Users\domib> ping piholelxc.fritz.box Ping wird ausgeführt für piholelxc.fritz.box [192.168.0.11] mit 32 Bytes Daten: Antwort von 192.168.0.11: Bytes=32 Zeit<1ms TTL=64 Antwort von 192.168.0.11: Bytes=32 Zeit<1ms TTL=64 Antwort von 192.168.0.11: Bytes=32 Zeit<1ms TTL=64 Antwort von 192.168.0.11: Bytes=32 Zeit<1ms TTL=64 Ping-Statistik für 192.168.0.11: Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust), Ca. Zeitangaben in Millisek.: Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms PS C:\Users\domib> ping piholelxc.fritz.box -6 Ping-Anforderung konnte Host "piholelxc.fritz.box" nicht finden. Überprüfen Sie den Namen, und versuchen Sie es erneut. Inside of the LXC runs keepalived with the "virtual_ipaddress" 192.168.0.99 and fd00::99 unraid-1-diagnostics-20230502-1554.zip

Booting only IPv4, but with Host Access https://pastebin.cloud-becker.de/976631d6fe43 i will also try IPv4 without Host Access. unraid-1-diagnostics-20230502-1537.zip

I rebooted my Server for RC5. Before reboot i deactived "Host Access to custom networks". Got this again: https://pastebin.cloud-becker.de/11a75f37551e Diagnostic is attached. Seems that the "Host Access" isn't the trigger. unraid-1-diagnostics-20230502-0713.zip

okay, i did. if this won't help, i can mirrow the syslog to my flashdrive in the next step.

so, short update. @JorgeB todays morning my server crashed. the macvlan call trace was right after booting two days before. server runs without any problems from there for two days. when i tried opening the web gui i got messages from uptime-kuma and uptime-robot that the server becomes unresponsive. ssh, monitor/keyboard also didn't worked. anything to do next?

In combination with "host access" the Port Forwarding etc got corrupted. AVM was contacted, and they said, that multiple IP from the same MAC address isn't support. To be fair, i am not very experienced with macvlan/ipvlan/linux, so i don't know if i am explained the problem valid to AVM. Maybe contacting from Unraid-Side, as a Developer-to-Developer can bring cearness into this? I am only "one of thousand user, with a special unique problem" in their eyes.

Don't get me wrong i don't wanna be one of this "mimimi-User" who is blaming on the Devs, but i think this is a huge problem, especially for german user. The AVM Fritzbox is very common in Germany. And i think the German-Unraid Community is one of the biggest? I am very thankful for Unraid and they (Community-)Devs. But you got only "workarounds", but we need a fix for that. -Don't use Custom Bride br0 I need a dedicated IP for some Containers (Docker/LXC) for Traffic Management and Port Forwarding -Don't use Host Access Also needed for Bridged Container... (maybe i can handle it, putting all bridge Containers into a "custom user network" -Use ipvlan Isn't support by my Router (Fritzbox) -Use a second NIC. Can be a solution for me, but the most users doesn't have a second NIC onboard or the space for a second one. Again, please don't get me wrong, all in all i am very thankful for the development of Unraid which worked flawless till 6.12.x for me.

Hi, thanks for support v6.12.x with your plugin. Is a global exlcuding list possible? I want to exlude file like cache.db,.DS_Store,.log,.log.,.tmp completely?