February 4, 20251 yr My system has been doing this for a long time and I haven't gotten to troubleshoot it till now. From what I can tell I thought it might be a memory issue, so I'm running memtest but its on its second pass with no errors yet. My only other thought is that the plex error is causing the kernel to crash out. Feb 4 03:50:40 katahdin kernel: BUG: unable to handle page fault for address: 0000000000080010 Feb 4 03:50:40 katahdin kernel: #PF: supervisor read access in kernel mode Feb 4 03:50:40 katahdin kernel: #PF: error_code(0x0000) - not-present page Feb 4 03:50:40 katahdin kernel: PGD 0 P4D 0 Feb 4 03:50:40 katahdin kernel: Oops: 0000 [#1] PREEMPT SMP PTI Feb 4 03:50:40 katahdin kernel: CPU: 4 PID: 28660 Comm: unraidd3 Tainted: P O 6.1.74-Unraid #1 Feb 4 03:50:40 katahdin kernel: Hardware name: Gigabyte Technology Co., Ltd. Z87X-UD4H/Z87X-UD4H-CF, BIOS F9 03/18/2014 Feb 4 03:50:40 katahdin kernel: RIP: 0010:unraidd+0xfb2/0x1140 [md_mod] Feb 4 03:50:40 katahdin kernel: Code: c0 01 00 00 31 ed 49 81 c4 08 01 00 00 39 6c 24 30 0f 8e 26 01 00 00 49 8b 56 80 4d 8d 6e 88 31 c0 4d 8b 3c 24 48 85 d2 74 0c <8b> 42 10 25 00 08 02 00 09 44 24 4c f0 49 0f ba b6 68 ff ff ff 0a Feb 4 03:50:40 katahdin kernel: RSP: 0018:ffffc90001d1fdf0 EFLAGS: 00010206 Feb 4 03:50:40 katahdin kernel: RAX: 0000000000000000 RBX: ffff88815f00c5e8 RCX: 0000000000000000 Feb 4 03:50:40 katahdin kernel: RDX: 0000000000080000 RSI: 0000000000000005 RDI: ffff8883a6335a80 Feb 4 03:50:40 katahdin kernel: RBP: 0000000000000004 R08: 0000000000000000 R09: ffffc90001d1fd58 Feb 4 03:50:40 katahdin kernel: R10: 0000000000000000 R11: ffff888100400068 R12: ffff8881696e4128 Feb 4 03:50:40 katahdin kernel: R13: ffff88815f00c9f0 R14: ffff88815f00ca68 R15: ffff88816965e718 Feb 4 03:50:40 katahdin kernel: FS: 0000000000000000(0000) GS:ffff88884f300000(0000) knlGS:0000000000000000 Feb 4 03:50:40 katahdin kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 4 03:50:40 katahdin kernel: CR2: 0000000000080010 CR3: 000000000420a002 CR4: 00000000001706e0 Feb 4 03:50:40 katahdin kernel: Call Trace: Feb 4 03:50:40 katahdin kernel: <TASK> Feb 4 03:50:40 katahdin kernel: ? __die_body+0x1a/0x5c Feb 4 03:50:40 katahdin kernel: ? page_fault_oops+0x329/0x376 Feb 4 03:50:40 katahdin kernel: ? fixup_exception+0x22/0x24b Feb 4 03:50:40 katahdin kernel: ? exc_page_fault+0xfb/0x11d Feb 4 03:50:40 katahdin kernel: ? asm_exc_page_fault+0x22/0x30 Feb 4 03:50:40 katahdin kernel: ? unraidd+0xfb2/0x1140 [md_mod] Feb 4 03:50:40 katahdin kernel: md_thread+0xf7/0x122 [md_mod] Feb 4 03:50:40 katahdin kernel: ? _raw_spin_rq_lock_irqsave+0x20/0x20 Feb 4 03:50:40 katahdin kernel: ? signal_pending+0x1d/0x1d [md_mod] Feb 4 03:50:40 katahdin kernel: kthread+0xe7/0xef Feb 4 03:50:40 katahdin kernel: ? kthread_complete_and_exit+0x1b/0x1b Feb 4 03:50:40 katahdin kernel: ret_from_fork+0x22/0x30 Feb 4 03:50:40 katahdin kernel: </TASK> Feb 4 03:50:40 katahdin kernel: Modules linked in: macvtap macvlan tap nvidia_uvm(PO) xt_connmark xt_mark iptable_mangle xt_comment iptable_raw veth xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag it87 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 libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs af_packet 8021q garp mrp bridge stp llc bonding tls nvidia_drm(PO) nvidia_modeset(PO) intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel i915 kvm nvidia(PO) crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel iosf_mbi drm_buddy i2c_algo_bit crypto_simd Feb 4 03:50:40 katahdin kernel: ttm cryptd drm_display_helper rapl mei_hdcp drm_kms_helper mei_pxp i2c_i801 intel_gtt intel_cstate mxm_wmi drm intel_uncore agpgart i2c_smbus mei_me syscopyarea i2c_core ahci sysfillrect input_leds sysimgblt libahci e1000e mei joydev led_class fb_sys_fops thermal fan video wmi backlight button unix Feb 4 03:50:40 katahdin kernel: CR2: 0000000000080010 syslog (1)
February 4, 20251 yr Community Expert Unraid driver is crashing, and that is almost always a hardware problem.
February 4, 20251 yr Author 15 minutes ago, JorgeB said: Unraid driver is crashing, and that is almost always a hardware problem. Are there any clues to what hardware might be causing the issue? I have a lot of hardware in there, It's going to take a long while to guess and check.
February 4, 20251 yr Community Expert We would have more clues about what hardware you have if you Attach Diagnostics to your NEXT post in this thread.
February 5, 20251 yr Community Expert Memtest is a good place to start, or since memtest is only definitive if it finds errors, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.
February 5, 20251 yr Community Expert 1 hour ago, jag5cof said: These issues I'm having with the Unraid 7 driver crashing, I didn't have with 6.12.3. Please start a new thread, the OP's issue is still not resolved, so this can get confusing.
February 5, 20251 yr Community Expert 3 hours ago, JorgeB said: Please start a new thread, the OP's issue is still not resolved, so this can get confusing. Obviously it already confused me. 5 hours ago, trurl said: Since you have ECC, and I didn't notice any memory corrections in your syslog, probably RAM is not the problem. I have split those to another thread here:
February 5, 20251 yr Community Expert To get us back on track 22 hours ago, trurl said: We would have more clues about what hardware you have if you Attach Diagnostics to your NEXT post in this thread.
February 23, 20251 yr Author diagnostics from post reboot (unclean shutdown) log pre reboot. I should mention that i have completed a memtest with no issues. im sure its a hardware issue, im leaning toward the mb or cpu causing the issue. katahdin-diagnostics-20250222-1914.zip syslog
February 23, 20251 yr Community Expert Let's simplify things somewhat. Disable Docker in Settings. Unassign disk1. Reboot in SAFE mode Post new diagnostics with the array started.
February 23, 20251 yr Community Expert Emulated disk1 is mounted and seems to have its data. Reassign disk1 and see if it will complete rebuild.
February 23, 20251 yr Author I've tried to complete it before, and it makes it to 100% and then hangs. I have left it running for 6 hrs after hitting 100% and it hung till the system became unresponsive and have to force a restart. is there anyway i can facilitate it to complete?
February 24, 20251 yr Community Expert 25 minutes ago, mountainmantra said: I've tried to complete it before Did you try it like this? 22 hours ago, trurl said: Disable Docker in Settings....Reboot in SAFE mode
February 24, 20251 yr Community Expert And post new diags, or the syslog at least, if it hangs again.
February 25, 20251 yr Author rebuild in safe mode completed successfully. i rebooted outside of safe mode, and turned docker on, ran some containers overnight and woke up to the ui unresponsive. here is the log from overnight. syslog 2
February 25, 20251 yr Community Expert There's a call trace at around 5AM, but unclear to me what caused it, see if it happens with docker disabled, if not, then start enabling the containers one by one and retesting.
February 28, 20251 yr Author unresponsive again this morning. docker running with only plex on. it was running a parity check as well though syslog 3
February 28, 20251 yr Community Expert Nothing relevant logged this time, a few ata errors with ata1, check/replace cables, but not a reason for the server to crash typically.
March 1, 20251 yr Author same situation, hanging without anything outstanding that i can tell in the logging. any suggestions on how to troubleshoot further? syslog 4
March 1, 20251 yr Community Expert The previous errors with the Unraid driver crashing suggest a hardware issue, but without anything else logged, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one, including the individual docker containers. Additionally, look in the BIOS for a "Global C-States" or similar setting and disable that to retest, it's been known to be a problem with some boards, with both Intel and AMD CPUs.
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.