February 1, 20242 yr Bonjour , Mon unraid plante systématiquement mais de facon aléatoire , je m'explique . Parfois alors qu'il est au repos , parfois lors de l'usage de share , parfois au bout de dix minute , parfois au bout de 2 jours... J'ai trouvé ca dans le kernel.log : WARNING: CPU: 20 PID: 15473 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] 2024-01-30T13:11:49+00:00 Tower kernel: Modules linked in: tls bluetooth ecdh_generic ecc xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables macvtap macvlan tap af_packet bridge 8021q garp mrp stp llc ixgbe xfrm_algo mdio r8169 realtek intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd rapl i2c_i801 intel_cstate mxm_wmi nvme i2c_smbus intel_uncore ahci i2c_core nvme_core 2024-01-30T13:11:49+00:00 Tower kernel: input_leds libahci led_class cdc_acm wmi button unix [last unloaded: xfrm_algo] 2024-01-30T13:11:49+00:00 Tower kernel: CPU: 20 PID: 15473 Comm: kworker/u48:2 Tainted: P O 6.1.64-Unraid #1 2024-01-30T13:11:49+00:00 Tower kernel: Hardware name: OEM X99-Turbo/X99-Turbo, BIOS 5.11 04/21/2022 2024-01-30T13:11:49+00:00 Tower kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan] 2024-01-30T13:11:49+00:00 Tower kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] 2024-01-30T13:11:49+00:00 Tower 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 2024-01-30T13:11:49+00:00 Tower kernel: RSP: 0018:ffffc900005b8d98 EFLAGS: 00010202 2024-01-30T13:11:49+00:00 Tower kernel: RAX: 0000000000000001 RBX: ffff88829530ca00 RCX: 1cd3587c04a669cb 2024-01-30T13:11:49+00:00 Tower kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88829530ca00 2024-01-30T13:11:49+00:00 Tower kernel: RBP: 0000000000000001 R08: 679cf2109bf4b5b0 R09: 929021535685e287 2024-01-30T13:11:49+00:00 Tower kernel: R10: 3c3230b131b902e4 R11: ffffc900005b8d60 R12: ffffffff82a14d00 2024-01-30T13:11:49+00:00 Tower kernel: R13: 000000000003276a R14: ffff88836e256300 R15: 0000000000000000 2024-01-30T13:11:49+00:00 Tower kernel: FS: 0000000000000000(0000) GS:ffff88885fd00000(0000) knlGS:0000000000000000 2024-01-30T13:11:49+00:00 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2024-01-30T13:11:49+00:00 Tower kernel: CR2: 0000145de747aa60 CR3: 000000000220a001 CR4: 00000000001726e0 2024-01-30T13:11:49+00:00 Tower kernel: Call Trace: 2024-01-30T13:11:49+00:00 Tower kernel: <IRQ> 2024-01-30T13:11:49+00:00 Tower kernel: ? __warn+0xab/0x122 2024-01-30T13:11:49+00:00 Tower kernel: ? report_bug+0x109/0x17e 2024-01-30T13:11:49+00:00 Tower kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] 2024-01-30T13:11:49+00:00 Tower kernel: ? handle_bug+0x41/0x6f 2024-01-30T13:11:49+00:00 Tower kernel: ? exc_invalid_op+0x13/0x60 2024-01-30T13:11:49+00:00 Tower kernel: ? asm_exc_invalid_op+0x16/0x20 2024-01-30T13:11:49+00:00 Tower kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] 2024-01-30T13:11:49+00:00 Tower kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack] 2024-01-30T13:11:49+00:00 Tower kernel: ? nf_nat_inet_fn+0x60/0x1a8 [nf_nat] 2024-01-30T13:11:49+00:00 Tower kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] 2024-01-30T13:11:49+00:00 Tower kernel: nf_hook_slow+0x3d/0x96 2024-01-30T13:11:49+00:00 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164 2024-01-30T13:11:49+00:00 Tower kernel: NF_HOOK.constprop.0+0x79/0xd9 2024-01-30T13:11:49+00:00 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164 2024-01-30T13:11:49+00:00 Tower kernel: __netif_receive_skb_one_core+0x77/0x9c 2024-01-30T13:11:49+00:00 Tower kernel: process_backlog+0x8c/0x116 2024-01-30T13:11:49+00:00 Tower kernel: __napi_poll.constprop.0+0x2b/0x124 2024-01-30T13:11:49+00:00 Tower kernel: net_rx_action+0x159/0x24f 2024-01-30T13:11:49+00:00 Tower kernel: __do_softirq+0x129/0x288 2024-01-30T13:11:49+00:00 Tower kernel: do_softirq+0x7f/0xab 2024-01-30T13:11:49+00:00 Tower kernel: </IRQ> 2024-01-30T13:11:49+00:00 Tower kernel: <TASK> 2024-01-30T13:11:49+00:00 Tower kernel: __local_bh_enable_ip+0x4c/0x6b 2024-01-30T13:11:49+00:00 Tower kernel: netif_rx+0x52/0x5a 2024-01-30T13:11:49+00:00 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] 2024-01-30T13:11:49+00:00 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] 2024-01-30T13:11:49+00:00 Tower kernel: process_one_work+0x1ab/0x295 2024-01-30T13:11:49+00:00 Tower kernel: worker_thread+0x18b/0x244 2024-01-30T13:11:49+00:00 Tower kernel: ? rescuer_thread+0x281/0x281 2024-01-30T13:11:49+00:00 Tower kernel: kthread+0xe7/0xef 2024-01-30T13:11:49+00:00 Tower kernel: ? kthread_complete_and_exit+0x1b/0x1b 2024-01-30T13:11:49+00:00 Tower kernel: ret_from_fork+0x22/0x30 2024-01-30T13:11:49+00:00 Tower kernel: </TASK> 2024-01-30T13:11:49+00:00 Tower kernel: ---[ end trace 0000000000000000 ]--- ce qui semble correspondre à ce que l'écran du serveur physique affiche ( quand il l'affiche ) Auriez vous une idée ? Merci d'avance , Cordialement ,
February 15, 20242 yr Author Bonjour , Oui je pensais que cela venait du hardware qui était un peu vieux donc j'ai tout changé ( CM ,CPU et RAM ) mais même résultat Cordialement
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.