BigChris Posted February 17 Share Posted February 17 Guten Morgen, mein alter Unraid-Server ist während eines Parity Sync kaputt gegangen. Ich habe die Festplatten nun in eine neue Maschine gesetzt und einen Parity-Sync gestartet. Da ist der Unraid während dessen abgestürzt, war nicht mehr erreichbar. Ich habe nun einen neuen Sync gestartet und versuche das Log im Auge zu behalten. Dabei sind mir zwei Errors aufgefallen bisher: Rot markiert sind folgende Zeilen: Feb 17 08:53:10 Tower kernel: CPU: 1 PID: 1700 Comm: .NET ThreadPool Tainted: P IO 6.1.64-Unraid #1 Feb 17 08:53:10 Tower kernel: Call Trace: Feb 17 08:53:10 Tower kernel: CPU: 1 PID: 1700 Comm: .NET ThreadPool Tainted: P IO 6.1.64-Unraid #1 Feb 17 08:53:10 Tower kernel: Hardware name: Dell Inc. PowerEdge T30/07T4MC, BIOS 1.8.1 12/16/2021 Feb 17 08:53:10 Tower kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Feb 17 08:53:10 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 Feb 17 08:53:10 Tower kernel: RSP: 0000:ffffc90008427810 EFLAGS: 00010202 Feb 17 08:53:10 Tower kernel: RAX: 0000000000000001 RBX: ffff8881598e5800 RCX: 74bd1bfd2f712247 Feb 17 08:53:10 Tower kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881598e5800 Feb 17 08:53:10 Tower kernel: RBP: 0000000000000001 R08: defca66ae9fd4719 R09: 1c041881253606c3 Feb 17 08:53:10 Tower kernel: R10: 8015b9512acd639d R11: ffffc900084277d8 R12: ffffffff82a14d00 Feb 17 08:53:10 Tower kernel: R13: 000000000001efb7 R14: ffff8881786b9300 R15: 0000000000000000 Feb 17 08:53:10 Tower kernel: FS: 0000150ace1fd700(0000) GS:ffff888265c80000(0000) knlGS:0000000000000000 Feb 17 08:53:10 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 17 08:53:10 Tower kernel: CR2: 000000000042b6a0 CR3: 000000015a8b2004 CR4: 00000000003706e0 Feb 17 08:53:10 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Feb 17 08:53:10 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Feb 17 08:53:10 Tower kernel: Call Trace: Feb 17 08:53:10 Tower kernel: <TASK> Feb 17 08:53:10 Tower kernel: ? __warn+0xab/0x122 Feb 17 08:53:10 Tower kernel: ? report_bug+0x109/0x17e Feb 17 08:53:10 Tower kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Feb 17 08:53:10 Tower kernel: ? handle_bug+0x41/0x6f Feb 17 08:53:10 Tower kernel: ? exc_invalid_op+0x13/0x60 Feb 17 08:53:10 Tower kernel: ? asm_exc_invalid_op+0x16/0x20 Feb 17 08:53:10 Tower kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Feb 17 08:53:10 Tower kernel: ? nf_nat_inet_fn+0xc0/0x1a8 [nf_nat] Feb 17 08:53:10 Tower kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Feb 17 08:53:10 Tower kernel: nf_hook_slow+0x3a/0x96 Feb 17 08:53:10 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Feb 17 08:53:10 Tower kernel: NF_HOOK.constprop.0+0x79/0xd9 Feb 17 08:53:10 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Feb 17 08:53:10 Tower kernel: ip_sabotage_in+0x4f/0x60 [br_netfilter] Feb 17 08:53:10 Tower kernel: nf_hook_slow+0x3a/0x96 Feb 17 08:53:10 Tower kernel: ? ip_rcv_finish_core.constprop.0+0x3e8/0x3e8 Feb 17 08:53:10 Tower kernel: NF_HOOK.constprop.0+0x79/0xd9 Feb 17 08:53:10 Tower kernel: ? ip_rcv_finish_core.constprop.0+0x3e8/0x3e8 Feb 17 08:53:10 Tower kernel: __netif_receive_skb_one_core+0x77/0x9c Feb 17 08:53:10 Tower kernel: netif_receive_skb+0xbf/0x127 Feb 17 08:53:10 Tower kernel: br_handle_frame_finish+0x43a/0x474 [bridge] Feb 17 08:53:10 Tower kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] Feb 17 08:53:10 Tower kernel: br_nf_hook_thresh+0xe2/0x109 [br_netfilter] Feb 17 08:53:10 Tower kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] Feb 17 08:53:10 Tower kernel: br_nf_pre_routing_finish+0x2c1/0x2ec [br_netfilter] Feb 17 08:53:10 Tower kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] Feb 17 08:53:10 Tower kernel: ? br_nf_hook_thresh+0x109/0x109 [br_netfilter] Feb 17 08:53:10 Tower kernel: br_nf_pre_routing+0x236/0x24a [br_netfilter] Feb 17 08:53:10 Tower kernel: ? br_nf_hook_thresh+0x109/0x109 [br_netfilter] Feb 17 08:53:10 Tower kernel: br_handle_frame+0x277/0x2e0 [bridge] Feb 17 08:53:10 Tower kernel: ? kill_orphaned_pgrp+0x3b/0xad Feb 17 08:53:10 Tower kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] Feb 17 08:53:10 Tower kernel: __netif_receive_skb_core.constprop.0+0x4fa/0x6e9 Feb 17 08:53:10 Tower kernel: ? __build_skb+0x20/0x4e Feb 17 08:53:10 Tower kernel: ? kmem_cache_alloc+0x122/0x14d Feb 17 08:53:10 Tower kernel: __netif_receive_skb_list_core+0x8a/0x11e Feb 17 08:53:10 Tower kernel: netif_receive_skb_list_internal+0x1d2/0x20b Feb 17 08:53:10 Tower kernel: gro_normal_list+0x1d/0x3f Feb 17 08:53:10 Tower kernel: napi_complete_done+0x7b/0x11a Feb 17 08:53:10 Tower kernel: e1000e_poll+0x9e/0x23e [e1000e] Feb 17 08:53:10 Tower kernel: __napi_poll.constprop.0+0x28/0x124 Feb 17 08:53:10 Tower kernel: net_rx_action+0x159/0x24f Feb 17 08:53:10 Tower kernel: ? e1000_intr_msi+0x118/0x124 [e1000e] Feb 17 08:53:10 Tower kernel: __do_softirq+0x126/0x288 Feb 17 08:53:10 Tower kernel: __irq_exit_rcu+0x5e/0xb8 Feb 17 08:53:10 Tower kernel: common_interrupt+0x3b/0xc1 Feb 17 08:53:10 Tower kernel: asm_common_interrupt+0x22/0x40 Feb 17 08:53:10 Tower kernel: RIP: 0033:0x150b7e6daff7 Feb 17 08:53:10 Tower kernel: Code: 73 01 c3 48 8b 0d 91 3e 2d 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 b8 18 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 61 3e 2d 00 f7 d8 64 89 01 48 Feb 17 08:53:10 Tower kernel: RSP: 002b:0000150ace1fc9a8 EFLAGS: 00000246 Feb 17 08:53:10 Tower kernel: RAX: 0000000000000000 RBX: 0000150abc017730 RCX: 0000150b7e6daff7 Feb 17 08:53:10 Tower kernel: RDX: 0000150b7fc19320 RSI: 0000000000000001 RDI: 0000000000000010 Feb 17 08:53:10 Tower kernel: RBP: 0000150ace1fc9f0 R08: 0000150abc017730 R09: e15bd102ab382c7d Feb 17 08:53:10 Tower kernel: R10: 00007ffe7a1f4080 R11: 0000000000000246 R12: 0000150abc013b50 Feb 17 08:53:10 Tower kernel: R13: 000000000000004a R14: 0000000000000000 R15: 0000000000000000 Feb 17 08:53:10 Tower kernel: </TASK> Feb 17 08:53:10 Tower kernel: ---[ end trace 0000000000000000 ]--- Hat das schon was zu bedeuten? Oder sollte ich stattdessen einen Parity rebuild starten? Quote Link to comment
Solution Mainfrezzer Posted February 17 Solution Share Posted February 17 https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces Quote Link to comment
Recommended Posts
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.