My frustrations with Unraid continue. I have learned from my past frequent issues and downloaded the diagnostics before I updated. It feels like everytime that I update or do anything with Unraid, it leads to having to redo a majority of things or some hardware issue occurs. So I've ignored for the most part my server for 5 months and had few issues until today when I went to access Radarr and found that it had, along with several other containers, disappeared. I know these are first world problems and not really a big deal in the grand scheme of life, but fuck if it doesn't frustrate me. I use Unraid primarily for media as I dabbled with other stuff in the past and found that I just don't have the ability or knowledge to adequately deal.

If anyone could give me some insight per my diagnostic, I'd appreciate it. Then I may be leaving the Unraid world and finding something that is more reliable for me. In the meantime, I need to get my media off, in particular my music as some can't be found anymore.

tower-diagnostics-20260221-1830.zip

Feb 21 18:21:25 Tower root: Fix Common Problems: Error: Invalid folder cache contained within /mnt

You don't have a pool named cache, but you probably have a docker still referencing that path and it is creating that folder, which is not mounted storage, but is in the RAM space reserved for the OS. If you fill that up, the OS will become unstable. This may be the reason for some of your trouble, and should be your first priority for fixing. Figure out what is referencing /mnt/cache.

Your Docker/VM related shares - appdata, domains, system - have files on the array. In fact, domains and system are configured to be moved to the array.

Ideally, these shares would have all files on cache or other pool, with nothing on the array, so Docker/VM will perform better, and so array disks can spin down since these files are always open.

Nothing can move open files, so you have to disable Docker and VM Manager in Settings before you can move those shares where they belong.

Just now, trurl said:

Figure out what is referencing /mnt/cache.

You should reboot after fixing this and post new diagnostics

@trurl thank you. i'll work on getting this fixed. i found the issue for /mnt/cache and redirected it. I'm going to try to get the shares resolved, but have to wait until the kiddo goes to bed since she's watching something.

Your Docker/VM related shares - appdata, domains, system - have files on the array. In fact, domains and system are configured to be moved to the array.

Ideally, these shares would have all files on cache or other pool, with nothing on the array, so Docker/VM will perform better, and so array disks can spin down since these files are always open.

Nothing can move open files, so you have to disable Docker and VM Manager in Settings before you can move those shares where they belong.

What is the best way to accomplish this once docker/vm mgr are disabled?

Set these shares to

Primary:appcache; Secondary:array; Mover action:array->appcache

Click MOVE in Array Operation, wait for it to complete, post new diagnostics.

Finally able to finish. Attached is new diagnostics.

tower-diagnostics-20260222-1917.zip

You have a lot of .cfg files in config/shares for user shares that no longer exist. Go to User Shares page and click CLEAN UP.

Your appdata still has files on the array. You didn't change its settings so it didn't get moved.

On 2/21/2026 at 9:05 PM, trurl said:

Set these shares to

Primary:appcache; Secondary:array; Mover action:array->appcache

Click MOVE in Array Operation, wait for it to complete, post new diagnostics.