HeNotSatisfied

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

HeNotSatisfied's Achievements

Noob

Noob (1/14)

1

Reputation

1

Community Answers

  1. The problem I found was that as soon as the screen is not connected, dimmed or turned off, this behavior occurs. To fix this, I connected an HDMI dummy to the server (LINK). Then the screen power saving settings need to be disabled. This results in a higher power consumption of approx. 0.5~1.5 W for me. The only way I have found to disable it, which also preserves all hardware functions, is to customize the "GO" file under: /boot/config/go [usb-drive/config/go]. here the first command under #!/bin/bash must be the command /bin/setterm -blank 0 -powersave off -powerdown 0. The file then looks like this for me: #!/bin/bash #fix kworker bug - keep display active /bin/setterm -blank 0 -powersave off -powerdown 0 # Start the Management Utility /usr/local/sbin/emhttp & the system must then be restarted. adjusting the go file alone does not solve the problem, it requires an HDMI dummy or monitor. normally the file "/etc/rc.d/rc.setterm" must be adjusted in Linux Slackware. The lines are already preconfigured and only need to be commented in. See Slackware docs [LINK]. Since unraid creates the /etc/ directory at every start and loads it into RAM, these settings are lost after every restart. you can have the file replaced at every start. but i didn't want to do that and i think it's easier to just write the command in the go-file. go
  2. hi, I have probably found a solution. i will test this further and then post my findings. If this works, all system functions will be retained. See you in three days or so. (I promise) What a journey with a lot of frustration.....
  3. i have found out that the problem only occurs when no monitor is connected. Any ideas?
  4. hey guys, since I'm getting desperate I decided to write a post in the hope that some of you have a few more ideas. Here's the problem: About every 25 seconds a CPU core goes to 100% for about 5 seconds. "top" gives me the information that the "kworker" process is very active during this time. I have already tried all the possible fixes I found in the forum and reddit, rebuilt the whole system several times, tried different hard disks, motherboards and SAS HBAs. There are no plugins, VMs or Docker installed. Once again, I really hope you guys can help me. The following components are installed. CPU: Intel i5 10500 Motherboard: ASRock H510M-HVS R2.0 RAM: 32 GB DDR4 (2x 16 GB Corsair CMK32GX4M2A2666C16) PSU: Corsair RM550x (2021) SAS HBA: Dell PERC H310 hsrv01-diagnostics-20240120-1923.zip
  5. I have the same issues with my server and an "ASRock H510M-HVS R2.0" (Intel). Hard locks every couple of days. I will try the Power Supply Idle Control if this finally solves my issue, you are my hero! Edit: Power Supply Idle Control must be something only for AMD. I turned off all C-States (sad german noices) lets see if it helps.
  6. +1 for multiple arrays. i need one for my data hdds and my vm ssds.