trurl

You are getting the "terms" backwards from our perspective. The "array" is the individual disks protected by separate parity disk(s) using Unraid's implementation of parity. There is only one array. The array is optional on recent Unraid versions. The array is for HDDs and they don't have to be the same size but none can be larger than parity. XFS is the default filesystem for the array disks but others are allowed. "Pools" are disks assigned outside the array. There can be zero or more pools, each can have one or more disks. Usually SSDs are used in pools, but HDDs are allowed. Multdlisk pools must be btrfs or ZFS. User Shares are the combined contents of array and pools. This is how Unraid allows folders to span.

Attach Diagnostics ZIP to your NEXT post in this thread.

Have you done that since those last diagnostics? Might be useful to see syslog that includes those activities.

Docker troubleshooting | Unraid DocsThis page offers troubleshooting guidance specifically for Docker containers on Unraid, managed by the Unraid team. For advanced troubleshooting, in-depth technical details, or topics beyond the Unrai

That backup is your configuration, including the drive assignments when the backup was taken.

Do you have a flash backup from before you started these changes?

Before we actually try to fix your dockers, let's get your appdata off the array. Ideally, Docker/VM related shares - appdata, domains, system - should have all files on cache or other pool, with nothing on the array, so Docker/VM will perform better, and so array disks can spin down since these files are always open. domains and system already have no files on the array, but appdata does have files on the array. Mover won't move those files because appdata has no Mover action, because it has no Secondary storage. Set appdata to Primary:cache; Secondary:array; Mover action:array->cache. Nothing can move open files. Go to Settings and disable Docker. Run Mover, wait for it to complete, post new diagnostics.

Just some advice on using the forum. When you edit a previous post, anybody that has already read the post, and might be willing to help (such as me) will not know there is anything new to see in the thread, and so may never visit the thread again unless someone actually does make a new post in the thread. That is why I said

Do you have a current flash backup?

If not, just restarting plex will update it. If you don't know, post docker run

Attach Diagnostics ZIP to your NEXT post in this thread.

Attach Diagnostics ZIP to your NEXT post in this thread.

Correct, "this device" is referring to the parity drive.

If it's working I guess it's OK. Not unusual to see some "error" lines on bootup as Unraid probes the hardware. The colors are completely based on keywords appearing in the line, such as "error". Do you have a current backup of the boot flash?

Looks OK, I guess you can use it again.

Which "official doc" is that? I don't recall anything about sysprep in Unraid documentation.

OK, let's go back to this This seems to indicate some problem listing the contents of the subfolder in user shares. Maybe we can narrow it down to the array or the pools. What do you get from command line with this? ls /mnt/user0/data/media/tvand this? ls /mnt/download/data/media/tvand this? ls /mnt/ssd_cache/data/media/tv

This shouldn't cause your problem, but you might try to fix it anyway: Apr 8 16:50:33 MHSTower root: Fix Common Problems: Warning: Share data set to use pool download, but files / folders exist on the ssd_cache poolSimplest way would be to use the built-in File Manager

What do you get from command line with this? ls -lah /mnt/user/data/media

This is a few years old but maybe something there for you:

Why?

Nothing can move open files. You have to go to Settings and disable Docker and VM Manager before mover can do that.

The host path /var/log has nothing to do with those containers assuming the mappings you specified above.

OK, not public, but also not private https://en.wikipedia.org/wiki/Private_network#Dedicated_space_for_carrier-grade_NAT_deployment

How is a computer with a public IP address able to login to your server? Apr 7 16:19:35 Tower webgui: Successful login user root from 100.93.240.74