If it were hardware failing, I would expect the hang to be in various locations, various offsets, but 24 times at the same offset? That seems suspicious, no?

10 hours ago, LumberJackGeek said:

I see them in the diagnostic, check this file here:

I meant the diags posted, not all those individual files, there's no chance for me to be going through all of them. Please just post that file

Panic#2 Part3

<6>BTRFS info (device loop2): first mount of filesystem fd9bd8af-d3b4-4fec-a4d8-55e7b9dff8b7

<6>BTRFS info (device loop2): using crc32c (crc32c-lib) checksum algorithm

<6>BTRFS info (device loop2): turning on async discard

<6>BTRFS info (device loop2): enabling free space tree

<4>kvm: Running KVM with ignore_msrs=1 and report_ignored_msrs=0 is not a

<4>a supported configuration. Lying to the guest about the existence of MSRs

<4>may cause the guest operating system to hang or produce errors. If a guest

<4>does not run without ignore_msrs=1, please report it to [email protected].

<4>mdcmd (36): check

<4>md: recovery thread: recon D4 ...

<4>------------[ cut here ]------------

<2>kernel BUG at drivers/md/unraid.c:1622!

<4>Oops: invalid opcode: 0000 [#1] SMP NOPTI

<4>CPU: 15 UID: 0 PID: 18261 Comm: mdunraidd0 Tainted: P O 6.18.33-Unraid #1 PREEMPT(voluntary)

<4>Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE

<4>Hardware name: ASUS System Product Name/ROG MAXIMUS Z690 HERO, BIOS 4001 10/07/2024

<4>RIP: 0010:unraidd+0x12ce/0x13d0 [md_mod]

<4>Code: 83 3d b9 70 3a 06 03 7e 17 41 8b 57 98 48 8b 73 20 44 89 e1 48 c7 c7 21 63 43 a8 e8 1c ea 20 df 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 89 47 a8

<4>RSP: 0018:ffffc900055cfd30 EFLAGS: 00010246

<4>RAX: 0000000000000000 RBX: ffff88812483c9b0 RCX: 0000000000000000

<4>RDX: 0000000000000000 RSI: ffffffff8335f240 RDI: ffff888101c6a038

<4>RBP: ffffc900055cfe40 R08: 0000000000000000 R09: 0000000000000000

<4>R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002

<4>R13: ffff88812483c9a0 R14: ffff88811d74d3b0 R15: ffff88812483ccd0

Replaced motherboard today, still happening.

9 hours ago, LumberJackGeek said:

<4>md: recovery thread: recon D4 ...

<4>------------[ cut here ]------------

<2>kernel BUG at drivers/md/unraid.c:1622!

<4>Oops: invalid opcode: 0000 [#1] SMP NOPTI

Do you have the time codes? It would be good to see how long the crash happens after the rebuild start, if it always immediate or just a couple of seconds; I would no longer consider it a hardware issue. If you enabled the syslog server it should have that, as long as keep it all in a single file, where there could be multiple crashes logged for comparison.

My suggestion for now, to see if there's really a specific issue when trying to rebuild that disk, would be to copy all the data from the emulated disk to the actual disk, then do a new config and resync parity, and see if that doesn't crash.

Can post more detailed instructions if needed.

Well i got it to rebuild the drive, and then when i did, i rebooted and it tried saying the disk was the old one again, so i did the new config and have been trying to resync parity for the last week but it's been hanging again trying to do so. i have shared multiple rounds of diagnostics, if what i have shared is not enough, please let me know what is enough? exact steps of what you are looking for would be appreciated. how confident are you that this is not a hardware problem anymore?

it hangs in a variety of places, sometimes it hangs during safe mode, sometimes it hangs before bringing the array online, but more often than not it hangs doing the parity computation. it can hang 10 minutes into it, or 10 hours later, there's no time duration or % pattern that i have noticed.

Edited 9 hours ago9 hr by LumberJackGeek

PS, i replaced the CPU today, but it sounds like that might have been unnecessary...?

The only thing I've asked for was the persistent sylog from the syslog server after the issue occurs; see the link for how to enable that and set it to be saved to a share, then post that, it will log the time codes.