How can I fix "Share system set to cache-only, but files / folders exist on the array... You should change the shares settings appropriately or use the dolphin / krusader docker applications to move the offending files accordingly. Note that there are some valid use cases for a set up like this. In particular: THIS  More Information"? I followed @Squid 's steps found on his post back in 2022 (https://forums.unraid.net/topic/120220-fix-common-problems-more-information/?tab=comments#comment-1098683).

Changed the "Secondary Storage" from "none" to "Array". Set the mover to "Array -> Cache" and then ran the mover. Then realized I forgot to stop my Docker containers and VMs. So I went into my Unraid Settings turned off Docker and VM and then ran the mover again multiple times. Changed the "Secondary Storage" back to "none". Still got the same error. Restarted my server. Still got the same error. Tried all the steps one more time. Still got the same error. Even ran the mover with "Secondary Storage" set to "none" just in case. No change.

What am I doing wrong here?

I've attached to Diagnostic files to help with debugging.

fossiltower-diagnostics-20251028-1229.zip

The reason for changing my settings share from Cache + Array to Cache only is that I recently converted my Docker data-root from "btrfs vDisk" to "Directory" and in the more information Unraid states

"You must specify a folder for Docker. The system will automatically create this folder when the Docker service is first started.

It is recommended to create this folder under a share which resides on the Cache pool (setting: cache=Only). For best performance SSD devices are preferred."

Edited October 28, 2025Oct 28 by SnugglyDino

The main reason I started poking around for things wrong with my Unraid server in general is because I keep getting the same error when I try to install/run PostgreSQL_Alpine and cannot figure out how to fix it.

docker run
  -d
  --name='PostgreSQL_Alpine'
  --net='dinopark'
  --pids-limit 2048
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="FossilTower"
  -e HOST_CONTAINERNAME="PostgreSQL_Alpine"
  -e 'POSTGRES_DB'='postgres'
  -e 'POSTGRES_USER'='postgres'
  -e 'POSTGRES_PASSWORD'='postgres'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon=''
  -p '5432:5432/tcp'
  -v '/mnt/cache/appdata/postgresql_alpine':'/var/lib/postgresql/data':'rw'
  --user=99:100
  --memory=2G
  --restart=unless-stopped 'postgres:alpine'


WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
cb5a7a7e0206cc37227a6d75e50ec02c16c3158de74aec4e115300e4edb3090f
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/mnt/cache/appdata/postgresql_alpine" to rootfs at "/var/lib/postgresql/data": change mount propagation through procfd: open o_path procfd: open /var/lib/docker/btrfs/subvolumes/0f5abc07d057f62fa3844b35cde2d395159746f4ef38822f226b2134c26781cc/var/lib/postgresql/data: no such file or directory: unknown.

The command failed.

Because you still have system share on disk1

system shareUseCache="only" # Share exists on cache, disk1

6 minutes ago, MowMdown said:

Because you still have system share on disk1

system shareUseCache="only" # Share exists on cache, disk1

How do I get the system share off of disk1?

I thought following the steps here (https://forums.unraid.net/topic/120220-fix-common-problems-more-information/?tab=comments#comment-1098683) would take all my system shares off of disk 1 and onto my cache.

Well first take a look at what's physically on disk1.

Confirm it's not just an empty "system" folder.

After that set mover logging to YES -> Settings > Scheduler > Mover Logging: Yes (hit apply)

Stop the docker service entirely -> Settings > Docker> Enable: No (hit apply)

Then run mover again, and post new diagnostics after it's complete. We'll go from there.

43 minutes ago, MowMdown said:

Well first take a look at what's physically on disk1.

Confirm it's not just an empty "system" folder.

After that set mover logging to YES -> Settings > Scheduler > Mover Logging: Yes (hit apply)

Stop the docker service entirely -> Settings > Docker> Enable: No (hit apply)

Then run mover again, and post new diagnostics after it's complete. We'll go from there.

Looks like the only thing in there is a docker.img file.

---

Stopped the docker service and VM service. Ran the mover again with mover logging enabled. The docker.img file refuses to budge.

Attached is the updated diagnostics.

fossiltower-diagnostics-20251028-1443.zip

Oct 28 11:41:40 FossilTower move: move: /mnt/disk1/system/docker/docker.img File exists

Mover won't move duplicate files, see which one you are using and delete the other one.

2 hours ago, JorgeB said:

Oct 28 11:41:40 FossilTower move: move: /mnt/disk1/system/docker/docker.img File exists

Mover won't move duplicate files, see which one you are using and delete the other one.

How can I tell which one is active? I'm assuming the one on the Cache drive is the one I am using but is there any way to double check? Or do I just have to delete the one on Disk 1 (after downloading the file for backup) and hope for the best?

probably the cache drive one since that is set to cache only and you probably have your docker.img configured to be wrote to /mnt/user/system/docker/... which would have re-created it on your cache drive after you set the share to use cache only.

docker.img can almost always be deleted and re-created with minimal downtime. You often just have to re-install the containers as the appdata is store separately.

Edited October 28, 2025Oct 28 by MowMdown