Squid

UPDATE: I found a little cubby hole that's not covered by any of the cameras and does have a bench seat from a van in it, so I'm temporarily safe from having to work. Just need to find a blanket now

I don't mind so much when this happens if its a weekend and I'm at home. Worst case I watch a chick flick with the wife. But this one has happened while I'm at work. Can someone PLEASE advise me on what I'm supposed to do now?!?!? And please don't tell me to actually earn my paycheck.

There's actually 2 sections for ignored errors 1st section is Ignored Errors. These are errors / warnings which are still present, but are ignored ie: will not send out a notification, but may still log it depending upon the settings 2nd section is All ignored errors. These are errors / warnings which have been ignored in the past but may not still be present. Also should be noted that any and all errors listed (and the 1st section of ignored) is from the last run of the tests. If another run hasn't happened on a schedule or you haven't clicked Run Tests, then those errors will remain...

That's a complication The history of that v is that originally the version numbers were 1.x, 2.x etc Because of the auto update plugin, the author kindly changed it to vYYYY.MM.DD so that auto update could do it's thing on it. Unfortunately now if the "v" gets removed, then unRaid will never find an update available for it, since on a comparision vYYYY.MM.DD is always greater than YYYY.MM.DD ie: You've just got to deal with it

??

First thing I do after releasing an update is to attempt to upgrade to it. I saw my boo boo before any of you. Unfortunately the server that hosts every plugin for unRaid has caching, so it takes ~10 minutes for my fix to actually take effect.

lol You guys got hit in the 10 minute window where that mistake of mine was there. It's fixed now. If it doesn't install, a reboot and a reinstall will work

Today's update is about checking for the security issue mitigations detailed below Two errors are possible: unRaid version 6.7.0 to 6.7.2 - Install the plugin via the apps tab as detailed in the above link. (You would have also received a separate warning that your OS version is out of date - Ideally, unless there is a compelling reason for you to remain on the unRaid version you are using, it is highly recommended to upgrade to 6.8.2+) unRaid version greater than 6.7.2 and less than 6.8.1, the advice is to upgrade your OS to 6.8.2+ Again, you would have also received a separate warning advising to upgrade your OS NOTE: the mitigation plugin will ALSO help secure your server if you are running any unRaid version of 6.6.x Unfortunately, Fix Common Problems requires unRaid 6.7.0 to operate, so no warning / error will be sent if you are still on those older versions of unRaid. I always advise users to keep their OS and plugin versions up to date with the latest stable version.

Probably the extra cores will be ignored. Worst case is an error will happen on the docker run

Just so that there's no confusion, this plugin has nothing to do with any security mitigations done by Limetech ie: Sysdream This plugin will only disable the mitigations for Spectre, Meltdown, et al and will NOT disable the mitigations discussed below

All my quick tests show that this should work no problems for you. Anything weird going on I should know about? Can you install any other docker app?

@binhex is the one to ask

Post the full URL that's in the browser bar when this happens (but edit out the hash value before unraid.net)

Also, either tonight or tomorrow an update to Fix Common Problems will be issued which will flag an error on affected systems if you do not have this plugin installed. See here

Available within CA. Either go to the new apps section or search for sysdream or limetech. If it doesnt appear, then you're not running a version of unraid which the plugin will work on (or isn't needed - 6.8.1 / 6.8.2)

What version of CA

It's definitely something with your network setup, and all the bridges you've got, but that's out of my realm of expertise @bonienl

Just so we're clear, is that error showing up when you click the reinstall default icon (ie: showing up within CA), or afterwards after the template shows up? And, if it's afterwards, is the template screen that pops up populated or empty?

Locking this, as it's probably more suitable for the CA thread where this q is also posted

Top of my head, not sure. I'd have to play around and see if there's an edge case that's resulting in that...

And if you have a file name dynamix.plg on the flash drive (/config/plugins), delete it.

The only reason for drive(s) not being read during a parity check / build is that they are smaller than the parity drive and the system has already passed the size of the drives. Share includes / excludes never affect parity operations

The VW Microbus of flash drives: https://www.newegg.com/p/0BD-00MW-000H4?Description=dtse9&cm_re=dtse9-_-9SIA12K2N94425-_-Product There is no substitute for this one within unRaid. It'll never die

To get it out of the way, have you deleted those mounts within UD and then recreated them? and does the WD support SMBv1?

I can guarantee its not CA causing you trouble with the flash drive dropping offline. CA is arguably the stablest thing you can install on your server. The only thing that it does which under your normal use case is write a file to the flash drive indicating that you've accepted the CYA (and a write will also happen by changing any setting within unRaid). It sounds more like whenever any write happens to the flash is when your system decides to drop it. I've had no problems with any flash drive I've used with unRaid, but you do always have to use a quality brand, and not one that you've ordered from China, as counterfeits of Kinston et al flash drives are rampant.