1 minute ago, trurl said:

Do we wait for each to complete before starting the next?

Correct, you can only remove on disk at at time.

2 minutes ago, trurl said:

How will we know it has completed? Just wait for the command prompt to return?

Yep, I recommend using tmux or something similar to not lose the connection if the terminal closes, can look at the progress by clicking on the pool, btrfs filesystem info will show that disk having less and less data.

6 minutes ago, JorgeB said:

recommend using tmux

@Moker-Vet

Since you have the preclear plugin installed, you should already have tmux.

But this plugin makes it easier to work with:

@Moker-Vet

Let us know when you are ready to proceed with removing sdv from the pool.

Hi Trurl,

i have installed the Tmux Terminal Manager plugin. Also the results of the 3 extended smart tests are back, all completed without errors. so i think we are good to go!

this error has just showed up

moker-vet-diagnostics-20260206-1206.zip

Is it possible to turn off logging for this plugin? It's really cluttering up syslog

fanctrlplus.plg - 1.3.3  (Up to date)

1 hour ago, Moker-Vet said:

this error has just showed up

Are there any containers you can live without while we work on these other things?

i disabled the logging of the fanctrl. i will disable as many containers as i can

i have disabled most of my containers, i have 21 running right now, if i would disable those i will feel some impact of it. so i left them running

Reboot and post new diagnostics

I'd like to clean up some of your docker/VM related shares so we can get that out of the way and let your dockers/VMs run while we work on getting moker-vet drives into array. This is mostly in the FCP stuff I quoted near the beginning of the thread here:

https://forums.unraid.net/topic/196809-varlog-is-getting-full/#findComment-1604757

You don't currently have VM Manager enabled. Do you have any VMs? If not, is there anything in the domains share? FCP is complaining that share is configured as cache-only, but all its files are on the array. Similar for isos share.

Your docker.cfg has

DOCKER_IMAGE_FILE="/mnt/cache/DockerImage/docker.img"
DOCKER_APP_CONFIG_PATH="/mnt/cache/appdata/"

Since these are on cache, not really in the way, but they are technically user shares named DockerImage and appdata. appdata is configured as cache-only, but FCP is complaining that DockerImage is configured to be on the array. Easy fix to make that share cache-only.

You also have a user share named docker which is not mentioned in docker.cfg. What is the purpose of that share? FCP is complaining that it is configured to be on array but is on cache. Another easy fix if you even need that share.

Same for bookbounty, Plex-Transcode, transcode. On cache but configured to be on the array.

Admin share is configured as cache-only, but it has files all over the place including moker-vet. What is the purpose of that share?

On 2/6/2026 at 4:08 PM, trurl said:

I'd like to clean up some of your docker/VM related shares so we can get that out of the way and let your dockers/VMs run while we work on getting moker-vet drives into array. This is mostly in the FCP stuff I quoted near the beginning of the thread here:

https://forums.unraid.net/topic/196809-varlog-is-getting-full/#findComment-1604757

You don't currently have VM Manager enabled. Do you have any VMs? If not, is there anything in the domains share? FCP is complaining that share is configured as cache-only, but all its files are on the array. Similar for isos share.

Your docker.cfg has

DOCKER_IMAGE_FILE="/mnt/cache/DockerImage/docker.img"
DOCKER_APP_CONFIG_PATH="/mnt/cache/appdata/"

Since these are on cache, not really in the way, but they are technically user shares named DockerImage and appdata. appdata is configured as cache-only, but FCP is complaining that DockerImage is configured to be on the array. Easy fix to make that share cache-only.

You also have a user share named docker which is not mentioned in docker.cfg. What is the purpose of that share? FCP is complaining that it is configured to be on array but is on cache. Another easy fix if you even need that share.

Same for bookbounty, Plex-Transcode, transcode. On cache but configured to be on the array.

Admin share is configured as cache-only, but it has files all over the place including moker-vet. What is the purpose of that share?

Hi Trurl,

This is what i am unable to fix, as i cannot find an option to change the share to be on array or on the cache. i can change the storage location but that doesnt make a share to be a cache only share, or an array only share i have found. i dont see a checkmark to make a share a cache only or something like that. how do i deal with this?

5 hours ago, Moker-Vet said:

Hi Trurl,

This is what i am unable to fix, as i cannot find an option to change the share to be on array or on the cache. i can change the storage location but that doesnt make a share to be a cache only share, or an array only share i have found.

A share is of the ‘only’ type if it has primary storage set and no secondary storage set.

Note, however, that Unraid will not automatically move any existing files that are in the wrong location when you remove a secondary storage option.

6 hours ago, Moker-Vet said:

