Squid

Absolutely And when you win I will lower my customary fee and only insist upon 10% Sent via telekinesis

Yeah, it's getting ridiculous now. So for Spectre / Meltdown. First you have to have the appropriate malware running locally on your server. (Which BTW, they have never found a single instance of). Then, it has to perform its attack, which will absolutely let it gather what ever info happens to be in the CPUs cache at the time. But, what exactly are the odds of the information that is actually of any value being in the cache at the exact same time as it runs? Sure, it can request to look at all of the memory locations in your server, and then determine what all the contents are. But, is it going to be able to actually discern what is a password or not? What is simply code? What is simply part of your movie file cached? I mean, I don't know about you, but I tend to not have in ram the phrase: "blahblahblah is my password for RoyalBank, and my account number is 1234". Sure, it's all possible that it will get a password (if you happen to have one stored on your server, and it is in RAM at the same time). But what exactly are the odds? My feeling is that I'd probably win the lottery two or three times before those attack vectors could discern and analyse anything meaningful from my system. But, the story is different for something like a bank where personal info would constantly be in a cache. Let them take the potentially 30% hit in CPU speed. Myself, I'm going to keep on buying lottery tickets. I'll bet you I come out ahead.

Fine

Thank @cybrnook. I never would have thought you could disable the mitigations if it wasn't for him.

My Settings Tab is getting too full IE: I don't know. Just where I initially thought it would go. Initially I was going to stick it next to Syslinux Configuration under Flash Settings, but since I can never easily remember where exactly syslinux settings is in the first place, I figured that was a pointless place to put it.

Disable Security Mitigations Thanks to @cybrnook's research (https://forums.unraid.net/topic/80235-disabling-spectremeltdownzombieload-mitigations/), this plugin will disable the OS mitigations for Spectre, Meltdown, and Zombieload (MDS) to possibly give you better CPU performance. Note that these mitigations are valid security concerns, and depending upon your workload you may want them mitigated. Myself, I'm not running a bank out of my house, and I don't think that the odds are too great that Plex would ever implement a Meltdown hack on my server to try and figure out my passwords (which doesn't exist anywhere on the server in the first place), so I'd just as soon have my CPU power back. That, and spectre et al are all proof of concept hacks. But disabling these mitigations is definitely one of the "Use at your own risk" type of thing. If your lawyer gets hauled before a FISA court, and can't tell you why, and you've wound up being transported off to another country where all sorts of things can be done to you simply because it's not on American soil all without due process, then don't blame me. Find it in the Apps tab by searching for Disable Security Mitigations, and then go to the Settings Tab (User Preferences), Mitigation Settings (6.7.0+ only) Note that the plugin will only disable the mitigations for your default boot mode. All other boot modes are left untouched (ie: Safe Mode will have all mitigations enabled). Also, while the plugin isn't required per se to be installed once the mitigations are disabled, uninstalling the plugin will automatically re-enable all of the mitigations.

Up shot is that maybe at the end of this, someone can tell me why I'm so special (no jokes @CHBMB)

I can tell you that on any of the usual suspects for /mnt/user vs /mnt/cache (plex, sonarr, radarr, etc) I have never had any issues with using /mnt/user (and continue to do this today). While this is an issue, it does not affect everyone for some unknown reason.

If you compare the docker run command returned when you try it via a template vs what you're entering in manually, you'll see whatever mistake there is.

Zero reason to do this on unRaid. There's nothing that you can do via the CLI that you cannot do from the Add Container on the docker tab, and by by-passing the template system you may lose functionality in managing the containers via the GUI

huh?

Looks like your template is setup to use a custom bridge (br0) by default. You should adjust your github template to instead be host

https://forums.unraid.net/topic/42808-plugin-templates-for-ca-appstore/

You should post updated diagnostics, krusader logs, and the docker run command

Suppressed it. The error is harmless Sent via telekinesis

Future as per the OP Parity sync/Data rebuild/Check pause/resume capability. Main functionality in place. Pause/resume not preserved across system restarts yet however. Sent via telekinesis

Sure. No problems. But you will invalidate parity 2 by re-assigning drives to disk 1, disk 2 etc

So true 👍. But like CHBMB said, I personally wouldn't use the RSS. I do however read the blogs (or at least skim them)

Try today's update

https://en.wikipedia.org/wiki/RSS_(disambiguation)

There are circumstances (in particular the parity swap procedure) where if that happened, but the backup happened before the procedure then after restoring you are guaranteed to lose data. So, it's not going to happen. Personally, whenever I've done this I just print out the DISK_ASSIGNMENTS.txt and simply reassign the drives accordingly

Replicated. Sorting it out...

Show me the output of these commands: hdparm -W /dev/sd* and hdparm -W /dev/nvme0n1

Before doing that, change the reference to /config on Plex to be /mnt/disk1/appdata/....

Not correct Your issue seems to be one that affects some users (definitely not all) where some applications do not like the reference to /config (edit the container(s) and then click show more settings) and switch /mnt/user/appdata to instead be /mnt/cache/appdata If this is the case, then you will run into this problem on any version of unRaid.