BRiT

If you track it up to some command "docker-containerd-shim" you can determine which exact docker container it is by matching container id prefixes. Notice how "9e837294036f" matches between the output of Docker Process and the overall Process output: ps -axf 13248 ? Sl 0:00 \_ docker-containerd-shim 9e837294036f29839277d497a83be3e1996df00ba63af497daacbb78229062f2 /var/run/docker/libcontainerd/9e837294036f29839277d497a83be3e1996df00ba63af497daacbb78229062f2 docker-runc docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9e837294036f emby/embyserver:latest "/init" 7 weeks ago Up 31 hours EmbyServer

ps -auxf or the following if the above expands too wide to be seen on your terminal screen, and try to find the 'sh' process by process id and see what process tree it belongs to. ps -axf

As stated in other threads, Stop your plex docker and any other dockers that may be scanning the system until after your unbalance operations finish.

You need to specify the exact previous version in the TAG field instead of "latest". I'm not sure if all dockers have each version tagged, but they really should, to make it easy to get back to exact moments in time. LinuxServer has their docker images tagged properly, so pick a moment in time that used to work for you. Perhaps 158 or 157, or even earlier depending on what version you were running before you updated when things ran fine. https://hub.docker.com/r/linuxserver/plex/tags Latest = 159, updated 7 days ago. Previous = 158, updated 14 days ago. Previous Previous = 157, updated 21 days ago.

Advice is to revert the plex server docker to the previous version.

Please pardon what is likely an extremely silly and basic question from someone who has not used Google's My Drive or Team Drives at all (I apologize to no one!): Wouldn't one have to pay an additional monthly fee for each additional user for Team Drive (to improve your daily upload limits)?

Very hackish, but it seems to work to for 3 and 4 character octal permission maps: stat -c "%a %n" * | awk '{print substr($1, length($1)-2, 3), $2}'

I had SUID/SGID initially on my array as it was setup from before and I think one of my downloaders had it set. You could use the following to get octal permissions and take the right-most 3 character of the first portion (not shown below): stat -c "%a %n" * Or more verbose to compare between Octal and Human Readable form: stat -c "%a %A %n" *

Soon™

Have you tried running a SCRUB on the Docker Image from the GUI? http://tower/Settings/DockerSettings

