aJmJuZyip4tZ5n

I do have a recent log of the crash (it's near the end with a spoiler). Given what it recorded, and what I've google, looks like a hardware issue. I've recently turned off XMP (RAM speed is sitting at 1366 Mhz) and disabled c-states (not sure if this matters for intel based CPUs). Just finished the 1 day and half of parity rebuilding without a crash! Hopefully this is stable now, I'll update if it crashes again.

This is my second time writing this late at night due to the first post not going through System SPECS: MSI Z87-G45 GAMING (MS-7821) , Version 1.0 Intel® Core™ i7-4770K CPU @ 3.50GHz Memory: 32 GiB DDR3 NO GPU Unraid Version: 6.12.4 Plugins: Community Applications Unassigned Devices Unassigned Devices Plus Unassigned Devices support for HFS+, exFAT, and apfs disk formats, and enabling destructive mode. Unassigned Devices Preclear My use case for unraid is to: 1) use as a NAS and run Docker containers to grab files using the -arr Apps 2) This is strictly a file server that downloads and shares across the network 3) No Plex or other mediaservers are running on this machine, and no VMs either There is a single issue where my server crashes. It has occured when it's running Docker containers and when nothing is running other than a parity sync. I'm unsure of whether is a hardware issue, software, software compatability. Issue 1: I have come across the issue of my server consistently crashing at least once a day. When running the following Docker containers, When the crashes occur, a single cpu core is stuck on 100% utilization on the webgui. I'm unable to stop the array, shutdown or reboot the server. I've tried running the terminal commands as root and the system just hangs. When I check what is running with htop, no processes appear stuck. When this occurs, I'm always forced to do a physical restart. Once I do that, the system chugs alongs for less than a day. This issue still hasn't been diagnosed yet. Issue 2: I recently purchased a 20TB drive to use to build my parity. I wanted this process to go smoothly because it takes 1 day and half to do the parity sync. I've restarted my system and turned off Docker Containers and Disable Docker. I've been through this process twice and the last one was very close to finishing, but crashed at 99.80%. There was only 40min left on the sync!! I'm incredibly frustrated and am seeking help from knowledgeable members. During the rebuild process the CPU sits between 3-10% The first time it crashed, I ran htop and there was a process with the CMD: ``` sh -c /sbin/udevadm test-builtin usb_id /devices/pci000:00/0000... ``` pinned at 100% cpu utilization I've ran a memtest86 and no errors came back: I recently found out how to log syslog for crashes and was only able to capture the recent crash of my parity build: I have also attached my diagnostics data. I appreciate any help I can get with understanding this issue. I know the hardware is old, but it ran as my windows machine without any crashes before I've turned it to an Unraid server. EDIT: MOBO Supported Memory Speeds: I've been reading a bit and it seems like memory speed could be an issue? I was running at 1866MHz, even thought my Mobo supports it, I have now moved it down to 1333MHz and I'll see how that goes bee-diagnostics-20231021-0221.zip