Hello, I'm having a problem with my unraid, it's at 100% cpu, however, when I do an htop or docker start, it uses very few resources, How can I find the cause of the problem? Because I have to restart my server every 3-4 days

Attach Diagnostics to your NEXT post in this thread.

Here is the file, thx @trurl

sljd-diagnostics-20250114-1438.zip

Edited January 14, 20251 yr by JD84

Have you tried to disable docker?  If it goes back to normal, it's one of your containers.

20 minutes ago, Veah said:

Have you tried to disable docker?

You could also try booting is SAFE mode to see if a plugin is causing it.

 

Unrelated, but your cache pool has 2 different sized drives in btrfs raid1. The total capacity will be the size of the smaller of the 2.

I just cut off the dockers, indeed, my CPU is down well. So how do I know which container is causing this? Because despite my orders, I have no trace. And the diagnosis I sent doesn't show anything?

1 minute ago, JD84 said:

So how do I know which container is causing this?

Try running them one at a time.

Here is a screenshot after the docker reboot. Now you will have a solution to diagnose which docker caused this?

1 minute ago, JD84 said:

which docker caused this?

Not clear whether any docker caused it.

5 minutes ago, trurl said:

Il n’est pas clair si un docker l’a causé.

can i schedule a re-recording every day of docker? like that i would have more worries 😂

Edited January 14, 20251 yr by JD84

Having 2 cache disks allows me to secure my docker.io instance because it is on the cache, so as not to lose the configurations. Do you confirm this? Is this done by default in RAID 1? @trurl

The docker templates are on the flash drive. You should always keep a current backup of flash.

 

It isn't necessary to have a backup of docker.img since its contents are easily recreated from the templates.

 

More important to have a backup of appdata, whether on a redundant pool or not.

 

btrfs raid1 is a redundant pool. My point was that the total capacity of btrfs raid1 when different sized disks are used is equal to the smaller of the disks. So your cache pool can only hold 256G (minus some overhead). Very important that you don't fill this up or it may corrupt.

 

Now that you have made me look more closely, I see that your appdata, domains, and system pools have files on the array.

 

https://docs.unraid.net/unraid-os/manual/shares/user-shares/#default-shares

 

Ideally, these shares would have all files on a pool such as cache, with no files on the array. This will improve Docker/VM performance, and allow array disks to spin down since these files are always open.

 

These shares should be Primary:cache, Secondary:array, Mover Action:array->cache.

 

Nothing can move open files so you have to disable Docker and VM Manager in Settings before running mover.

Its ok @trurl

 

Your screenshot shows those shares configured to be moved from cache to the array. What I said was to move them from the array to cache.

3 hours ago, trurl said:

Ideally, these shares would have all files on a pool such as cache, with no files on the array. This will improve Docker/VM performance, and allow array disks to spin down since these files are always open.

 

Also, that screenshot only shows how things are configured currently, where new files will be written, and how mover will (try) to move files. They won't necessarily move anything.

3 hours ago, trurl said:

Nothing can move open files so you have to disable Docker and VM Manager in Settings before running mover.

 

You can see how much of each disk or pool is used by each user share by clicking Compute... (or your language equivalent) for each share.

On 1/14/2025 at 2:48 PM, JD84 said:

Hello, I'm having a problem with my unraid, it's at 100% cpu, however, when I do an htop or docker start, it uses very few resources, How can I find the cause of the problem? Because I have to restart my server every 3-4 days

 

 

Do You have "detailed CPU time" enabled in htop?
it is under F2 setup\display options

 

in my case it was due to Disk IO Wait