how do i deal with this?

https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/shares/#primary-and-secondary-storage

Nothing can move open files. Disable Docker and VM Manager in Settings, then

On 2/6/2026 at 10:08 AM, trurl said:

You don't currently have VM Manager enabled. Do you have any VMs? If not, is there anything in the domains share? FCP is complaining that share is configured as cache-only, but all its files are on the array. Similar for isos share.

Maybe OK to hang on to them in case you want that later.

Set domains and isos shares to

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

On 2/6/2026 at 10:08 AM, trurl said:

FCP is complaining that DockerImage is configured to be on the array. Easy fix to make that share cache-only.

Set DockerImage share to

Primary:cache; Secondary:none

On 2/6/2026 at 10:08 AM, trurl said:

a user share named docker which is not mentioned in docker.cfg. What is the purpose of that share? FCP is complaining that it is configured to be on array but is on cache. Another easy fix if you even need that share.

If you do want to keep that for some reason, and you do want it cache-only, set it to

Primary:cache; Secondary:none

On 2/6/2026 at 10:08 AM, trurl said:

Same for bookbounty, Plex-Transcode, transcode. On cache but configured to be on the array.

If you want them cache-only, set them to

Primary:cache; Secondary:none

On 2/6/2026 at 10:08 AM, trurl said:

Admin share is configured as cache-only, but it has files all over the place including moker-vet. What is the purpose of that share?

If you want all that share to be on cache, set it to

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

After all that, click MOVE in Array Operation, wait for it to complete, then

Post new diagnostics

Hi Trurl,

Thank you for your explanation! i already had these settings set but i think something went wrong, so i removed these shares and added them again with the same settings. then i ran unbalanced to move the remaining files on wrong disks and now the warnings have dissapeared!

i think we are ready to move to the next phase!

moker-vet-diagnostics-20260213-0939.zip

Lots to discuss, but we might be able to eliminate some of it by simply

On 2/11/2026 at 9:03 AM, trurl said:

click MOVE in Array Operation, wait for it to complete, then

Post new diagnostics

i believe it all has finished

moker-vet-diagnostics-20260216-1341.zip

Lots of stuff cluttering up syslog including some mover errors.

Reboot and post new diagnostics.

moker-vet-diagnostics-20260217-0912.zip

Hi Trurl, i have restarted and new diagnostics!

Some changes to your user shares have fixed a lot.

E----s                            shareUseCache="only"    # Share exists on cache, disk7, disk12, disk13, disk14

To get that moved, you have to set

Secondary storage:array: Mover action:cache->array

assuming you do want that moved to the array.

If instead you want that moved to cache, set Mover action the other way.

B------s                          shareUseCache="only"    # Share exists on moker-vet, disk1, disk3, disk4, disk7, disk8, disk9, disk11
M---------------e                 shareUseCache="only"    # Share exists on moker-vet, disk4, disk7, disk9

These would be moved to the array since disks for moker-vet pool are going into the array.

But let's see how much space each of your user shares are taking on moker-vet pool currently.

What do you get from command line with this?

du -h -d 1 /mnt/moker-vet | sort -hr

On 2/17/2026 at 3:32 PM, trurl said:

Some changes to your user shares have fixed a lot.

E----s                            shareUseCache="only"    # Share exists on cache, disk7, disk12, disk13, disk14

To get that moved, you have to set

Secondary storage:array: Mover action:cache->array

assuming you do want that moved to the array.

If instead you want that moved to cache, set Mover action the other way.

i have already fixed this by manually moving these files. for some reason my mover didnt do his job right, as it was already set for a long time as "Secondary storage:array: Mover action:cache->array". so i believe this is resolved. i also dont see warnings for this anymore

On 2/17/2026 at 3:39 PM, trurl said:

B------s                          shareUseCache="only"    # Share exists on moker-vet, disk1, disk3, disk4, disk7, disk8, disk9, disk11
M---------------e                 shareUseCache="only"    # Share exists on moker-vet, disk4, disk7, disk9

These would be moved to the array since disks for moker-vet pool are going into the array.

But let's see how much space each of your user shares are taking on moker-vet pool currently.

What do you get from command line with this?

du -h -d 1 /mnt/moker-vet | sort -hr

I have set all shares (except moker-vet) that exist on moker-vet pool to move to array, this includes:

backup

downloads

media-landingzone

synology-nas

i have not yet set the moker-vet share to start to move to the array.

the issue i am seeing coming up, with the array i can move data of a specific disk one by one. but with the moker-vet pool i cannot. i cannot see one disk, its just the entire storage pool so i cannot move the data of one disk to another and exclude it from using. how would i overcome this?