June 1, 20242 yr Hello, not sure what diags or info is required here, will grab whatever is needed. Here's the scenario, I downsized rigs and moved before I could test the drives/config in the new rig. 6 disks, single parity. New box is up and running, config and settings in general seem intact. - Immediately got an error on disk 3 (13TB WD white label shuck). "DEVICE IS DISABLED, CONTENTS EMULATED". Would not even get through an extended SMART test. Swapped bays, the error followed the drive. - I took disk 5 (14TB WD white label shuck), did a new config and put it in disk 3's spot. - Started array, parity rebuild starts, first time got to ~20% after ~18 hours. Slowed to double digit KB/sec. - 5 CPU threads pegged at 100% - Unable to pause/cancel rebuild - Force rebooted machine - Started array, parity rebuild starts again, got to 4.2%, now "running" at 604 KB/sec. 5 CPU threads pegged at 100% (including threads 16 and 18... but there are only threads 0-15 available (14700k). Unable to pause/cancel parity check again.
June 1, 20242 yr Author 1 hour ago, rjdipcord said: Whats the SMART status of the "new" drive? Short test completed without error. Extended test running now.
June 1, 20242 yr Community Expert You should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs.
June 1, 20242 yr Author 12 hours ago, itimpi said: You should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs. Diags here. I was able to cancel the parity sync, it just took many hours for the command to go through. Extended SMART test did not finish but I don't see a record of it failing. Trying it again now that the CPU isn't pegged. unraidbr-diagnostics-20240601-1356.zip
June 3, 20242 yr Community Expert Start the parity sync and post new diags if there are issues again.
June 3, 20242 yr Author 14 hours ago, JorgeB said: Start the parity sync and post new diags if there are issues again. Ran it again, at the 5 hour mark. Similar results. Went from 20 MB/sec to 180 MB/sec but has since slowed to 350 KB/sec. Diagnostics attached. unraidbr-diagnostics-20240603-1814.zip
June 4, 20242 yr Community Expert Unraid driver crashed, this is almost always a hardware issue, if I understand correctly hardware changed?
June 4, 20242 yr Author @JorgeBcorrect. Z690 mobo, 14700k, 64gb ram. Jonsbo n 3 case. Standard consumer parts. Only outlier there is an m.2 to sata adapter card, but I have not heard of that causing driver/crashing issues.
June 4, 20242 yr Community Expert If it's a hardware, this type of issue, is usually CPU/board/RAM related.
June 7, 20242 yr Author @JorgeB fresh diags. Ran memtest and pc would crash, replaced ram and it works now. Thoughts? unraidbr-diagnostics-20240606-2348.zip
June 7, 20242 yr Community Expert Try a parity since again with just one stick of RAM, if the same try the other one, that will basically rule out the RAM.
June 8, 20242 yr Author @JorgeB So memtest completes with 0 errors with both new sticks, but I reran parity attempt twice. Once with stick A in slot A and once with stick B in slot A. It doesn't seem RAM related to me at this point but let me know what you think. ram stick B in slot A.zip ram stick A in slot A.zip
June 8, 20242 yr Community Expert Looks like RAM is not the problem, unlikely that there would be two bad sticks, I would recommend downgrading to 6.11.5 and re-test, although rare, there are some cases where this issue can be caused by a kernel compatibility problem with the board, if it's the same with v6.11, then board or CPU would be the next suspects.
June 8, 20242 yr Author @JorgeBI will try that. I'm using an m.2 SATA expansion card. I haven't noticed any issues, and the drives all show up fine in Unraid, but have you known those to cause issues?
June 8, 20242 yr Community Expert Not that error, that's usually board/CPU/RAM or is some rare cases kernel compatibility.
June 9, 20242 yr Author @JorgeB new diags. I rolled it back to 6.11.3 because that was readily available in the GUI... It ran at 200MB/sec+ for nearly 4 hours before crashing to a much higher floor of 1.3 MB/sec... I'm going to make sure BIOS is updated.
June 9, 20242 yr Community Expert Unraid driver is still crashing, suggesting it's not a kernel compatibility issue, so it will be a hardware problem.
July 26, 20241 yr Author Solution I ended up buying an identical motherboard and CPU to test. The old CPU was bad (and the new motherboard was bad). Not sure exactly what the issue was, but it was CPU related.
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.