Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Parity check grinds to a halt at a few percent.

Featured Replies

My NAS seems to be suffering an issue. The parity check after a reboot gets stuck at a few percent and tells me is has a thousand days to finish.

No other problems that I can see.

Regards

Iain .

sol-diagnostics-20260114-1216.zip

Solved by JorgeB

  • Community Expert
  • Solution

Unraid driver is crashing; this is almost always a hardware issue. You can start by running Memtest, but I see you have a 14900K, so most likely the Intel 13/14 gen issue; a BIOS update may help if the CPU isn't too far gone.

  • Author

Ok. Firstly, where do you see that the driver crashed - so I can learn to spot problems myself - the diagnostic data is a little overwhelming…

Secondly, do I need to do the memtest and bios update outside of the unraid environment?

I’m still learning about the hardware side of things - despite having been a desktop programmer for 30 years…

Thanks,

Iain.

  • Community Expert
2 hours ago, Iain Hodge said:

Firstly, where do you see that the driver crashed

In the syslog, md_mod is the unRAID driver:

Jan 14 01:23:37 Sol kernel: ------------[ cut here ]------------

Jan 14 01:23:37 Sol kernel: kernel BUG at drivers/md/unraid.c:1617!

Jan 14 01:23:37 Sol kernel: Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI

Jan 14 01:23:37 Sol kernel: CPU: 9 UID: 0 PID: 7633 Comm: unraidd0 Tainted: P U O 6.12.54-Unraid #1

Jan 14 01:23:37 Sol kernel: Tainted: [P]=PROPRIETARY_MODULE, [U]=USER, [O]=OOT_MODULE

Jan 14 01:23:37 Sol kernel: Hardware name: CWWK CW-Q670-NAS/CW-Q670-NAS, BIOS 5.27 05/13/2024

Jan 14 01:23:37 Sol kernel: RIP: 0010:unraidd+0x12d1/0x13d0 [md_mod]

Jan 14 01:23:37 Sol kernel: Code: 83 3d d6 31 00 00 03 7e 17 41 8b 57 98 44 89 e1 48 c7 c7 c1 63 56 a1 48 8b 73 20 e8 39 d3 5e e0 41 f6 87 69 ff ff ff 02 75 02 <0f> 0b 48 8b 43 20 49 03 46 18 41 c7 47 b0 00 10 00 00 49 8b 57 10

Jan 14 01:23:37 Sol kernel: RSP: 0018:ffffc90001a97d80 EFLAGS: 00010246

Jan 14 01:23:37 Sol kernel: RAX: 0000000000000000 RBX: ffff88819effa550 RCX: 0000000000000000

Jan 14 01:23:37 Sol kernel: RDX: 0000000000000000 RSI: ffffffff83063fe0 RDI: ffff88810267c838

Jan 14 01:23:37 Sol kernel: RBP: ffffc90001a97e90 R08: 0000000000000000 R09: 0000000000000000

Jan 14 01:23:37 Sol kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001

Jan 14 01:23:37 Sol kernel: R13: ffff88819effa540 R14: ffff888107c752e8 R15: ffff88819effa7c0

Jan 14 01:23:37 Sol kernel: FS: 0000000000000000(0000) GS:ffff888c4f640000(0000) knlGS:0000000000000000

Jan 14 01:23:37 Sol kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Jan 14 01:23:37 Sol kernel: CR2: 000000c002407010 CR3: 0000000005618003 CR4: 0000000000772ef0

Jan 14 01:23:37 Sol kernel: PKRU: 55555554

Jan 14 01:23:37 Sol kernel: Call Trace:

Jan 14 01:23:37 Sol kernel: <TASK>

Jan 14 01:23:37 Sol kernel: ? preempt_latency_start+0x2b/0x50

Jan 14 01:23:37 Sol kernel: ? md_thread+0xf1/0x120 [md_mod]

Jan 14 01:23:37 Sol kernel: ? kthread_should_park+0x12/0x30

Jan 14 01:23:37 Sol kernel: md_thread+0xf1/0x120 [md_mod]

Jan 14 01:23:37 Sol kernel: ? __pfx_autoremove_wake_function+0x10/0x10

Jan 14 01:23:37 Sol kernel: ? __pfx_md_thread+0x10/0x10 [md_mod]

Jan 14 01:23:37 Sol kernel: kthread+0xec/0x100

Jan 14 01:23:37 Sol kernel: ? __pfx_kthread+0x10/0x10

Jan 14 01:23:37 Sol kernel: ret_from_fork+0x21/0x40

Jan 14 01:23:37 Sol kernel: ? __pfx_kthread+0x10/0x10

Jan 14 01:23:37 Sol kernel: ret_from_fork_asm+0x1a/0x30

Jan 14 01:23:37 Sol kernel: </TASK>

Jan 14 01:23:37 Sol kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net vhost vhost_iotlb tap br_netfilter xt_conntrack xfrm_user xfrm_algo xt_addrtype xt_MASQUERADE xt_tcpudp xt_mark tun nf_tables nfnetlink ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nfsd auth_rpcgss lockd grace sunrpc md_mod zfs(PO) spl(O) ntfs3 tcp_diag inet_diag i915(O) intel_gtt ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls igc led_class intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel xe kvm drm_gpuvm drm_exec gpu_sched drm_buddy crct10dif_pclmul drm_ttm_helper crc32_pclmul crc32c_intel ghash_clmulni_intel ttm sha512_ssse3 sha256_ssse3 i2c_algo_bit sha1_ssse3 drm_suballoc_helper aesni_intel drm_display_helper crypto_simd cryptd rapl intel_cstate drm_kms_helper mei_hdcp mei_pxp drm wmi_bmof intel_uncore mei_me i2c_i801 tpm_crb i2c_smbus agpgart apex(O) mei tpm_tis i2c_core gasket(O)

Jan 14 01:23:37 Sol kernel: tpm_tis_core thermal fan tpm video wmi libaescfb ecdh_generic backlight ecc acpi_tad acpi_pad button [last unloaded: led_class]

Jan 14 01:23:37 Sol kernel: ---[ end trace 0000000000000000 ]---

Memtest is an option in the Unraid boot menu, for the BIOS updater, most boards have a flash utility where you can do it from a flash drive.

  • Author

OK - I think it was a RAM seating error - I shutdown and ran MemTest86+ on the system.

After 2 passed I had 6 errors coming up so I shutdown and removed on stick of RAM.

MemTest86+ then ran overnight with NO errors in 13 passes.

I then swapped the sticks of RAM and reran the meatiest.

Again. no errors across multiple passes.

So I put both sticks back in and tried again - this time 13 passes of memtest showed no errors.

I fired up UnRaid again and seemed to get no matching errors so I think I can resolve this one.

I have lots of other errors which I'd better raise different threads for.

Thanks for your help

Iain.

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.