trurl

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

After you get your user shares cleaned up, it would be very helpful to us if you would delete any .cfg files in the config/shares folder on flash that are no longer being used so they don't get included in your diagnostics in the future.

If anything writes a top level folder to any of the disks, that folder is automatically a user share, named for the folder, whether you intentionally created it as a user share or not. Any user share you haven't made settings for gets default settings. Incorrect host paths when setting up dockers can have this result.

Technically these are dockers. Plugins are something else and they are installed at boot using the .plg files in /boot/config/plugins

See this "Need Help" sticky pinned near the top of this same subforum for some ideas on how to get us more information: Do you have a current backup of flash?

If you really need a quick fix for plex then forget about doing it on Unraid. Ideally, plex would be the last step in all that. You need to get the basic Unraid setup done before you try to add things to it.

I'm afraid that txt file you attached is just about as hard to work with as that list of 84 anonymized share .cfg files in your diagnostics. Actual screenshots might have been better, unless you want to take the trouble to reformat that text file so the columns line up. I see it does already have the "Compute" done though, which is a good addition. Or maybe we can just clean it up so there isn't so much to deal with and get another look. You can remove a user share by getting rid of all of its contents (moving or deleting). Then you will be able to delete the share by clicking on it and it will let you delete it from its page. Just one note of caution. You must never mix disks and user shares when moving or copying files. Linux doesn't know the disks and user shares are just different views of the same files, so it will let you try to write over the source file and it gets truncated. Only work with user shares, or only work with disks. Never both at the same time. The user shares are simply the aggregate of all top level folders on cache and array. They are located in /mnt/user. The disks are at /mnt/disk1, /mnt/disk2, ..., /mnt/cache (if you had one)

I see you already have Community Applications installed. That is how you need to work with your dockers on Unraid. I see you don't currently have a cache drive or pool. Cache is not required, but there are some advantages of cache besides speeding up user share writes. In particular, your docker (and VMs) can stay on cache where they will perform better and won't keep array disks spinning. I always recommend installing cache before setting up dockers (and VMs) so all that gets created on cache to begin with. It can be a little extra trouble getting them moved to cache later. Were you planning to have cache in the near future?

Your diagnostics says you have had various different user shares, 84 in all, so that is quite a mess. Unfortunately, that count also includes .cfg files for user shares you might have had in the past but no longer have any files. Go to Shares - User Shares and post one or more screenshots as needed that shows all of your current user shares. That will help me narrow things down somewhat since I don't even get the complete names in your anonymized diagnostics, and as I said, probably some of those in the list don't exist now.

You shouldn't even be using the command line for managing your dockers on Unraid. Personally, I recommend using the linuxserver or binhex plex. They are much better supported on this forum. And there are some advantages if you use multiple dockers from the same authors since they will have some code in common and will download / update faster and take less space in docker image. I use mostly linuxserver dockers myself, and those are the ones I am most familiar with. Give me a few minutes to analyze your diagnostics and I will post a response about that. Some patience will probably be required to get thing working optimally.

No that is wrong. I don't know if you can get any help on the Plex forums with basic understanding of how to setup dockers, and if your shares are a mess, then the first thing to do is clean that up instead of setting up dockers based on messed up shares. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

The host part of that mapping, /mnt/user/disk4/movies, is wrong, or at least it should be wrong, since /mnt/user is where your user shares are, and you shouldn't have a user share named disk4.

Are you actually using the official plexinc docker, or some other? Do you have any other working dockers? Post the docker run command as explained at this very first link in the Docker FAQ:

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

yes. All files on the existing disks will be there, and all shares will be there since they are just the top level folders. A2 You don't mention the size of your existing parity disk, but of course no data disk can be larger than any parity disk, so if each parity isn't at least 10TB then you can't add a 10TB data disk. You can actually do all of it at the same time. Parity will just be built based on the assigned disks regardless of their contents. Doesn't matter if they are clear or have random bits or actual files. And formatting (writing the empty filesystem to the new disk) in the array will update parity at the same time (since it is a write operation), so parity will still be good. As I already mentioned, be sure you don't accidentally assign a data disk to any parity slot, or it will be overwritten with parity. And before formatting the new disk, make sure all the existing disks are showing their filesystem and size. In other words, make sure they aren't unmountable, since format applies to all unmountable data disks. If you have that problem come back for further advice on repairing unmountable filesystems.

An even bigger question is why have you been having problems with docker image? Filling docker image is almost certainly due to misconfigured applications, 20G should be more than enough, and it shouldn't grow. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

You can go directly to the correct support thread for any of your dockers by simply clicking on its icon and selecting Support. Usually there will be some documentation links in the first post of the support thread that will explain how to setup the docker, including choosing a particular version.

Your shares problem is almost certainly due to the cache problem, since cache is part of the user shares. /mnt/user is the user shares, which isn't there, but /mnt/user0 is the user shares excluding anything on cache. Probably that docker image on disk1 is newly created and the one you were using was on cache. You should disable dockers until you get your cache fixed, and delete that docker image so when you enable dockers again it will be recreated on cache where it belongs. In any case, docker image is unimportant and easily recreated. It is just the downloaded executables of your applications. Without the appdata and the templates (see next paragraph) it is useless, and with the appdata and templates the executables will just be downloaded again. Not sure about your Previous Apps. It works from the docker templates on flash, but if your user shares aren't working I'm not sure how it would behave. And in any case you don't want to mess with any of that until you fix cache. You can see those templates in /boot/config/plugins/dockerMan/templates-user. There is no need to recreate any shares. The user shares are simply the aggregate of all top level folders on cache and array, and if your cache were good they would still be there. Another possibility would be to remove cache completely if you just want to reassure yourself, but I don't recommend enabling docker that way since you would have to do some extra work to get all that moved to cache when you get cache going again.

Did you have backups of anything on cache, such as appdata backup with the CA Backup plugin? Setting up your dockers again with the same mappings etc. isn't hard. You can use the Previous Apps feature of the Apps page for that. But without appdata the applications themselves would be starting from scratch.

WireGuard

Your array data is likely OK, but looks like cache pool isn't, and that is likely the cause of any docker or user share issues. Were you following some FAQ about converting your cache pool? Never tried anything other than raid1 with 2 identical SSDs personally. @johnnie.black is the expert and wrote the FAQ procedures on cache pool. Maybe he will reply.

There are enclosures with SAS or eSATA connections. Best if you get something without port multipliers. You don't want to connect multiple disks with a single eSATA port, for example.

The only way I would consider USB connections for anything except Unassigned Devices is for a system where parity or cache isn't used at all, such as backups only. Otherwise you are just going to be constantly rebuilding due to disconnects.

According to that docker run you posted you were using the "official" plexinc docker, which doesn't have a support thread on this forum.