MrYoshii

Members
  • Posts

    106
  • Joined

  • Last visited

Everything posted by MrYoshii

  1. 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.
  2. 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.
  3. okok but why did it shutdown unclean? I just kicked shutdown in the GUI and waited until the system turned off.
  4. 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?
  5. 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
  6. 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.
  7. 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.
  8. 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?
  9. 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.
  10. Is there a way to auto shutdown the server after parity check?
  11. 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.
  12. 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
  13. Ok so I did a rerun and I got this? On the notification it says 2 errors and in the main tap it says 0 errors? It also shows different Durations and speed? Also this is the Notification on telegram: HomeServer01: Notice [HOMESERVER01] - Parity-Check finished (2 errors) Unraid Parity-Check Notice [HOMESERVER01] - Parity-Check finished (2 errors) Duration: 21 hours, 6 minutes, 42 seconds. Average speed: 105.3 MB/s homeserver01-diagnostics-20230608-1529.zip
  14. oh damn I missed that setting in the scheduling tap. I'm now doing the correcting check and I will keep you posted.
  15. Hi, I got monthly Parity Syncs going and last time I was seeing the error. I did ignore it because I was not sure if I got an unsafe shutdown. But now there are two errors again. Maybe someone knows what's up with that? homeserver01-diagnostics-20230602-2358.zip
  16. Hi i just fresh installed unraid 6.11.5. I got 2 drives 8TB. XFS formatted. I'm transferring now my files on the array and i get a lot of errors in log. Feb 11 13:05:00 HomeServer01 smbd[23836]: [2023/02/11 13:05:00.071252, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) Feb 11 13:05:00 HomeServer01 smbd[23836]: synthetic_pathref: opening [path/to/file/file.pdf] failed it's not only pdf files. Unfortunately, i can not share the log because of sensitive file names and co. What's up with that? it already uses 81% of the log space...
  17. Have now set this to Adaptec. Unfortunately without success
  18. The system keeps showing drive usage like this even though nothing is being done to the system.
  19. its just in passthrug mode so i can use my 24 bay case. I have already reinstalled unraid. I have no containers running and only 1 vm which is only at the cache. It was also when no plugins were installed. The hard drives also go down after 1h inactivated but do not stay there for long.
  20. I have just jellyfin and íts stopped. this is because I reinstalled unraid and have not yet adjusted this.
  21. Hello currently I have the problem that my drives just do not stay in standby. They go off automatically but do not stay for long. I have reinstalled Unraid. Currently I have only 1 VM on the cache. Plugins: Community Applications Dynamix System Temperature GPU Statistics Nerd Tools Nvidia Driver Does anyone else have an idea what can be wrong with it? homeserver-diagnostics-20220822-1858.zip