Squid

Click on the docker's icon and select More Info. On the docker hub page it should say the last time the container was built

Yeah, it's not a bug, but by design. Trouble is that there were so many users copying / pasting scripts from the forums here and doing that introduces other unwanted characters into the script, that all non pure ASCII characters were removed. I'll revisit next week.

Your docker.img is read only. Best to open a new thread with your diagnostics. (And reminder to myself to cut off the message a bit )

@ljm42

Your memory is actually 2133 overclocked to 3200 https://www.gskill.com/specification/165/185/1567584549/F4-3200C16D-16GIS-Specification

Is the boot order correct?

Probably best to to ask about this here

YMMV. Some users have no problems with Marvel based controllers, others have nothing but problems. You will always have the best luck with LSI based (say a 9201 or Dell Perc H200) flashed into IT mode. You can find them very reasonable on ebay as server pulls (but beware of ones bought from China as the odds are good that they're counterfeit

You've changed the network type from the default bridge to instead be host, which has the effect that all port mappings are ignored.

Full diagnostics are always better, but the issue is Dec 6 11:51:22 Tower kernel: BTRFS info (device loop2): bdev /dev/loop2 errs: wr 2283, rd 0, flush 0, corrupt 0, gen 0 Dec 6 11:51:22 Tower kernel: BTRFS info (device loop2): start tree-log replay Dec 6 11:51:23 Tower kernel: BTRFS critical (device loop2): corrupt leaf: root=2 block=340262912 slot=37, unexpected item end, have 3426207789 expect 15062 Dec 6 11:51:23 Tower kernel: BTRFS critical (device loop2): corrupt leaf: root=2 block=340262912 slot=37, unexpected item end, have 3426207789 expect 15062 Dec 6 11:51:23 Tower kernel: BTRFS: error (device loop2) in __btrfs_free_extent:6805: errno=-5 IO failure Dec 6 11:51:23 Tower kernel: BTRFS: error (device loop2) in btrfs_run_delayed_refs:2935: errno=-5 IO failure Dec 6 11:51:23 Tower kernel: BTRFS: error (device loop2) in btrfs_replay_log:2281: errno=-5 IO failure (Failed to recover log tree) Sight unseen without diagnostics, you have to delete and recreate the image. https://forums.unraid.net/topic/57181-docker-faq/#comment-564309

Definitely. While it's the unofficial way of doing things, its usually far far faster to zip up appdata locally move it to the array and then replace the drive and unzip it (ala Appdata backup plugin)

Not how I use $_POST. I've never played with them when reloading the page

If you're managing everything through portainer, add the line I listed to the templates. The xmls are there

Is the warning that Template URL is missing or wrong? If so, manually edit the xml in /boot/config/plugins/dockerMan/templates-user and change (or add) <TemplateURL>false</TemplateURL>

The diagnostics don't cover Sundary the 29th. Post new diagnostics Monday AM

@SpencerJ

Only way that the particular issue with the folder should ever happen is if some script or something you're running is deleting the contents of /tmp (eg: transcoding to RAM with Plex and your mapping is /tmp)

A screenshot of the settings, and your diagnostics covering that time period would be needed

Then during the shutdown, the system forced a processes that was tying up the system to close.

Are they in the middle of an update being installed? (Auto Update plugin)

smdion deprecated it. Nothing says you can't continue to utilize it if its working fine for you

Finally got the time to fix this today

Settings - Scheduler - Mover Settings

Any chance you've plugged into a management port instead of the ethernet port on the T20 (if it has one)? Check the BIOS to make sure its enabled Maybe the weather also took out your NIC

It is on the never ending bucket list to have it support any event.