MrYoshii

Hi, I'm trying to reduce power consumption on my system. I don't get below C1 and C2. If already stopped all docker and VMs. Also, I used power top auto-tune. Also enabled power safe via tips and tweaks. I notice that the CPU load is bumpy. Also the load is always over 1. Why is that happening all the time? All drives are spun down, and I am not doing anything with the server. Thanks for any hint.

thanks, I think it works now.

oh, sry i did misunderstand that. the last log is already here. Its that one if made. But there is one from the shutdown time to. Its a bit earlier than the time stamp you posted.

okok but why did it shutdown unclean? I just kicked shutdown in the GUI and waited until the system turned off.

Where will you see that?

If got a backup unraid server that i auto start just for a backup. But every time it boots up, it also starts a parity check?? It makes no difference if i use the GUI or the command powerdown. And i also have this problem with my main server two. I just used the GUI to shut down the system and after i turned it back on it started a check. I'm running the latest unraid version on both systems. What's up with that?

Hi im not sure what im missing.. i have run the updatet script but still getting the error #!/bin/bash # Write XMRig Optimised MSR values # https://github.com/xmrig/xmrig/blob/master/scripts/randomx_boost.sh VERSION=1.3 echo "Installing msr-tools v${VERSION}" echo "" echo "(don't!) blame lnxd if something goes wrong" echo "" curl -fsSL https://packages.slackonly.com/pub/packages/14.2-x86_64/system/msr-tools/msr-tools-${VERSION}-x86_64-1_slonly.txz -o /tmp/msr-tools-${VERSION}-x86_64-1_slonly.txz upgradepkg --install-new /tmp/msr-tools-${VERSION}-x86_64-1_slonly.txz rm /tmp/msr-tools-${VERSION}-x86_64-1_slonly.txz echo "" echo "Optimising register values for XMRig" echo "" modprobe msr if grep -E 'AMD Ryzen|AMD EPYC' /proc/cpuinfo > /dev/null; then if grep "cpu family[[:space:]]\{1,\}:[[:space:]]25" /proc/cpuinfo > /dev/null; then if grep "model[[:space:]]\{1,\}:[[:space:]]97" /proc/cpuinfo > /dev/null; then echo "Detected Zen4 CPU" wrmsr -a 0xc0011020 0x4400000000000 wrmsr -a 0xc0011021 0x4000000000040 wrmsr -a 0xc0011022 0x8680000401570000 wrmsr -a 0xc001102b 0x2040cc10 echo "MSR register values for Zen4 applied" else echo "Detected Zen3 CPU" wrmsr -a 0xc0011020 0x4480000000000 wrmsr -a 0xc0011021 0x1c000200000040 wrmsr -a 0xc0011022 0xc000000401570000 wrmsr -a 0xc001102b 0x2000cc10 echo "MSR register values for Zen3 applied" fi else echo "Detected Zen1/Zen2 CPU" wrmsr -a 0xc0011020 0 wrmsr -a 0xc0011021 0x40 wrmsr -a 0xc0011022 0x1510000 wrmsr -a 0xc001102b 0x2000cc16 echo "MSR register values for Zen1/Zen2 applied" fi elif grep "Intel" /proc/cpuinfo > /dev/null; then echo "Detected Intel CPU" wrmsr -a 0x1a4 0xf echo "MSR register values for Intel applied" else echo "No supported CPU detected" fi echo "" echo "Done!" echo "To reset values, please reboot your server." [2023-08-11 10:51:48.249] msr msr kernel module is not available [2023-08-11 10:51:48.249] msr FAILED TO APPLY MSR MOD, HASHRATE WILL BE LOW I am running it on a AMD EPYC 7302

okok if switched platform now i got ecc RAM. After the correcting check, i did a another normal check. it finished without an error. Hopefully it doesn't come back with the next check.

ok there were no unclean shutdowns. What could cause this issues? yes, but I got the errors the last time when I started this thread, and they were gone after I used a correcting check and now they are back again.

I don't know why, but yesterday it did an auto check and showed again two sync errors. Now I'm running a correction sync. Should I be worried?

ok yes, thanks for that hint. I think my use case may be very special ^^ I have two unraid servers, the main one is online 24/7 and the second one starts every day for a backup and after that it shuts down again. But on the Backup server I also want to run parity checks, but I don't want to manually think about them, so I would just auto start the server and after the check is done it should shut down itself again.

Is there a way to auto shutdown the server after parity check?

Thanks for the hint. At the moment I just disabled some USB power saving stuff, and It's now up for over 24h. I will update if it crashes again.

I just installed unraid Version: 6.12.2 to Backup my main unraid server. But I can not even go through the initial Parity sync. The monitor randomly turns off, no ping and not even the numlock led changes when I press the button. It's new hardware and it worked with windows. ROG STRIX B550-XE GAMING WIFI AMD Ryzen 5 5600G 32 GiB DDR4 3600Mhz XMP stuff off. I have already tried mirror syslog, but it's not putting anything in. Maybe someone has an idea, or should I just try an older unraid version? backupserver01-diagnostics-20230702-1622.zip syslog-192.168.1.97(2).log

ok thanks