May 24, 20251 yr Hi Folks,I recently added 2 more (new) disk's to my array.Yesterday I added a parity first. Synced fine. Today I wanted to add the next disk to the array and had to wait 7 hours for it to maybe finish?! I don't know if it really finished in a way. When I was trying to connect or interact with the server, everything seemed dead. (It's no real server. Desktop MB with ryzen 7 1700x and now 6x 4TB NAS disks) However I never had an issue in that way. I had to forcefully power off the system because nothing worked. (no ssh, hdmi, network or something else.I cannot find evidence of what happened after the sync might have finished.I restarted the server and now I have to wait until the sync finishes again in a couple of hours...Are there some settings for better logging in case of crashes?
May 25, 20251 yr Community Expert Only if you had the syslog server enabled, regular syslog starts over after every boot.
June 9, 20251 yr Author Hi again,sorry that I haven't replied back earlier. Was trying troubleshooting a bit.Haven't found a real solution yet.I still have random crashes in different varieties. Either the server is freezing completely, or it's crashing and rebooting, or crashing/rebooting but still not coming up properly again.Really weird symptoms.I experience these issues since I added more disks and upgraded my RAM. (I know the RAM is fine. got 2 different sets of ram and it behaves the same with any one of them.I assume it's either my CPU or the amount of disk drives...However, I managed to get rsyslog on another system running to get a better log view for my unraid system.The times logged dont match the exact time it happened. Maybe need to configure a proper NTP on unraid...The only thing that IMO stands out and is being logged last, are the kernel log's.Here a snippet:kernel.log2025-06-09T02:08:08+02:00 NASty kernel: </TASK>2025-06-09T02:08:37+02:00 NASty kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:2025-06-09T02:08:37+02:00 NASty kernel: rcu: #01113-....: (239999 ticks this GP) idle=3aac/1/0x4000000000000000 softirq=106882/346221 fqs=480002025-06-09T02:08:37+02:00 NASty kernel: rcu: #011(detected by 5, t=240005 jiffies, g=439565, q=292771 ncpus=16)2025-06-09T02:08:37+02:00 NASty kernel: Sending NMI from CPU 5 to CPUs 13:2025-06-09T02:08:37+02:00 NASty kernel: NMI backtrace for cpu 132025-06-09T02:08:37+02:00 NASty kernel: CPU: 13 UID: 99 PID: 16573 Comm: PMS ReqHandler Tainted: P O 6.12.24-Unraid #12025-06-09T02:08:37+02:00 NASty kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE2025-06-09T02:08:37+02:00 NASty kernel: Hardware name: ASUS System Product Name/CROSSHAIR VI HERO, BIOS 8801 08/30/20242025-06-09T02:08:37+02:00 NASty kernel: RIP: 0010:smp_call_function_many_cond+0x329/0x3502025-06-09T02:08:37+02:00 NASty kernel: Code: 01 48 63 d0 4c 89 e7 e8 a5 01 4c 00 3b 05 0f d8 4c 01 73 1e 48 63 c8 48 8b 13 48 03 14 cd 40 82 36 82 8b 4a 08 80 e1 01 74 04 <f3> 90 eb f4 ff c0 eb c9 48 83 c4 38 5b 5d 41 5c 41 5d 41 5e 41 5f2025-06-09T02:08:37+02:00 NASty kernel: RSP: 0018:ffffc9000651fb28 EFLAGS: 000002022025-06-09T02:08:37+02:00 NASty kernel: RAX: 0000000000000002 RBX: ffff88842ef71300 RCX: 00000000000000012025-06-09T02:08:37+02:00 NASty kernel: RDX: ffff88842ecb59e0 RSI: 0000000000000010 RDI: ffff88842ef713082025-06-09T02:08:37+02:00 NASty kernel: RBP: 0000000000000001 R08: 0000000000000002 R09: 00000000000000002025-06-09T02:08:37+02:00 NASty kernel: R10: 0000000000000000 R11: ffffea000411ad00 R12: ffff88842ef713082025-06-09T02:08:37+02:00 NASty kernel: R13: ffff88842eff59e0 R14: 0000000000000001 R15: 00000000000000102025-06-09T02:08:37+02:00 NASty kernel: FS: 0000145a8f965b38(0000) GS:ffff88842ef40000(0000) knlGS:00000000000000002025-06-09T02:08:37+02:00 NASty kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 00000000800500332025-06-09T02:08:37+02:00 NASty kernel: CR2: 000014a7b80bb000 CR3: 0000000241baa000 CR4: 00000000003506f02025-06-09T02:08:37+02:00 NASty kernel: Call Trace:2025-06-09T02:08:37+02:00 NASty kernel: <TASK>2025-06-09T02:08:37+02:00 NASty kernel: ? __pfx_flush_tlb_func+0x10/0x102025-06-09T02:08:37+02:00 NASty kernel: on_each_cpu_cond_mask+0x42/0x702025-06-09T02:08:37+02:00 NASty kernel: ? __pfx_flush_tlb_func+0x10/0x102025-06-09T02:08:37+02:00 NASty kernel: __flush_tlb_multi+0x5/0x102025-06-09T02:08:37+02:00 NASty kernel: flush_tlb_mm_range+0xec/0x1602025-06-09T02:08:37+02:00 NASty kernel: tlb_flush_mmu_tlbonly+0x70/0x802025-06-09T02:08:37+02:00 NASty kernel: tlb_flush_mmu+0x15/0xf02025-06-09T02:08:37+02:00 NASty kernel: tlb_finish_mmu+0x2c/0x602025-06-09T02:08:37+02:00 NASty kernel: vms_clear_ptes.part.0+0xc9/0x1002025-06-09T02:08:37+02:00 NASty kernel: vms_complete_munmap_vmas+0x97/0x1702025-06-09T02:08:37+02:00 NASty kernel: do_vmi_align_munmap+0x15c/0x1a02025-06-09T02:08:37+02:00 NASty kernel: do_vmi_munmap+0x13e/0x1502025-06-09T02:08:37+02:00 NASty kernel: __vm_munmap+0x92/0xd02025-06-09T02:08:37+02:00 NASty kernel: __x64_sys_munmap+0x17/0x202025-06-09T02:08:37+02:00 NASty kernel: do_syscall_64+0x68/0xe02025-06-09T02:08:37+02:00 NASty kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e2025-06-09T02:08:37+02:00 NASty kernel: RIP: 0033:0x145aa26856c32025-06-09T02:08:37+02:00 NASty kernel: Code: b8 ca 00 00 00 be 01 00 00 00 ba ff ff ff 7f 0f 05 9b c3 48 89 fe bf 02 10 00 00 b8 9e 00 00 00 0f 05 c3 b8 0b 00 00 00 0f 05 <48> 31 ff b8 3c 00 00 00 0f 05 cc cc cc 31 c0 b0 38 49 89 fb 48 892025-06-09T02:08:37+02:00 NASty kernel: RSP: 002b:0000145a8f964fc8 EFLAGS: 00000246 ORIG_RAX: 000000000000000b2025-06-09T02:08:37+02:00 NASty kernel: RAX: ffffffffffffffda RBX: 0000145a8f965b38 RCX: 0000145aa26856c32025-06-09T02:08:37+02:00 NASty kernel: RDX: 0000145a8f964fd0 RSI: 0000000000203000 RDI: 0000145a8f7630002025-06-09T02:08:37+02:00 NASty kernel: RBP: 0000145a8f965bc0 R08: 0000000000000000 R09: 00000000000000002025-06-09T02:08:37+02:00 NASty kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 00000000000000032025-06-09T02:08:37+02:00 NASty kernel: R13: 0000145a8f9650a8 R14: 0000145a8f965be8 R15: 0000145a8f965b702025-06-09T02:08:37+02:00 NASty kernel: </TASK> unraid-logs.zip
June 9, 20251 yr Community Expert 20 minutes ago, W0nderW0lf said:CROSSHAIR VI HEROSince it's AMD, make sure this has been taken care of:https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173
June 9, 20251 yr Author Thanks for the quick reply!I wonder why I haven't received an email as notification... (I follow that post)BTT:If I understand your post correctly, I have throttle down my clock speed for my RAM? I currently have 2x 3200 MHz 8GB RAM. For my CPU to work properly, I have to lower the speed to ~2400, right?My current CPU is an Ryzen 7 x1700.Would be bummer, but at least it would run for a while, until I have my new system running.edit:Forgot to mention disabling the c-states .. Seems like I really have to turn against ryzen :( Edited June 10, 20251 yr by W0nderW0lf
June 10, 20251 yr Community Expert 14 hours ago, W0nderW0lf said:I have to lower the speed to ~2400, right?It will depend on if they are single or dual rank, if you are not sure, you can post the diagnostics.
June 15, 20251 yr Author Hey @JorgeBI just wanted to mention that you provided the solution. It seems I had to adjust my power management settings for my ryzen and the clockspeed for my RAM...I wondered because it worked for years without issues. It just stopped working properly after adding 2 more disks...Maybe that's the reason the CPU didn't work that well..
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.