Bug CPU Core 4 pinned at 100%


Recommended Posts

Hello everybody,

 

several days ago i migrated from proxmox to unRAID.

Sadly i discovered a problem since day one with unRAID on the system.

 

I dont know why, but on of my CPU Cores is pinned at 100%.

Directly after a new start and typing in htop its CORE 2 at 100% and after 3 secs it switches to CORE 4.

 

Any idea what causes this problem?

Edited by C0bra_2056
Link to comment

Why are you running Mover every 5 minutes? Mover is intended for idle time. Since your cache is so small probably better to not cache any user share writes and just use it for fast storage for dockers / VMs.

 

Your system share has some files on the array. You want appdata, domains, system shares all on cache so dockers / VMs won't be impacted by slower parity, and so they won't keep array disks spunup since they will always have files open.

Link to comment

Every 5 minutes? Mh, i was pretty new to the system and tried to learn.

Wasted the whole day to get into the system. ATM i set it to an daily base for mover, before it was an hour. Dont know where the 5 minutes come from.

 

An hour ago i already removed the cache option of my "StorageArray", the cache is now exlusive for the "DockerArray".

 

But thx for the explanation, took a while to understand the cache logic in unRAID.

 

Got any idea about the cpu core usage?

 

 

 

I completely forgot to attach an screenshot, but i dont think it helps a lot if the diagnostics got already posted:

 

Dafuq.PNG

 

EDIT: well the screenshot is kinda useless, the top part of htop is cut. But it shows that the cpu core is maxed out at 100%.

Edited by C0bra_2056
Link to comment

I tried to search in the forum if somebody else got the same problem.

Every other thread where i found the same problem was source of the problem the gui mode. Which was some kind of a bug that i reboots into the gui mode.

So i plugged in my monitor and there was only a terminal session. Too bad. Back to zero.

Link to comment

Finally i got time today to restart the system.

 

Alright, hooked up a monitor and restartet into safe mode (no GUI, no plugins).

And the 100% cpu usage was gone (Diagnostic attached).

 

After a another restart into normal mode (no GUI), there was again a core locked at 100% (Diagnostic attached aswell).

 

Interesting fact was, after i set up unRAID at the beginning without installing any plugin, there was already this issue.

 

Down below is a picture of htop showing the top cpu processes in normal mode with 100% cpu core usage, aswell a picture of all installed plugins.

 

The Plugin Nerd Tool was only nessecery for the gpu dashboard installation.

Unbalance is deactivated.

01.04.unraid.PNGunraid plugins.PNG

normalmode-albert-diagnostics-20210401-1749.zip safemode-albert-diagnostics-20210401-1744.zip

Edited by C0bra_2056
Link to comment

I got an idea today, and searched a bit in the "Setup" menu from htop.

And removed the "x" from "Hide kernel threads.

 

Now its possible to see which process is taking up the cpu usage.

The command "kworker/3:2+pm" is taking round about 83-85% cpu usage.

 

But i dont know what this process is good for. Anybody an idea?

Bild_2021-04-04_202912.png

Link to comment
  • 2 weeks later...
  • 4 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.