To assign the drive into the variable named DRIVE, using " " and $() to evaluate the command and take the output. DRIVE="$(df | grep /mnt/disk | awk 'NR == 1 {line = $6; min = $3} NR > 1 && $4 < min { line = $6; min = $4} END { print line}')" Then to see the result you could do: echo ${DRIVE} You should then be able to refer to that variable in your command ... rclone ${DRIVE}/rclone_upload/google_vfs/ gdrive_media_vfs: -vv --drive-chunk-size 512M --checkers 3 --fast-list --transfers 2 --exclude .unionfs/** --exclude *fuse_hidden* --exclude *_HIDDEN --exclude .recycle** --exclude *.backup~* --exclude *.partial~* --delete-empty-src-dirs --fast-list --bwlimit 15500k --tpslimit 3 --min-age 30m Using ECHO to see what the command expansion would be: echo rclone ${DRIVE}/rclone_upload/google_vfs/ gdrive_media_vfs: -vv --drive-chunk-size 512M --checkers 3 --fast-list --transfers 2 --exclude .unionfs/** --exclude *fuse_hidden* --exclude *_HIDDEN --exclude .recycle** --exclude *.backup~* --exclude *.partial~* --delete-empty-src-dirs --fast-list --bwlimit 15500k --tpslimit 3 --min-age 30m Produces the following output: rclone /mnt/disk2/rclone_upload/google_vfs/ gdrive_media_vfs: -vv --drive-chunk-size 512M --checkers 3 --fast-list --transfers 2 --exclude .unionfs/** --exclude *fuse_hidden* --exclude *_HIDDEN --exclude .recycle** --exclude *.backup~* --exclude *.partial~* --delete-empty-src-dirs --fast-list --bwlimit 15500k --tpslimit 3 --min-age 30m So I think putting it together to only do the drive with least free: DRIVE="$(df | grep /mnt/disk | awk 'NR == 1 {line = $6; min = $3} NR > 1 && $4 < min { line = $6; min = $4} END { print line}')" rclone ${DRIVE}/rclone_upload/google_vfs/ gdrive_media_vfs: -vv --drive-chunk-size 512M --checkers 3 --fast-list --transfers 2 --exclude .unionfs/** --exclude *fuse_hidden* --exclude *_HIDDEN --exclude .recycle** --exclude *.backup~* --exclude *.partial~* --delete-empty-src-dirs --fast-list --bwlimit 15500k --tpslimit 3 --min-age 30m

Try the following... df | grep /mnt/disk | awk 'NR == 1 {line = $6; min = $4} NR > 1 && $4 < min {line = $6; min = $4} END {print line}' We shouldn't use df -h because it switches units, from TB to GB. Column 4 of "df" is Available Space. Column 6 of "df" is the disk filesystem label. Column 3 would be Used Space, and column 5 would be Percentage Used. Here's my input and output results, split between two steps so you can get an idea for what the first part does before awk is thrown in: # df | grep /mnt/disk /dev/md1 7811939620 4640646784 3171292836 60% /mnt/disk1 /dev/md2 7811939620 7444221980 367717640 96% /mnt/disk2 /dev/md3 7811939620 895848128 6916091492 12% /mnt/disk3 # df | grep /mnt/disk | awk 'NR == 1 {line = $6; min = $4} NR > 1 && $4 < min { line = $6; min = $4} END { print line}' /mnt/disk2

Its possible if you can do some bash scripting. I'd start off with trying to parse output of df or similiar command for the disks of interest before trying to parse out specific columns. It might beging to look like this ... "df -h | grep /mnt/disk", and probably fed through "awk" scriplets to calculate min free and associated disk #. Im not sure if it would be /mnt/disk# or /dev/md#. Im away from the server now so I can't try running this to get better script code.

Using Google DNS is safe. Putting your unraid server on the internet is not safe.

Unannounced Reaction announced here... 🎯

As said earlier, Select more than 1 DESTINATION drive.

MOCA adapters are also very flexible and may provide higher throughput than powerline adapters. The only requirement is to have COAX cables to use.

What settings do you have on Windows? If you have display thunbnails enabled then opening Windows Explorer will always cause a disk to spin up, as WinExplorer will read contents of files. CacheDir can only cache filenames, not file contents.

No.

Not a bug at all. Thats how spaces or special characters are escaped in Linux command lines. It's that or surrounding everything in double quotes.

You need to specify RAW in the URL when linking to the PLG. Try using: https://raw.githubusercontent.com/arberg/dynamix/master/unRAIDv6/dynamix.cache.dirs.plg When I used the URL without the RAW, what I got was an HTML file, with the first bits looking like this: <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <link rel="dns-prefetch" href="https://assets-cdn.github.com"> <link rel="dns-prefetch" href="https://avatars0.githubusercontent.com"> <link rel="dns-prefetch" href="https://avatars1.githubusercontent.com"> <link rel="dns-prefetch" href="https://avatars2.githubusercontent.com"> <link rel="dns-prefetch" href="https://avatars3.githubusercontent.com"> <link rel="dns-prefetch" href="https://github-cloud.s3.amazonaws.com"> <link rel="dns-prefetch" href="https://user-images.githubusercontent.com/"> <link crossorigin="anonymous" media="all" integrity="sha512-DMUv06uA9jcLpuzWEnwuWTuYn/1rt3UmOKgIrS5ESQLJtqWQzexcD85XhWhAk0wcGQmlhspauIq+6Hjmue1A5g==" rel="stylesheet" href="https://assets-cdn.github.com/assets/frameworks-1291ffafdf7ffb4d9be67d690fd09212.css" /> <link crossorigin="anonymous" media="all" integrity="sha512-T7Yq7rbiCzjLhP8CjEZRSSk/MBGeGhrW/1qjEVxq3LRxojFj+lZBb+irUNAsx12/UMTqKfO4++C5RoVNxAoJtQ==" rel="stylesheet" href="https://assets-cdn.github.com/assets/github-040328cdcb5f37143588d5b5e7893ba5.css" />

Might be interesting, if not entertaining: The Fuck https://github.com/nvbn/thefuck

If adding MergerFS ( https://github.com/trapexit/mergerfs ) one will likely also want all of MergerFS Tools ( https://github.com/trapexit/mergerfs-tools ) and Scorch ( https://github.com/trapexit/scorch ) too.

No.

Try running the "docker safe fix permissions" tool.