trurl

That doesn't help at all with automount or scripting since it still has no way to decide which of the 2 identical serial numbers that name should apply to.

Here are the relevant instructions from the link I gave you: You have it set to cache-no, but it still has files on cache. Mover ignores cache-no and cache-only shares. In order to get the rest of that share moved from cache to array, you will have to set it to cache-yes and run mover. It doesn't look like we actually confirmed that you had successfully taken care of 2 and 3 earlier so after doing those post your diagnostics. After we have confirmed that system is all on cache and Death Star is all on the array, then you can change system to cache-only and Death Star to cache-no. Here are some search results: https://www.google.com/search?q=unraid+cpu+scaling+driver&oq=unraid+cpu+scalin&aqs=chrome.0.0j69i57j0.9070j0j7&sourceid=chrome&ie=UTF-8

No, that is only the syslog. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

👍

Why have you allocated 40G to docker image? 20G is what I always recommend and should be more than enough unless you have an application misconfigured to write to a path that isn't mapped. Have you had problems filling docker image? Your appdata and system shares have some files on disk1, and mover can't move them to cache where they belong because mover can't move open files. Go to Settings - Docker and disable dockers. Go to Setting - VM Manager and disable. Run mover and when it complete post new diagnostics.

OK, the folder on cache doesn't actually have any contents. Go to Settings - Docker, disable and delete docker image. Delete the system folder from disk1. Enable docker again and docker image will be created on cache where it belongs. You can install all of your dockers with all their settings just as they were using the Previous Apps feature on the Apps page.

Better price per TB with larger disks and better performance. If you go with a single data disk with a little more capacity than you need now, and a parity disk at least that large, then you will have more expandability and possibly come out similar cost as 3 drives.

That is the way you should work with all (or at least most) dockers in Unraid. There are currently over 700 Apps to choose from on the Apps page. Any docker from the Apps page takes you to that same form with some things already filled in for you. I recommend not sharing any disks and only allow access to user shares on the network. You can definitely get yourself in trouble if you try to work with disks and user shares together. And unless you have specifically allowed disk shares, none will be shared.

What exactly do you mean by "renaming"?

Also note that caching user share writes doesn't happen unless you make it happen. Each user share has settings including whether and how it uses cache. In addition to domains share being on cache, your appdata and system shares will be (and should be) on cache by default.

As in, added to NZBGet manually and since you installed it fresh?

And you aren't using the appdata from a previous install?

Is this an NZB you added yourself?

Where are you seeing this?

Are you booting from a USB2 port?

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

Did you set the UMask as explained in the first post of this thread?

What is your current docker run for plex?

That doesn't agree with that last plex docker run you posted. Did you redo your plex docker since you posted that?

Looks like you have duplicate docker images. What do you get with these? ls -lah /mnt/cache/system/docker ls -lah /mnt/disk1/system/docker

Still a little unsure about your anonymized share names. Some are showing up in the diagnostics with upper case, but your plex mappings don't seem to match that. Post a screenshot of the User Shares page.

Been a while since I did this so I'm not sure what happens from scratch. It may be that enabling VMs creates the domains share. No harm in creating it yourself though. It should be cache-prefer.

Thanks, much better. Since you are starting your dockers over, have you deleted the appdata for each of those old dockers? Or were you hoping to reuse that?

If you did indeed mean sdg sdh, then what would your proposed solution do with Automount devices? How could it know which should automount and which script to run if there was an associated script? Of course it has to be something that persists or it will just be more problems.