Omega666 Posted February 9, 2022 Share Posted February 9, 2022 I have a new Unraid system. after about 15 hours of parity check the interface freezes, the nas can no longer be reached via png, http or otherwise. i have set up a syslog so that i have log files. i have already replaced the USB stick with a new one. I need help urgently, it is my productive NAs with 26TB of data. it helps only a cold power off. I have attached the syslog log and the diagnostiv file. Bios is up to date. syslog.zipmothership-diagnostics-20220209-1227.zip Quote Link to comment
Solution JorgeB Posted February 9, 2022 Solution Share Posted February 9, 2022 Uninstall de corefeq plugin. Quote Link to comment
Omega666 Posted February 9, 2022 Author Share Posted February 9, 2022 Is this a general recommendation or did you see something in the logs? Thanks for the help Quote Link to comment
JorgeB Posted February 9, 2022 Share Posted February 9, 2022 There's a crash related to it: 2022-02-09T11:50:27+00:00 Mothership kernel: Call Trace: 2022-02-09T11:50:27+00:00 Mothership kernel: <IRQ> 2022-02-09T11:50:27+00:00 Mothership kernel: queued_spin_lock_slowpath+0x7/0xa 2022-02-09T11:50:27+00:00 Mothership kernel: nr_blockdev_pages+0x13/0x64 2022-02-09T11:50:27+00:00 Mothership kernel: si_meminfo+0x3a/0x57 2022-02-09T11:50:27+00:00 Mothership kernel: Sys_MemInfo+0x20/0x9b [corefreqk] 2022-02-09T11:50:27+00:00 Mothership kernel: ? paravirt_sched_clock+0x5/0x8 2022-02-09T11:50:27+00:00 Mothership kernel: ? timekeeping_get_ns+0x19/0x2f 2022-02-09T11:50:27+00:00 Mothership kernel: ? Sys_DumpTask+0xe9/0xf1 [corefreqk] 2022-02-09T11:50:27+00:00 Mothership kernel: Cycle_Skylake+0x53a/0x730 [corefreqk] 2022-02-09T11:50:27+00:00 Mothership kernel: __hrtimer_run_queues+0xb7/0x10b 2022-02-09T11:50:27+00:00 Mothership kernel: ? Cycle_Skylake_X+0x711/0x711 [corefreqk] 2022-02-09T11:50:27+00:00 Mothership kernel: hrtimer_interrupt+0x8d/0x15b 2022-02-09T11:50:27+00:00 Mothership kernel: __sysvec_apic_timer_interrupt+0x5d/0x68 2022-02-09T11:50:27+00:00 Mothership kernel: asm_call_irq_on_stack+0xf/0x20 2022-02-09T11:50:27+00:00 Mothership kernel: </IRQ> 2022-02-09T11:50:27+00:00 Mothership kernel: sysvec_apic_timer_interrupt+0x71/0x95 2022-02-09T11:50:27+00:00 Mothership kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 2022-02-09T11:50:27+00:00 Mothership kernel: RIP: 0010:nr_blockdev_pages+0x4c/0x64 Also it's a common issue. 1 Quote Link to comment
Omega666 Posted February 9, 2022 Author Share Posted February 9, 2022 Thank you very much. That sounds good. I have removed the plugin. I also have a new CPU i5 11600T here because I want to use the second NVMe slot of my board, The question is, swap the CPU now, do parity check or do parity check first and then swap. General recommendation? Quote Link to comment
JorgeB Posted February 9, 2022 Share Posted February 9, 2022 9 minutes ago, Omega666 said: General recommendation? Shouldn't make much difference, but I would swap before. Quote Link to comment
Omega666 Posted February 10, 2022 Author Share Posted February 10, 2022 My server has been running stable for 24 hours. Apparently it was really the plugin. My perity check has also gone through now and I have successfully upgraded the server to the i5 11600T and am very happy with the results. Also my cache is now running with 1TB Raid 1. Thanks for the help. 1 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.