itimpi

You are just downloading faster than mover is capable of handling. Mover can never move files faster than you would get if you were bypassing the cache and going directly to the array. It sounds as if your download speed can exceed the speed you can write to the array. Mover is not really designed for the scenario you describe and you may be better of not trying to cache these downloads. One solution will be to avoid downloading to a location that mover later needs to move to the main array. If you DO want to continue downloading to the cache drive then make sure that you have the Minimum Free Space value for that pool set to be larger than the biggest file you expect to download so that downloads will start by-passing the cache pool for new files when the free space on it drops below that value. If you download multiple files in parallel then the free space value would need to be larger than their combined size.

This is saying do not format it from with UD BEFORE adding it to the array as if you try to add it as a new drive to the array and the drive being added does not have the 'clear' signature then Unraid will promptly try to start clearing it again to avoid invalidating parity. It is a very common mistake to format the drive from within UD after preclearing and before adding it to the array. It will always need formatting AFTER adding it to the array as a new drive.

You should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs. The one thing that occurs to me for a potential cause is the Split Level setting on User shares? This setting takes priority on User shares in case of conflict with other share settings so can force files to a drive because of the path involved.

The New Config option is covered Here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The Unraid OS->Manual section in particular covers most features of the current Unraid release. i recommend you use the option to keep all current assignment, and then just remove the drive you longer want in the array on the Main tab before starting the array to commit the change. No need to physically disconnect that drive. Your dockers, etc will stay installed.

The sym[toms do sound very much like insufficient power. You never actually mentioned what PSU you are using?

You should handle drives that are not intended to be permanently part of the Unraid array by using the Unassigned Devices plugin. you can reset your current array settings via Tools->New Config.

I would create the top level folders that correspond to shares as Dynamix File Manager does not seem to let you create folders at the top level of s disk shares. I assume this is intentional (but I am not sure) as it would end up creating User Shares with the folder name. This is probably a permissions issue. You can correct this using Tools->New Permissions (probably do it direct on the list+found share). You can also set that share to be visible on the network by changing the Export setting under its SMB properties.

The setting applied to drives in the main array regardless of what type of dtive they are. sounds like you need to run iperf tests in both directions to check what speed you are getting over the network.

If you use Dynamix File Manager to do the ‘move’ it will automatically use a copy/delete strategy while doing it.

Correct. only if you do a copy followed by a delete. if you try a ‘move’ then you will encounter the behaviour described here in the Caution in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The Unraid OS->Manual section in particular covers most features of the current Unraid release.

This tends to mean that you have a docker container continually crashing and then restarting. You can tell which one(s) it might be by the uptime on the Docker page.

You might find something like this to be more reliable. The problem with the ones you have is that if you connect 4 drives to them they might be subject to voltage sag when under load as the SATA connection at the host end is less robust and can carry less current than the Molex equivalent and that can cause the symptoms you are seeing. Your issue could of course be something else entirely but power issues can be a bit tricky to track down at times.

The latest instructions for this are here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. The Unraid OS->Manual section covers most aspects of the current Unraid release.

How many ways does it split? A SATA->SATA splitter tends to be unreliable if it is more than 2 way as the SATA connection cannot handle much current, whereas a Molex->SATA gets away with a 4 way split.

I would expect that you can just delete the file and it would be recreated.

Unraid licences work for any Unraid release

That location is only inside the container so you should be fine.

Any top level folder on a drive or pool is automatically considered a share so the behaviour you got is what is expected.

With those settings at the container level, you want to tell Plex to transcode to /transcode. The docker system will then redirect that to /tmp/plex_transcode at the Unraid level.

Simply mapping transcoding to /tmp at the Plex level inside the container does NOT map it to RAM, but to a location inside the docker.img file. What you would normally want is something like /transcode at the Plex level mapped to /tmp/transcode at the Unraid level since at the Unraid level /tmp IS in RAM.

Yes but make sure you are deleting it from the physical drive and not via a User Share.

I would suggest mapping it to a folder with /tmp as otherwise Plex may end up removing files under the /tmp path at the Unraid level that belong to other applications.

Cannot see any entry in the docker settings that maps the /tmp location that you have set at the Plex level to a location on the Unraid host (e.g. mapped to something like /tmp/plex) so the transcode temporary file will be inside the container.

If you have files existing in the wrong location (particularly if they are duplicates) it is up to you to manually sort this out if you want to stop these warnings. Unraid will not do it automatically.

You should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs.