UnRaid crash once in a while - caught a syslog, need help interpreting

[hundsboog]

Hello folks,

 

like the title said, I need some help with my UnRaid Box. Once in a while my server crashes and to be honest, I really don't know why. So I setup a syslog server on my second UnRaid machine to bring some light in that situation.

 

If someone could help me, whats causing this hickup would be fine.

Thanks alot and enjoy your sunday!

 

May  2 02:26:48 Tower emhttpd: read SMART /dev/sdj
May  2 02:58:12 Tower emhttpd: spinning down /dev/sdj
May  2 03:00:18 Tower emhttpd: read SMART /dev/sdj
May  2 03:32:45 Tower kernel: kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
May  2 03:32:45 Tower kernel: BUG: unable to handle page fault for address: ffffffff81a01640
May  2 03:32:45 Tower kernel: #PF: supervisor instruction fetch in kernel mode
May  2 03:32:45 Tower kernel: #PF: error_code(0x0011) - permissions violation
May  2 03:32:45 Tower kernel: PGD 200e067 P4D 200e067 PUD 200f063 PMD 10a2a75063 PTE 8000000001a01163
May  2 03:32:45 Tower kernel: Oops: 0011 [#1] SMP NOPTI
May  2 03:32:45 Tower kernel: CPU: 9 PID: 53622 Comm: CPU 0/KVM Not tainted 5.10.28-Unraid #1
May  2 03:32:45 Tower kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X399 Taichi, BIOS P3.90 12/04/2019
May  2 03:32:45 Tower kernel: RIP: 0010:0xffffffff81a01640
May  2 03:32:45 Tower kernel: Code: 6f 00 67 00 00 00 00 00 00 00 58 00 00 00 02 00 00 00 b6 40 00 00 00 00 32 01 89 0b 03 00 00 00 0b 00 20 a6 d5 1d 02 00 00 00 <68> 4d e1 70 89 31 d7 01 01 20 00 00 00 00 00 00 00 00 00 00 20 00
May  2 03:32:45 Tower kernel: RSP: 0018:ffffc90006a80ea8 EFLAGS: 00010202
May  2 03:32:45 Tower kernel: RAX: ffffffff81436103 RBX: ffff889084f0a008 RCX: 0000000000000240
May  2 03:32:45 Tower kernel: RDX: ffffc90006a80f10 RSI: ffffffff814382b9 RDI: ffff889084f0a008
May  2 03:32:45 Tower kernel: RBP: ffff88a03e45cb40 R08: ffff889084f0a728 R09: 0000000000000004
May  2 03:32:45 Tower kernel: R10: 0000000000000214 R11: ffff88a03e462400 R12: 00000000ffffffff
May  2 03:32:45 Tower kernel: R13: ffff889084f0a008 R14: ffffc90006a80f10 R15: ffffffff820060c8
May  2 03:32:45 Tower kernel: FS:  0000000000386000(0053) GS:ffff88a03e440000(002b) knlGS:0000000000384000
May  2 03:32:45 Tower kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May  2 03:32:45 Tower kernel: CR2: ffffffff81a01640 CR3: 0000001afcf3c000 CR4: 00000000003506e0
May  2 03:32:45 Tower kernel: Call Trace:
May  2 03:32:45 Tower kernel: <IRQ>
May  2 03:32:45 Tower kernel: ? iova_domain_flush+0x15/0x1c
May  2 03:32:45 Tower kernel: ? fq_flush_timeout+0x27/0x8b
May  2 03:32:45 Tower kernel: ? call_timer_fn.isra.0+0x12/0x6f
May  2 03:32:45 Tower kernel: ? fq_ring_free+0x92/0x92
May  2 03:32:45 Tower kernel: ? __run_timers.part.0+0x144/0x185
May  2 03:32:45 Tower kernel: ? update_process_times+0x68/0x6e
May  2 03:32:45 Tower kernel: ? hrtimer_forward+0x73/0x7b
May  2 03:32:45 Tower kernel: ? tick_sched_timer+0x5a/0x64
May  2 03:32:45 Tower kernel: ? timerqueue_add+0x62/0x68
May  2 03:32:45 Tower kernel: ? run_timer_softirq+0x21/0x43
May  2 03:32:45 Tower kernel: ? __do_softirq+0xc4/0x1c2
May  2 03:32:45 Tower kernel: ? asm_call_irq_on_stack+0x12/0x20
May  2 03:32:45 Tower kernel: </IRQ>
May  2 03:32:45 Tower kernel: ? do_softirq_own_stack+0x2c/0x39
May  2 03:32:45 Tower kernel: ? __irq_exit_rcu+0x45/0x80
May  2 03:32:45 Tower kernel: ? sysvec_apic_timer_interrupt+0x87/0x95
May  2 03:32:45 Tower kernel: ? asm_sysvec_apic_timer_interrupt+0x12/0x20
May  2 03:32:45 Tower kernel: ? kvm_vcpu_running+0x7/0x38 [kvm]
May  2 03:32:45 Tower kernel: ? apic_has_pending_timer+0xf/0x2c [kvm]
May  2 03:32:45 Tower kernel: ? kvm_arch_vcpu_ioctl_run+0x21b/0x1363 [kvm]
May  2 03:32:45 Tower kernel: ? __bpf_prog_run32+0x35/0x51
May  2 03:32:45 Tower kernel: ? __wake_up_common+0xa7/0x12f
May  2 03:32:45 Tower kernel: ? kvm_vcpu_ioctl+0x176/0x4ac [kvm]
May  2 03:32:45 Tower kernel: ? vfs_ioctl+0x19/0x26
May  2 03:32:45 Tower kernel: ? __do_sys_ioctl+0x51/0x74
May  2 03:32:45 Tower kernel: ? do_syscall_64+0x5d/0x6a
May  2 03:32:45 Tower kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
May  2 03:32:45 Tower kernel: Modules linked in: xt_connmark xt_comment iptable_raw xt_mark xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle nf_tables vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter xfs nfsd lockd grace sunrpc md_mod nct6775 hwmon_vid iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding igb i2c_algo_bit edac_mce_amd kvm_amd kvm btusb btrtl btbcm btintel bluetooth crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd ecdh_generic wmi_bmof mxm_wmi i2c_piix4 ecc cryptd i2c_core ahci glue_helper ccp rapl wmi k10temp libahci button acpi_cpufreq [last unloaded: i2c_algo_bit]
May  2 03:32:45 Tower kernel: CR2: ffffffff81a01640

 

 

Regards,

 

hundsboog

[barnowan]

I know it's been a while, but did you happen to find the solution to this? I'm running into the same issues with very similar error messages.