die3zehn

so after testing a while now with only one kit installed it seems to be running. I think one of the RAM modules was not working correctly. Memtest was showing no errors but whenever I added this module the server crashed after a while. I returned this kit. Guess this thread can be closed now. Thanks a lot for your support JorgeB

after getting crashes even with those settings I then moved the USB flash drive to another USB port as I saw I have it on a USB3.1 port instead of USB2.0 Still got a crash while copying data. Now I removed 3 RAM modules and just left one in. I could copy my data without a crash of Krusader or the system. So everything which caused a crash before went through so far. I'm using 2 16GB Kits of 2x8GB RAM and I read somewhere that this might cause issues as both kits are not tested together. Or maybe I just mixed the modules and put them in the "wrong" slot as the kit pairs should be in A2 & B2 and A1 & B1. Will try that out as well and put them back one after the other to see if I get some more crashes. Just hope that this is really the root cause of my issues. Will report back my experience after testing. Any idea how long I should run the server with the different combinations of RAM to get a rough idea if it is stable or not?

thanks JorgeB I did set it to "Typical Current Idle", just double checked. Will now set the "Global C-State Control" to disabled as well and test it again

tried it over night, got a kernel panic after some cpuidle_enter_state messages. Couldn't take any diag file, just saw it on the screen connected to the server. Could this be RAM related as well? I read that memtest isn't that reliable. Would now try it with one RAM at a time to see if one of them is causing issues. Although most of the error messages show some CPU issues. Maybe I should just accept that unraid and my HW setup just don't work together.....

not sure if this is still due to using a Ryzen CPU as it seems that some cores tend to run at 100% after they stop working. Happening still during file transfers, no longer using Krusader although now SMB seems to crash and the only thing working is a manual reboot pushing the reset button. diags attached mittelerde-diagnostics-20200913-1004.zip

just saw that 2 CPUs have 100% load since krusader stopped working while copying files from an external USB drive. Diag attached mittelerde-diagnostics-20200911-1858.zip

don't have it from the time of the high cpu load. Got one from last evening and I can pull one now if that helps Next time I try to remember to pull one

Stable version didn't really made a difference unfortunately. MSI released a new bios which contains "Updated AMD AGESA ComboAm4v2PI 1.0.8.1" and some improvements to S3 wake up issues. Testing it since yesterday. Parity check went through over night, server has been up for 17 hours without a crash 😀. Although I had a CPU load of 90 - 100% when I checked this morning. WebUI was very slow due to the cpu load. Not sure what caused the load as nothing was actively running at that moment. Attached the syslog from this morning. mittelerde-syslog-20200911-0714.zip

tested the server without the SATA card, same issue. Another "Kernel panc - not syncing: Attempted to kill the idle task! Shutting down cpus with NMI" Anyone another idea? Guess using the stable version is no option as the Kernel is even older?

attached the complete diags while server was running. In the meantime it crashed again. Unfortunately I don't have a syslog file after that. Just saw a kernel panic on the screen. Was just running parity. mittelerde-diagnostics-20200909-1410.zip

updated bios, will test for some time again. do you think the additional SATA card causes issues?

thanks for the reply. RAM is currently running at 2400

hello community, did set up my first unraid server on mostly new HW some days back and keep on getting server crashes during parity checks or copying data from an USB device to the disks on the server using krusader. Things I did so far: Did run a memtest without errors just yesterday. Disabled C-states in BIOS no OC (CPU/ RAM) This time I could save the syslog when it crashed, see attached. Also it seems that copying the syslog file to the flash drive doesn't work. At least that is my interpretation on Sep 9 09:10:07 Mittelerde rsyslogd: Could not find template 1 'flash' - action disabled [v8.2002.0 try https://www.rsyslog.com/e/3003 ] Sep 9 09:10:07 Mittelerde rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 66: errors occured in file '/etc/rsyslog.conf' around line 66 [v8.2002.0 try https://www.rsyslog.com/e/2207 ] I'm not using a cache drive at the moment as I first wanted to upload all data. HW specs: MSI x570 Tomahawk AMD Ryzen 7 3700x MSI GT 710 4x8GB HyperX Fury RAM Ziyituod PCIe SATA 4 port card 4x WD Red 3TB (used) 4x WD Blue 1TB (used) ADATA XPG SX8200 Pro 512GB 1x Crucial 128GB SSD (used) No VMs I'm using the beta version as it enables the onboard network (as far as I read in the forum). Hope someone can help me finding the root cause of the crashes or has suggestions to improve the setup syslog_20200909-1119.zip