Squid

Something is weird with your flash drive. (Corrupt?) On boot up, it was downloading every plugin over again (which it shouldn't be as they're all stored on the flash). That happened until it looks like the network got completely initialized at which point it started doing network failures. Quite honestly, I'd switch your DNS servers from the ones your ISP wants you to use to something like 208.67.222.222 / 208.67.220.220 to bypass any problems that they might be having (my experience has always been that ISP's DNS servers suck at the best of times, even beyond that fact that by using them you're simply helping them track where and what you're doing) Might not solve the problem, but after that I'd suggest deleting /config/network.cfg (or renaming) on the flash drive to see if things work via the defaults.

Your share B....p exists on the cache drive. Did you change it's Use Cache Settings? Since it's currently set to Use Cache No, it won't ever get moved. You need to change it to Use Cache Yes, run mover and then set it back to No when Mover is finished

@hugenbdd took over this plugin a while ago. The thanks on the current iterations go to him.

Apr 7 22:08:12 fs emhttpd: /mnt/cache mount error: No file system Apr 7 22:08:12 fs emhttpd: shcmd (48): umount /mnt/cache Apr 7 22:08:12 fs kernel: XFS (sdi1): Invalid superblock magic number Run the File System Check against the cache drive

It says CPU #1, Channel #0, Dimm 0. Your system event log in the BIOS may have more information

If the system has to kill off processes that are holding up the shutdown process, then this happens. Could be as simple as a a command prompt sitting somewhere within /mnt/user, or could be a container that refuses to stop. A lot of time, it's a Windows VM (in Settings - VM settings, set the system to hibernate everything during shutdowns, and install the virtio guest tools on the VM)

yup

What does it show when you hit Container Size on the Docker Tab

It's recommended to use the unraid.net plugin to handle the flash backup (even if you don't use the remote access features) All the templates are stored on the flashdrive and are included in the backup. Depends what you're doing to customize the container. If you're actually changing files within the container (ie: docker exec...), then yes that's not backed up and if you ever update the container you will have to re-apply those changes. If you are making the changes within the /config (appdata) path, then that is backed up via the appdata backup portion of the plugin.

And they're in there now.

I know. Talking with the guys on which one of them to remove.

Then probably none of those icons were appearing at all.

How long have you waited? One of the quirks of the UI is that if autostart is enabled, then the UI is not available until after every thing is actually started (docker, VMs). It appears that from the time emhttp started until the end about 2.5 minutes elapsed. Failing that, try the system in safe mode.

The logs are being filled because you've got atop installed via NerdPack. It's notorious for that.

https://forums.unraid.net/topic/103802-unraid-os-version-691-available/page/5/?tab=comments#comment-961668 Looks to be a browser issue....

Your System Event Log in the BIOS should also have more info.

Apr 5 19:27:20 barkbox root: Memory ECC error occurred during scrub Apr 5 19:27:20 barkbox root: Memory corrected error count (CORE_ERR_CNT): 1 Apr 5 19:27:20 barkbox root: Memory transaction Tracker ID (RTId): 83 Apr 5 19:27:20 barkbox root: Memory DIMM ID of error: 2 Apr 5 19:27:20 barkbox root: Memory channel ID of error: 0 You have memory issues. The other mce that you referenced is semi-normal, happens to a fair amount of users when the OS initializes the cores. That one can be safely ignored.

I can guarantee that I've never updated FCP to take into consideration other cache pools beyond "cache". Will update it in the next few days.

I believe that's by design, as the system looks at the naming to determine how to handle it.

If I think about it, I'll take a pic of my BIOS, as you've also got to set T1 and T2 IIRC

The one absolute thing you want to do is NOT setup up plex to transcode to /tmp. You want it to transcode to /tmp/Plex. Within /tmp there are multitudes of other files and folders and the system does not respond very well if Plex decides to delete them.

How much memory do you have in the server? This appears to me to be a RAM completely full issue.

On the 10th Gen motherboards, damn near every one of the manufacturers is setting them up as an "Unofficial" overclock out of the box by allowing the CPU to run as hot as it possibly can by not following the rules on what Intel states. Look at this