Squid

Definitely memory Aug 21 15:58:11 Tower1 kernel: EDAC sbridge MC0: HANDLING MCE MEMORY ERROR Aug 21 15:58:11 Tower1 kernel: EDAC sbridge MC0: CPU 20: Machine Check Event: 0 Bank 5: cc026a8000010092 Aug 21 15:58:11 Tower1 kernel: EDAC sbridge MC0: TSC 0 Aug 21 15:58:11 Tower1 kernel: EDAC sbridge MC0: ADDR 85a848b80 Aug 21 15:58:11 Tower1 kernel: EDAC sbridge MC0: MISC 2440169686 Aug 21 15:58:11 Tower1 kernel: EDAC sbridge MC0: PROCESSOR 0:206d7 TIME 1598047091 SOCKET 0 APIC 9 Aug 21 15:58:11 Tower1 kernel: EDAC MC0: 2474 CE memory read error on CPU_SrcID#0_Ha#0_Chan#2_DIMM#0 (channel:2 slot:0 page:0x85a848 offset:0xb80 grain:32 syndrome:0x0 - OVERFLOW area:DRAM err_code:0001:0092 socket:0 ha:0 channel_mask:4 rank:1) Your BIOS' event log may have more information on the exact location of the affected DIMM (dimm 0, channel 2)

Per the link, you can also prioritize the container. Setting the shares to 1024 and everything else to 2 gives that container the highest priority and everything else the lowest.

yes

For more advanced usage, you can google docker run reference

Are those diagnostics from a state when /mnt/user is empty?

Update or remove the docker folder plugin

You should post the full diagnostics. Far more info in them.

Because Unraid unpacks the appropriate files from the flash drive when it boots up. If you save the appropriate downloaded file onto the flash drive, and then at boot up time (via user-scripts plugin), you run a script that will install it.

You've set the minimum freespace for the share to be 749GB. Until the disk 5 reaches that point, all copies to the TV share will go to disk 5, not disk 6

ALL software is beta

You should post the diagnostics (Tools - Diagnostics), as it gives far more information. But, unless you're running with very little RAM, this Aug 16 10:06:44 Unraid root: Fix Common Problems: Warning: Rootfs file is getting full (currently 77 % used) is something that is effectively an error

Yeah, the mappings don't match between the two containers for the downloads (data) folder. Review the linked post by @trurl. https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=566086

What are you looking to move? the docker.img file or the appdata? If it's the docker.img file, then simply stop the docker service (settings - docker), delete the file, and then set the location to where you want and restart the service, followed by apps, previous apps, check off what you want and grab a coffee / tea / beer (depending upon the time of day) If it's the appdata, many ways to accomplish what you want, but what I would do is make a backup of it via the appdata backup / restore plugin, then change the SOURCE within the settings for the plugin, and then restore the backup set you just created.

Those speeds are more or less inline if you have a parity enabled share. Once the memory cache gets filled, the speed will always drop down to those speeds-ish. Enabling turbo write (reconstruct write) in disk settings will speed things up, at the expense of all drives must be spinning.

I would try a different port on the switch if only to rule it out.

Tried a memtest yet? Maybe also update to 6.9-beta25. (Later Kernel)

Docker - Add Container, select your template https://forums.unraid.net/topic/57181-docker-faq/?tab=comments#comment-566084

AFAIK, you would have to create a custom docker bridge via the command line to allow this. Google would be your friend.

You should update to beta 25 Your problem with R&N is most likely https://forums.unraid.net/topic/57181-docker-faq/?tab=comments#comment-566086

Not going to address the webUI thing as it seems to be a very common problem with plex across all platforms and systems, but the port mappings is quite normal. With any app running via host networking (which this one does), the concept of port mappings doesn't exist, so there's nothing to populate,

Press the "?" in the top right corner of the screen to bring up the inline help when on the Unassigned Devices page, which should answer your questions.

This shouldn't change, as it's your host IP. (The 172.x.x.x address will change). Referring to host:port is the usual way of doing things.

On the flash drive, if you delete the contents of /config except for super.dat and the .key file then you are starting over again, with the exception that you will not have to reassign your drives.

First off, it only shows up when you're within fix common problems, not every where within the OS. If you've got a problem with me putting up an unobtrusive banner when youre within the settings for one of my minor plugins simply because I happen to have a conscience then I dont care and my advice is to get over it.