Squid

Got you beat... Sept 2018... Of course I'm long since done with reading every thread.

Is it just me, or is unread not showing anything new since ~5 hours ago? @SpencerJ

Sorry. Didn't look closely enough. It's the WED that's causing it to never run. Change it to be 3

If you see the flash as one of your shares on the server over the network, then just delete it the same as you would any other file. If you don't (you don't have the flash drive exported), then from the command prompt rm /boot/config/plugins/advanced.buttons.plg

Try getting rid of the spaces

No

There's nothing particularly wrong with that speed (the maximum sustained speed that drive can do it 190MB/s) But, you have to bear in mind that every drive slows down the closer they get to the end. Since you have a mixture of smaller drives (you mentioned 4TB, but implied other (presumably smaller) drives), then those slowdowns slow down the speed until the check is past those drives and no longer needs them. As an aside, more and more people run the parity check in bursts overnight via the parity tuning plugin, so it doesn't particularly matter how long it takes because it's only running at times when nothing else is happening for a couple of hours a night.

Have you tried disabling it and XMP if only to rule it out?

General rule is that if it boots fine then you don't need to worry about it. But, when you get into VM's and passing through certain video cards, then booting via EFI (ie: renaming the folder to efi and selecting the UEFI boot in the bios) then you might have better success.

Your diagnostics will say why in the log

Not sure if you're aware or not, but your last link is an Expander, not a controller. (It requires a controller to operate)

Is there a question there?

Works perfectly for me.... Anything weird in your system? (DockerHub conversions etc?) Try without any browser extensions...

Known issue. Should be fixed next release. In the meantime, you can also try another browser

Technically it is still valid, but the screenshots are way out of date. But it is still far easier to simply go to Apps and then Previous Apps.

Same reason why you drive on a parkway, park on a driveway and get ticketed if you do the opposite. It's simply a misnomer commonly in use here (same thing as referring to the container itself as a "docker")

Huh? If you're talking about an error from FCP telling you to remove advanced buttons from your server, then the file is in the flash drive /config/plugins/advanced.buttons.plg

Don't install it from Apps - Previous Apps (or the Add Container) Just search for nzbget in apps But, what you're describing doesn't particularly make a ton of sense either.

FAT32 is required. Most BIOS you actually select the flash drive to be the first boot device in the Hard Drive boot order section.

Only difference in terms of problems is if a particular piece of hardware needs to have the power actually cycled to it to solve it's issue instead of merely a reset.

Your vdisk share (presumably where you've got the vdisk mounted for the VM) exists on the cache drive and on disk 1 / 2. On which drive is the vdisk for the VM actually stored? On the array will have a huge performance impact.

Post your diagnostics (Tools - Diagnostics)

Pretty much anything the OS kernel is capable of mitigating is already being done (with the exception of disabling SMT). These are valid attack vectors for malicious players to make use of to possibly determine the contents of a memory location which the program doesn't have access to. Realistically though, even if you were running a bank in your house, the odds of actually discerning any private information that would be of use is very (very) low, but not zero. A financial institution has no choice but to close all possible vectors. As a normal user it's up to you. The performance hit (depending upon what the kernel has to do etc) is up to 15%. With the power of CPUs being what they are, you may not even notice it. TLDR: Don't worry about it.

You said "low quality". Forgetting Plex as there's a million reasons why quality degrades when you're transposing and streaming remotely. Using Kodi you're on your own LAN, so no transposing is involved and it just plays the file as-is. So, you're down to quality of the source, settings on the video card, settings on the TV, etc. LAN problems with Kodi would usually be Buffering, or blockiness etc.

Certain combinations of hardware (and on occasion having a wife who thinks that well-done (and with ketchup) is a perfectly acceptable way to eat a steak) will issue an MCE when initializing the processors. Completely normal and harmless to ignore. This is happening to you (hopefully not your wife though -> as then you've got real problems)