Server keeps powering off since 6.11 update

[Runaround]

Howdy.

 

My server has been working really well until I updated it to 6.11. For some reason since then it has been powering off at night randomly. The uptime is usually only a couple of days. If I don't start the array it seems to keep running. I'm really at a loss on the cause of this. I've looked a little bit at the syslog but it doesn't show any warning before it turns off. I've attached the diagnostics log bundle. I'm currently running 6.11.3. Any assistance would be greatly appreciated.

nas4-diagnostics-20221114-0943.zip

[JorgeB]

Start here:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

 

[Runaround]

Thank you JorgeB for your quick reply. I actually had to go through all that checking when I previously had an issue. It had been running very well. The CPU is at stock speeds as is the memory. I also reduced from 4 DIMMs to 2.

 

I happened to get a Kernel warning in the syslog a little bit ago, which is below. I found in a previous request changing the docker custom network type to ipvlan. Do you think this is still worth trying?

 

Nov 14 16:53:56 NAS4 kernel: ------------[ cut here ]------------
Nov 14 16:53:56 NAS4 kernel: WARNING: CPU: 12 PID: 1260 at net/netfilter/nf_conntrack_core.c:1208 __nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack]
Nov 14 16:53:56 NAS4 kernel: Modules linked in: macvlan nvidia_uvm(PO) veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod ipmi_devintf ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) drm_kms_helper drm edac_mce_amd edac_core kvm_amd kvm wmi_bmof crct10dif_pclmul mxm_wmi crc32_pclmul asus_wmi_sensors crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd igb mpt3sas cryptd rapl backlight i2c_piix4 nvme i2c_algo_bit k10temp syscopyarea i2c_core nvme_core ccp sysfillrect ahci raid_class sysimgblt fb_sys_fops scsi_transport_sas libahci wmi button acpi_cpufreq unix
Nov 14 16:53:56 NAS4 kernel: CPU: 12 PID: 1260 Comm: kworker/12:1 Tainted: P           O      5.19.17-Unraid #2
Nov 14 16:53:56 NAS4 kernel: Hardware name: System manufacturer System Product Name/ROG STRIX X470-F GAMING, BIOS 5809 12/03/2020
Nov 14 16:53:56 NAS4 kernel: Workqueue: events macvlan_process_broadcast [macvlan]
Nov 14 16:53:56 NAS4 kernel: RIP: 0010:__nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack]
Nov 14 16:53:56 NAS4 kernel: Code: c6 48 89 44 24 10 e8 dd e2 ff ff 8b 7c 24 04 89 da 89 c6 89 04 24 e8 56 e6 ff ff 84 c0 75 a2 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 16 de ff ff e8 2c e3 ff ff e9 7e 01
Nov 14 16:53:56 NAS4 kernel: RSP: 0018:ffffc90000468cf0 EFLAGS: 00010202
Nov 14 16:53:56 NAS4 kernel: RAX: 0000000000000188 RBX: 0000000000000000 RCX: 04b1607232711a15
Nov 14 16:53:56 NAS4 kernel: RDX: 0000000000000000 RSI: 0000000000000328 RDI: ffffffffa046709c
Nov 14 16:53:56 NAS4 kernel: RBP: ffff888105c3f600 R08: bcbcf0f29609d337 R09: e535f8438e9bc070
Nov 14 16:53:56 NAS4 kernel: R10: e038729afc21c74d R11: 74f7e7d7c2846d05 R12: ffffffff82909480
Nov 14 16:53:56 NAS4 kernel: R13: 000000000002bb97 R14: ffff888095ea2400 R15: 0000000000000000
Nov 14 16:53:56 NAS4 kernel: FS:  0000000000000000(0000) GS:ffff88841eb00000(0000) knlGS:0000000000000000
Nov 14 16:53:56 NAS4 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 14 16:53:56 NAS4 kernel: CR2: 00000ab78cdaf002 CR3: 0000000273362000 CR4: 00000000003506e0
Nov 14 16:53:56 NAS4 kernel: Call Trace:
Nov 14 16:53:56 NAS4 kernel: <IRQ>
Nov 14 16:53:56 NAS4 kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack]
Nov 14 16:53:56 NAS4 kernel: nf_hook_slow+0x3d/0x96
Nov 14 16:53:56 NAS4 kernel: ? ip_protocol_deliver_rcu+0x164/0x164
Nov 14 16:53:56 NAS4 kernel: NF_HOOK.constprop.0+0x79/0xd9
Nov 14 16:53:56 NAS4 kernel: ? ip_protocol_deliver_rcu+0x164/0x164
Nov 14 16:53:56 NAS4 kernel: ip_sabotage_in+0x4a/0x58 [br_netfilter]
Nov 14 16:53:56 NAS4 kernel: nf_hook_slow+0x3d/0x96
Nov 14 16:53:56 NAS4 kernel: ? ip_rcv_finish_core.constprop.0+0x3b7/0x3b7
Nov 14 16:53:56 NAS4 kernel: NF_HOOK.constprop.0+0x79/0xd9
Nov 14 16:53:56 NAS4 kernel: ? ip_rcv_finish_core.constprop.0+0x3b7/0x3b7
Nov 14 16:53:56 NAS4 kernel: __netif_receive_skb_one_core+0x77/0x9c
Nov 14 16:53:56 NAS4 kernel: process_backlog+0x8c/0x116
Nov 14 16:53:56 NAS4 kernel: __napi_poll.constprop.0+0x2b/0x124
Nov 14 16:53:56 NAS4 kernel: net_rx_action+0x159/0x24f
Nov 14 16:53:56 NAS4 kernel: __do_softirq+0x129/0x288
Nov 14 16:53:56 NAS4 kernel: do_softirq+0x7f/0xab
Nov 14 16:53:56 NAS4 kernel: </IRQ>
Nov 14 16:53:56 NAS4 kernel: <TASK>
Nov 14 16:53:56 NAS4 kernel: __local_bh_enable_ip+0x4c/0x6b
Nov 14 16:53:56 NAS4 kernel: netif_rx+0x52/0x5a
Nov 14 16:53:56 NAS4 kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Nov 14 16:53:56 NAS4 kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]
Nov 14 16:53:56 NAS4 kernel: process_one_work+0x1ab/0x295
Nov 14 16:53:56 NAS4 kernel: worker_thread+0x18b/0x244
Nov 14 16:53:56 NAS4 kernel: ? rescuer_thread+0x281/0x281
Nov 14 16:53:56 NAS4 kernel: kthread+0xe7/0xef
Nov 14 16:53:56 NAS4 kernel: ? kthread_complete_and_exit+0x1b/0x1b
Nov 14 16:53:56 NAS4 kernel: ret_from_fork+0x22/0x30
Nov 14 16:53:56 NAS4 kernel: </TASK>
Nov 14 16:53:56 NAS4 kernel: ---[ end trace 0000000000000000 ]---

 

[JorgeB]

8 hours ago, Runaround said:

Do you think this is still worth trying?

Yes, though that should cause a crash, not a shutdown.