BRiT

I can delete my own posts, but not sure if that's time-limited capabilities. I'm not sure if that capability is granted based on length of time registered, number of posts, or all approved members have it.

I can't find anything anywhere at all on how to even get back to a "hidden" post. It doesn't even show up in your activity history from your own profile. Curious feature. Not seeing the usage scenario(s) for it. 👀

Have you found the Seek Button yet? Deja-Vu.

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

I had developed my dockers over a year ago in WinOS and never had any issues like you're having, so I cant help you at all, except to say that doesnt seem typical at all. Try using a non-special directory like "c:\docker\" instead of putting it on your desktop or documents.

Another way of adding the commands is through CA User Scripts. Its much easier to manage than manual GO file changes.

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.

You could copy the file to another share (if you have any other shares configured) if the other shares are configured and accessable. cp /boot/logs/tower-diagnostics-*.zip /mnt/user/destinationshare

Whitelist your server in your browser addons and your Antivirus programs.

No. Parity is always the full drive size.

No. Absolutely not. Wrong thing to do.

It updates the Parity Drive(s) as if the write(s) to the data drive happened. Then when you replace the faulty drive and the system is rebuilding the drive, it reads from all the other data drives and parity drives to calculate what the data should be for that drive.

The easiest tuners to use will be the ones that do not requires to be plugged into the server, they function over ethernet. This way you wont even need special editions of unRaid. For the US market this means SiliconDust HDHomeRuns. I'm not sure exactly which model for UK DVB usage. Try searching on network DVB.

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.

Post your diagnostics from when a parity check is being run. Have you tried adjusting your Tunables?

Have you adjusted your unraid tunables when on 6.6.5 to see how it impacts parity times?

AFAIK, CA Backup would never reboot the server.

Yes. Simply use the command line, and issue direct 'docker' commands. That will create and generate your own docker image. For instance after you create your "Dockerfile" with what commands and items to do, you create the image by telling docker to build docker build -t friendlyhello . There is no need for a GIT Repo unless you want to possibly share the source. If you want to share the final docker image then you will need a Docker Hub account to push the finalized image. For those unfamiliar with it, here's the Docker starting guide: https://docs.docker.com/get-started/ Part 2 goes over how to build your own Docker.

They really shouldn't be doing so as user "ROOT". If Limetech wants it to be a suitable desktop then please make the needed changes to provide real user accounts to be used as that purpose.

Your perspective is skewed -- unRaid is not a desktop, it's a server.