Squid

Harmless. Probably user scripts

There's only 5 entries in cron. You've got 6 You may have to give it the full path to rsync /usr/bin/rsync That hasn't worked for quite a while. You would need to put the .cron into the dynamix folder and then call update_cron (or use the user scripts plugin)

I don't sleep my servers, but the first thing to do would be to see if the dynamix s3 plugin works for you

I think its more that we need to see the error message that sonarr is giving. But, I think that the issue is more Don't use torrents, but I would think that sonarr can't move a file that's currently in use by seeding.

Should be fixed next release of unRaid

In a nutshell you can't. unRaid doesn't have the GPU drivers installed. You could use a VM and passthrough the GTX to it and then run in the VM if Plex supports supports the GPU (don't use Plex, so can't say)

TLDR: @bonienl, issue here is that cron on slackware/unRaid doesn't seem to support ranges (and seems to not be consistent in that not every field allows comma separated values either). Revert the simplification commit on Sept 8 (https://github.com/limetech/webgui/commit/d07fec0c6ff594783ef0eff1544d3299e57ff7d6#diff-c74d37c40da2052f6f1e7778412b87db) and everything will work fine. @limetech, this is a bug even though the cron entry appears to be correct. Just happened to have noticed that mine never ran either (on both my servers) While I can't 100% guarantee that both servers wasn't being reset or something when the last parity check was scheduled to happen, it never ran. Just to test, I've changed it to 2nd week # Generated parity check schedule: 0 22 8-14 * 5 /usr/local/sbin/mdcmd check &> /dev/null || : an 11 21:55:01 ServerA emhttpd: req (11): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog Jan 11 21:55:01 ServerA emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Jan 11 21:55:01 ServerA crond[1659]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Jan 11 21:55:20 ServerA root: plugin: running: anonymous Jan 11 21:59:51 ServerA emhttpd: req (12): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog Jan 11 21:59:51 ServerA emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Jan 11 22:00:02 ServerA root: Cache used space threshhold (70) not exceeded. Used Space: 38. Not moving files Jan 11 22:00:42 ServerA kernel: CIFS VFS: Close unmatched open Jan 11 22:01:06 ServerA kernel: mdcmd (62): spindown 0 Jan 11 22:01:07 ServerA kernel: mdcmd (63): spindown 1 So you can see that it never actually ran. if I however change the cron tab back to the original method you were using to run in the first / second / third / fourth week, it does work fine. # Generated parity check schedule: 15 22 * * 5 [[ $(date +%e -d -7days) -le 7 ]] && /usr/local/sbin/mdcmd check &> /dev/null || : Jan 11 22:15:01 ServerA kernel: mdcmd (64): check Jan 11 22:15:01 ServerA kernel: md: recovery thread: check P ... Jan 11 22:15:02 ServerA kernel: md: using 8192k window, over a total of 3907018532 blocks.

Install Community Applications https://forums.unraid.net/topic/38582-plug-in-community-applications/ and forget about the docker repositories section, the add container button, etc.

Docker Tab - Advanced View

Too late

What's wrong. The description is just that - a description of what the mapping is for. If the template authors don't enter in a description in English, then it's on them, not up to unRaid.

So much for the next plugin I started working on: CA unRaid Hacks

Or you could probably add this as a repository on the docker page https://github.com/Josh5/unmanic/tree/master/docker

Nothing to do with CA at all. Based on the error, it does appear that you have corruption on the flash drive, or it dropped offline. I would try the stick in another port, ideally USB2

Correct

Because port mapping only works in bridged mode.

Probably the argument would be that the statement as above is actually correct. Nothing says that you can't isolate a core and then have a container(s) run on it. The problem lies when multiple cores are isolated and the container is then pinned to those multiple cores. (as an aside, the Fix Common Problems plugin does catch this error)

If the mappings are like /media <--> /mnt/user/MediaServer/ Read only /dvr <--> /mnt/user/MediaServer/PlexDVR/ Read write Then, Any attempt to access the plexDVR folder within the container via /media/PlexDVR will result in read-only access Accessing the plexDVR folder via /dvr will result in read-write access

Add to ignore list. And, IMHO if you're using FCP, then it being out of date is an error as you're going to be missing out on fixes, new errors / warnings / etc.

Starting with unRaid 6.7, plugin authors have the ability to add in another entity into the .plg file to allow the plugin to display a font-awesome icon on the Plugins Tab <PLUGIN name="&name;" author="&author;" version="&version;" launch="&launch;" pluginURL="&pluginURL;" icon="refresh"> This will show the icon fa-refresh on the plugin page. For compatibility with previous versions of unRaid though you should still have the appropriate png in the Images folder. This is optional. If the icon attribute doesn't exist, the status quo remains in effect Additionally, for pretty much all of the v6 series, you have also been able to specify a font-awesome icon for the .page file's settings. Menu="Utilities" Type="xmenu" Title="Auto Update Applications" Icon="refresh" Will display the fa-refresh icon on the settings page for the AutoUpdate plugin. To utilize those icons within the Community Applications plugin (versions after 1/5/19), add another entry to the xml (For compatibility with previous versions of CA the <Icon> entry should still be present with an appropriate URL link. Once again, optional. If IconFA isn't present, CA will use Icon. ** CA has been changed so that a font-awesome icon can be utilized in the <Icon> entry. Technically, this deprecates <IconFA>, but that method is still supported. <IconFA>refresh</IconFA> You can also utilize the new unRaid specific icons (I'll leave it to you to discover them once 6.7 gets released) by using (on any of those entries) the full name of the icon. (But obviously, those new icons will not display on unRaid versions prior to 6.7)

Unpacking and repairing if necessary are also hugely cpu intensive tasks. By default, if 2 (or more) docker containers each require 100% of the CPUs available, they will split the resources. You may be able to get better performance from Plex in this circumstance by not having it be able to use Core 5. Beyond that, I'd look at prioritizing Plex over NZBGet https://forums.unraid.net/topic/57181-real-docker-faq/?page=2#comment-566087. Don't run Plex, so can't really comment upon its CPU requirements. It might also help to have an unassigned drive storing the intermediate files instead of the cache drive (where the media may be located also) to remove bottlenecks on the drives from the equation.

load average: 12.78, 8.63, 4.32 Cores: 6 NZBGet is doing something, and Plex is also doing its thing. Right now, the processes are being starved for CPU (load avg of 12), and if you grabbed the diagnostics while watching the CPU utilization, it is consuming the bulk at the moment. This isn't about the odd spike here and there. You want to know whats going on when every core is hitting 100% and sits there. At that point you want to grab diagnostics, or start scrolling through the various charts in NetData so you can easily see what's going on.

The overall loads are still fine. Once its unpacking and reading / writing all the files, you can expect other cores to also go up as unRaid, the drivers etc still have to handle the actual reads / writes. load average: 1.07, 0.92, 1.05 Cores: 6 Its what is going on when everything seems to be stuck at nearly 100% that we're interested in seeing what's going on.

Doesn't appear to be. Its the way the container is designed. Talk to MS

Installing NetData and leaving it running in another tab would be great as you'd be able to see graphs (at least from the point you installed it)