trurl

Since you read the FAQ on volume mapping and others have posted screenshots, it's not clear what you are having a problem with. Could you post a screenshot?

Did you use Community Applications to get started with this? Are you actually using the linuxserverio plex docker or some other plex docker?

Sounds like you don't really understand volume mapping. Have you read the Docker FAQ? Are you following any guides to set this up?

Epecially when reporting something in prerelease support.

It is important for the docker volumes to be mapped correctly, but the thing that typically causes an application to write inside the docker image is not configuring the application itself so that it only writes into a mapped folder. For example, if SAB has a setting which controls what folder it uses to process files it has downloaded, then you must make sure that folder is in a mapped folder. And don't forget upper/lower case is important, as is whether or not you use a '/' at the beginning of the path depending on whether it is relative or absolute.

Your log space is completely full but it's not clear why, since syslog isn't that large. What else do you have in /var/log?

Yes, I like that too. Won't let you copy a file to that folder though.

Unless you are at the command line you won't be able to see /usr/local.

Sorry I let this get out of hand. This thread belongs to the OP, ChaOConnor. Anybody else who wants help with this should start a separate thread for themselves.

And don't forget that linux is case sensitive, so if you have entered something that differs in upper/lower case it is a different path, and you can only use paths that are mapped.

And you didn't successfully tag him above. You must select from the list that appears after you type the @ Just getting the characters '@binhex' in the post won't get it done. You have to have @binhex

A more likely cause isn't the mappings of the dockers, it is the settings within a docker application. You must make sure that the applications are set to write only to mapped storage.

And you really, really want to set this up. I have been asking for a way to get users to notice this feature for a very long time. Most of the time when we get a user with multiple disk problems, they never set up Notifications because they just didn't know about them. They were running with one problem disk for a while and didn't even know about it until they got another problem disk and so parity couldn't help them anymore.

Then you probably have lots of bots trying to login right now.

Have you read the section of the Docker FAQ about "Docker Image Filling Up"?

3 plugins which might be useful to you. Active Streams, File Activity, and Open Files. You can get them from Community Applications of course.

You can specify the plex version as documented in both the Docker hub and github links in the first post of this thread.

Since user shares are simply the top level folders on cache and all array disks with the same name, any file at the top level of a disk; i.e., not inside a folder, isn't in any user share, and so no user share rules can be applied to them. Unless you are sharing disks on the network or letting some app directly access disks (I don't recommend either of these), the files aren't accessible except at the command line.

This is not the correct path to disk1. It is at /mnt/disk1. /mnt/disks/disk1 would be an Unassigned Device you had mounted and named disk1. Or possibly a folder created in /mnt by some misconfigured app. Does that path even exist on your server?

Do you have any files at the top level (not in a folder) on any of your disks?

Tools - Diagnostics, post complete zip

Tools - Diagnostics, post complete zip.

The Use cache setting for each user share is the builtin solution for your problem, and is much more flexible than a global "disable mover". You can disable mover for any specific user share simply by setting it to cache-only (new writes will go to cache) or cache-no (new writes will go to array). There is also cache-prefer, which will move from array to cache. I can understand temporarily wanting to prevent mover, but that can be accomplished simply by changing its schedule so it doesn't run before you want. To permanently disable it for a user share, use the appropriate setting for the user share.

Windows / SMB only allows one connection. If it has already negotiated a connection, it won't use another, even though it prompts for credentials.

Go to config/plugins folder on your flash drive and delete the .plg for Advanced Buttons then reboot. But even before doing that, read the update notes for updating to 6.5. You may have other things that need to be changed for the new version. See here: https://lime-technology.com/forums/topic/66327-unraid-os-version-650-stable-release-update-notes/