Just set up another unraid server and have a strange issue I am scratching my head with trying to figure out.

the set up is basically a 4 bay NAS, x4 6TB disks set up in ZFS & x2 NVME's set up in ZFS, each NVMe is its own pool.

the x4 disk are called zfs-hdds and one of the 2 nvme's is called zfs-cache.

I have a share set up called share (How original)

This share currently has no files within it apart from a .RcycleBin folder from the recycle bin plugin.

The share is set like this for mover

So the primary storage is the zfs-cache, when mover runs it moves the share folder to the secondary storage as expected.

then I get the error below from fix common problems, It seems any shares I set this way have the same issue, have one for nextcloud too that does the same,


is there a better way to set this up, my other server isnt running zfs and was wondering if its possible due to that.

The server was also only set up in recent days and updated from 7.3.4 to 7.4.0 last night and I didnt notice the issue before then, not saying it wasnt present before 7.4.0 as I did only set the server up 2 days ago so had to say and hoping someone can provide some inseight or guidance into what I am doing wrong and if theres a better way to set up the system with zfs.

us01-diagnostics-20261111-2209.zip

Edited Wednesday at 10:11 PM3 days by DeekB
adding diags

The share view merges every pool that has a folder of the same name, so files on zfs-hdds are not a second copy that went missing. Mover putting the folder onto the secondary pool is the setting doing what you asked.

Fix Common Problems raises that warning when it finds the folder on a pool the share is not set to use. Open the share and check Secondary storage is zfs-hdds, not None, and the mover direction is zfs-cache to zfs-hdds. If Secondary is None, the files now on zfs-hdds are exactly what the warning is about.

Then look at /mnt/zfs-cache/share and /mnt/zfs-hdds/share. The .RecycleBin folder is a usual leftover. The plugin creates it on whichever pool the write hit, and it stays after you change primary and secondary. If that folder is the only thing on the pool the share should not use, that is the warning.

Don't delete a folder that exists on both pools until you have compared them. The share page shows them as one tree. ZFS is not the cause. The same split happens on any pool.

FCP stil has a bug when two pools are being used for the same share. It only correctly detects that when pool and array are being used, you can ignore.

1 hour ago, JorgeB said:

FCP stil has a bug when two pools are being used for the same share. It only correctly detects that when pool and array are being used, you can ignore.

Thank you, I will safely ignore it then.