Hello,

I've been having some trouble with my unraid server. A while ago I had a hard crash while messing with a vm and everything seemed borked afterward. One of the array drives was marked disabled after booting and I replaced it with a drive I was about to add to the array. Was fine for a couple days. But then the drive appeared disabled again. Now every time I run the rebuild around 36% it gets stuck and the speed keeps reducing. Last night was the 2nd time its done this. When it's in this state the pause doesn't do anything, and if I hit reboot it just hangs on the "rebooting..." page powered on. All the SMART data looks fine, and I've tried different SATA ports/cables. Any idea what is happening here? Do the BTRFS errors in logs mean anything? Thanks for any help in advance.

Also I am pretty out of date. Was hoping to stabilize then update the OS and move cache/vms to that 2tb nvme and retire the other SSDs.

Edit: I should add it's still currently going. I don't hear the drives spinning up at all and CPU/RAM usage is similar to idle.

Also possible related. Docker keeps getting corrupted. It'll be fine a few days then service fails to stop and I delete docker.img and let it rebuild. Currently have it disabled while figuring this out.

Edited January 13Jan 13 by MacDreidel
Extra info

Unraid driver crashed, this is almost always a hardware problem. Start by looking here and making any applicable adjustments:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

Ahh thank you. Bios was a few years out of date, so that's updated and set "Power Supply Idle Control" to "typical current idle". I haven't overclocked the RAM. It's been pretty stable generally, but does seem to crash/lose connection after a month or so up.

So try another rebuild and it should hopefully go through now? Was there something in the diagnostics that pointed the unraid driver crashing out?

10 hours ago, MacDreidel said:

Was there something in the diagnostics that pointed the unraid driver crashing out?

Yes, it showed the actual crash.

1 hour ago, JorgeB said:

Yes, it showed the actual crash.

Yes, can you elaborate on what to look for in the logs? Nothing stood out to me.

Always random issues with this setup. I think I'll go ahead and do a rebuild around another system. Just want to verify this is an OS level issue and not some hidden problem with any of the drives.

Edited January 12Jan 12 by MacDreidel

md_mod is the unRAID driver

Jan 10 02:25:39 Tower kernel: general protection fault, probably for non-canonical address 0xca332d4ec4f963e0: 0000 [#1] PREEMPT SMP NOPTI

Jan 10 02:25:39 Tower kernel: CPU: 0 PID: 12500 Comm: unraidd0 Tainted: P O 6.1.118-Unraid #1

Jan 10 02:25:39 Tower kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B85/B450 GAMING PRO CARBON AC (MS-7B85), BIOS 1.G1 06/27/2022

Jan 10 02:25:39 Tower kernel: RIP: 0010:copy_data+0x16/0x219 [md_mod]

Jan 10 02:25:39 Tower kernel: Code: c4 d8 00 00 00 5b 5d 41 5c 41 5d 41 5e 41 5f e9 b1 87 68 e1 0f 1f 44 00 00 41 57 48 89 f0 41 56 41 55 41 54 55 53 48 83 ec 40 <48> 8b 5e 20 89 7c 24 14 48 89 54 24 18 48 39 cb 72 07 29 cb c1 e3

Jan 10 02:25:39 Tower kernel: RSP: 0018:ffffc900047f3d78 EFLAGS: 00010286

Jan 10 02:25:39 Tower kernel: RAX: ca332d4ec4f963c0 RBX: ffff88815006b348 RCX: 0000000252c7a040

Jan 10 02:25:39 Tower kernel: RDX: ffff88814a524000 RSI: ca332d4ec4f963c0 RDI: 0000000000000000

Jan 10 02:25:39 Tower kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffffc900047f3d58

Jan 10 02:25:39 Tower kernel: R10: 0000000000000000 R11: 0000000000000002 R12: 0000000000000004

Jan 10 02:25:39 Tower kernel: R13: 0000000000000002 R14: 00000000ffffffff R15: 0000000000000001

Jan 10 02:25:39 Tower kernel: FS: 0000000000000000(0000) GS:ffff888ffe800000(0000) knlGS:0000000000000000

Jan 10 02:25:39 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Jan 10 02:25:39 Tower kernel: CR2: 000014ddee76169c CR3: 0000000104b0c000 CR4: 0000000000350ef0

Jan 10 02:25:39 Tower kernel: Call Trace:

Jan 10 02:25:39 Tower kernel: <TASK>

Jan 10 02:25:39 Tower kernel: ? __die_body+0x1a/0x5c

Jan 10 02:25:39 Tower kernel: ? die_addr+0x38/0x51

Jan 10 02:25:39 Tower kernel: ? exc_general_protection+0x30f/0x345

Jan 10 02:25:39 Tower kernel: ? asm_exc_general_protection+0x22/0x30

Jan 10 02:25:39 Tower kernel: ? copy_data+0x16/0x219 [md_mod]

Jan 10 02:25:39 Tower kernel: ? srso_return_thunk+0x5/0x10

Jan 10 02:25:39 Tower kernel: unraidd+0x51a/0x1140 [md_mod]

Jan 10 02:25:39 Tower kernel: md_thread+0xf7/0x122 [md_mod]

Jan 10 02:25:39 Tower kernel: ? rawspin_rq_lock_irqsave+0x20/0x20

Jan 10 02:25:39 Tower kernel: ? signal_pending+0x1d/0x1d [md_mod]

Jan 10 02:25:39 Tower kernel: kthread+0xe7/0xef

Jan 10 02:25:39 Tower kernel: ? kthread_complete_and_exit+0x1b/0x1b

Jan 10 02:25:39 Tower kernel: ret_from_fork+0x22/0x30

Jan 10 02:25:39 Tower kernel: </TASK>

Jan 10 02:25:39 Tower kernel: Modules linked in: xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc bonding tls edac_mce_amd edac_core intel_rapl_msr intel_rapl_common iosf_mbi kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 btusb aesni_intel btrtl btbcm crypto_simd btintel cryptd input_leds wmi_bmof rapl igb bluetooth joydev led_class nvme ecdh_generic i2c_piix4 i2c_algo_bit ecc k10temp ccp ahci i2c_core nvme_core libahci wmi tpm_crb tpm_tis tpm_tis_core tpm button acpi_cpufreq unix

Jan 10 02:25:39 Tower kernel: ---[ end trace 0000000000000000 ]---