I don't think I setup and use my cache the right way. How do I remove it? Idiot version please.

Right now I have appdata and system on the cache, not sure why, and under the storage heading on the shares page it says "secondary storage to primary storage" and there's the cache symbol with an arrow pointing to it then the array symbol.

Attach Diagnostics ZIP to your NEXT post in this thread.

As requested.

tower-diagnostics-20251228-1535.zip

Just needs a little tweaking with the user shares. You have several .cfg files for shares that no longer exist. Possibly you accidentally created some that you didn't want by specifying path to them.

Go to Shares - User Shares and click Clean Up at the bottom.

Your appdata is already on cache where it belongs, but your system share has files on the array.

Go to Settings - Docker and disable docker.

Go to Main - Array Operation and Move. Wait for it to complete.

Then post new diagnostics.

Great, thanks. For Docker, I went to settings, docker and then changed it to Enable Docker "No" and hit apply.

Here's the file. Thanks for the help.

tower-diagnostics-20251228-1648.zip

That looks good. You can enable docker again if you want.

None of your other user shares are configured to use cache. Is that how you want it? Or would you like some user shares to be written to faster cache then moved later to slower array?

LOL that's why I wanted to just remove the cache, I literally have no idea of what I'm doing. I didn't really have problems before just thought since I was building a new server that I add that in. I'd rather just remove it.

You want your Docker related shares - appdata, system (also domains for VMs) - on cache or other fast pool so they will perform better, and so array disks can spin down since these files are always open.

I appreciate you trying to help, but you're talking over my head. I'd rather just remove the cache as I never had a problem with the system before. Thanks.

17 hours ago, trurl said:

That looks good. You can enable docker again if you want.

None of your other user shares are configured to use cache.

Why not just leave it like that then. You get the benefits for Docker

16 hours ago, trurl said:

Docker related shares - appdata, system (also domains for VMs) - on cache or other fast pool so they will perform better, and so array disks can spin down since these files are always open.

And your other shares will not use cache

Still over my head, sorry. I have no idea what docker is or does. I just use this as a file server for my home theater.

2 minutes ago, Cartierusm said:

I have no idea what docker is or does.

None of the information below is intended to convince you to use cache or Docker. it is just information to help you better understand why they exist.

Docker is a system that allows applications or services to run in a self-contained way instead of installed directly in the host operating system. Take Plex for example. It is a Docker application hosted in the docker infrastructure running in Unraid. Here are some examples:

Plex, for example, can interact with media on Unraid shares but each has its own file system and management. Docker applications have configuration and other databases, files, etc. (apart from media stored in Unraid shares) and these work best if contained on a "cache" drive that is not part of the Unraid storage array. Using and SSD for a cache drive means it can be accessed by docker applications without spinning up HDDs in the array.

If you write large amounts of media to your Unraid array, it is often advantageous to use the cache drive (typically, an SSD) to initially receive those files at a faster speed and then let the Mover move them to the array at a time of minimal load on the server. A cache drive lets you avoid the initial parity write penalty during times of high server utilization.

If all you want is a simple file server and have no need for other applications or services, you don't need Docker. If you don't care about write speed to the array, you don't need to utilize the cache concept. Both are very handy and useful if you need them. You can ignore them for now if you have no need; however, knowing what they do may open up possibilities for future use of your Unraid server.

Edited December 29, 2025Dec 29 by Hoopster

Ah ok thanks. When I first installed and setup the cache I asked about it here and one person said something like since I have appdata and system on the cache it's not being protected. I'd rather remove it completely and the docker and reinstall at a later time if I decide to go that route.

Simpler to leave cache in and not use it than to remove it and then add it later.

In any case, better if you don't enable Docker or VM Manager unless you have cache.

Ok thanks. Don't I want to move appdata and system off the cache if I'm just going to leave it?

appdata and system belong on cache as already mentioned.

20 hours ago, trurl said:

You want your Docker related shares - appdata, system (also domains for VMs) - on cache or other fast pool so they will perform better, and so array disks can spin down since these files are always open.

You won't actually be using them anyway if you don't enable Docker or VM Manager.

Ah gotcha. So everything important on my system is already protected?

So I don't have to use "move" or anything else?

Edited December 29, 2025Dec 29 by Cartierusm

7 minutes ago, Cartierusm said:

Don't I want to move appdata and system off the cache if I'm just going to leave it?

No need, really. The appdata and system shares are used by docker containers and VMs. If you are using neither Docker nor VMs (they are disabled), nothing will be written to appdata so it doesn't really matter where it is. If you decide to use docker containers or create VMs in the future, appdata and system will be on cache which is really where they should be.

Edited December 29, 2025Dec 29 by Hoopster

Your other user shares are all on the array, protected by dual parity.

But parity is not a substitute for backup. Plenty of more common ways to lose data besides a failed disk, including user error. If you accidentally delete something, parity will agree it has been deleted.

I've always been bi-curious, that's why i have two parities....

Thanks for all the help peeps.