trurl

Your screenshot above is missing a crucial detail. What is the name of that user share?
 
Your appdata, domains, system shares all have files on the array. Ideally, these shares would all be on fast pool (cache) so Docker/VM performance isn't impacted by slower array, and so array disks can spin down since these files are always open.
 
Set appdata, domains, system shares to cache:prefer so these can be moved to cache.
 
Nothing can move open files, so you will have to go to Settings and disable Docker and VM Manager before these can be moved.
 
Then run Mover.
 
When mover completes, post new diagnostics.
 
Why is your docker.img so large?

Unraid installs itself into RAM fresh from the archives on flash at each boot, and runs completely in RAM. Think of it as firmware. These flash archives are not modified except on each upgrade. These are the bz* files in the root folder of the flash drive.
 
Your configuration is completely stored in the config folder on flash. You must always have a current backup of your configuration.
 
Everything on your disks is just your data, no Unraid OS files are stored with your data, but Dockers/VMs are stored with your data.

I've seen occasional reports of spurious pending on some brands of disk. Should be OK now.
 
 
 
 

Revert to stock go file

Your appdata, domains, system shares have files on the array. Ideally these should all be on fast pool (cache) with no files on the array. Docker/VM performance will be impacted by slower array if these files are on the array. More importantly for your question, if these files are on the array, array disks can't spin down because these files are always open. With no docker running, appdata won't be open, but files in system share are always open whenever Docker and/or VM Manager is enabled in Settings even if no dockers/VMs are running.
 
If you have large vdisks you might have to keep domains on the array. If not, set domains share to cache:prefer.
 
Nothing can move open files. Disable Docker and VM Manager in Settings, run mover to get these moved to cache.
 
Mover won't replace files so if any already exist on cache they won't be moved. You will have to decide which to keep. Installing Dynamix File Manager plugin will help with this.

Looks like everything mounted cleanly.

No I did as you figured out. Corrected my post above.
 
So your docker.img is on the array. Some good reasons to not have it there. Docker performance will be impacted by slower array, and array disks can't spin down since these files are always open.
 
Not clear those would cause your problems, but might as well recreate docker.img so it will go to cache and maybe a fresh one will work better as well.
 
https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file
 
https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications

https://wiki.unraid.net/Manual/Shares#Default_Shares

Unraid installs itself to RAM at each boot from the archives on flash. Think of it as firmware. Flash also has all of your configuration that you set in the Unraid webUI. None of Unraid installs to any of your disks. Flash must always be present to boot and to save your configuration. Never remove it when running your server. 

I do see a disk like that in pool cache_nmve, but I think you must instead be talking about the single disk pool named vms_nvme. I don't see any disk for that and the pool doesn't currently exist. You might try replugging it.
 
If it was on that pool, unless you backed it up yourself, perhaps with a plugin, then there is no copy.

I don't know which file you are talking about. Or where you moved it to. You don't want to move files FROM cache. You want to move files TO cache so those array disks can spin down. Doesn't sound like what you might have done will help anything.
 
If Docker and VM Manager are disabled in Settings, and if User Share named "system" is still set to cache:prefer, go to Main - Array Operation and run Mover to get files for that share moved FROM array TO cache.
 
Then post new diagnostics.

Do it again without -n, if it asks for it add -L
 
 

You need to combine your Music share and your music share, and you need to combine your Data share and your data share. Linux is case-sensitive, so these are different user shares. But, SMB is not case-sensitive, so it will only let you see one or the other on the network.
 
But wait until you get your disk problems fixed. FCP is saying disk22 may be read-only, or it may be full. And it is, in fact full.
 
And it isn't the only disk that is way too full. You need to add capacity and move some files off those disks.
 
 

Do it again without -n. If it asks for it add -L. Post results.
 
Why does it think your cache pool disk assignments are wrong?

Check filesystem on disk7

What date and time is it on your server? 

You will also want to wait until you have cache to enable Docker and/or VM Manager. You want appdata, domains, system shares on cache or other fast pool so Docker/VM performance isn't impacted by slower array, and so array disks can spin down since these files are always open.

It allows the disk to be shared on the network, but that isn't the same as an Unraid user share. User shares can span disks, can be operated on by mover, and can have all of the other settings you see for any of your other user shares.

Your docker templates are on flash and the working storage for each container should be in appdata, so unless you did something to delete those you should be able to recreate docker.img and reinstall your containers from Previous Apps and they will work just as before and pick up where they left off.
 
https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file
 
https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications

You can create multiple user shares, each can specify which disks to use, default is to use all disks

Looks like you are running trim hourly and those entries have filled your log. I only trim weekly.

Correct.
 
But since you mention hotswap I just want to make sure you don't intend to do this under power. Hotswap not recommended for array or pool disks even if hardware supports it. Even for replacing disks, since Unraid won't do anything with a new disk until you assign it, and you can't make assignment changes with the array started anyway, so no point in hotswap.
 
Be sure to double check connections before startup.

No ethernet connection. Check ports, plugs, cables on server, switch, router.

If you're sure you don't need anything still on the original disk now, you can rebuild the contents of the emulated disk onto that original disk by stopping the array, reassigning the disk to its slot in the array, and starting the array to being rebuild. Note that the contents of that original disk will be completely overwritten by the contents of the emulated disk.
 
Please let us know if you have questions or other problems.