Squid

If you want to always run the latest, greatest, (and occasionally bug ridden) version of Plex, then you should instead ru the version from linuxserver.io Sent from my NSA monitored device

rename /config/network.cfg on the flash drive, reboot and see if that makes a difference (your server however will revert to DHCP though if you've assigned it a static DHCP in settings - network)

Just for future reference, (and for anyone else that reads this post), forget that the "Docker Repositories" tab ever exists. You'll never use it if CA is installed. Unfortunately, for various reasons (none of which make sense to me) that section is part of unRaid's GUI, and I am not in the mood to have CA actually delete it.

Tools - Diagnostics

Your best bet is to set up the syslog server (Settings - Syslog Server) to mirror to the flash drive, and then wait for another crash. After recovering, then upload that syslog.

At what point did it cut in half? There's no real fundamental reason why 6.7.2 would have dropped the speeds down. On the other hand, there are a million reasons why external influences would cut it down (other programs scanning the media, writes to array, etc) If you stop all other apps, what speeds do you get after it runs for a few minutes? You can also always install the parity check tuning plugin which will ensure that a check only runs in the middle of the night and will resume the next night.

How so? As a general rule, appdata (and that's the only path mapping that has relevance here) is confined to either the cache drive (use Cache: Prefer), or a single disk for performance reasons. In that case, there is fundamentally zero difference between referencing it as /mnt/user/appdata or as /mnt/cache/appdata That being said, this issue is a priority for limetech.

Your external Buffalo has file system corruption, and you need to Check Disk Filesystem on it (probably need to do it via command line) Jun 30 03:10:40 downloadbox kernel: XFS (sdc1): Corruption detected! Free inode 0xc36fd4cf not marked free! (mode 0x81ff) Your cache pool is nearly fully allocated, and you need to fix that up (Probably a FAQ about that one) Device size: 476.97GiB Device allocated: 462.97GiB Device unallocated: 14.00GiB I would also consider limiting the memory resources of the various docker apps to see if your out of memory situation improves

Fix Common Problems is telling me that Write Cache is disabled on a drive. What do I do? This test has nothing to do with any given unRaid version. For some reason, sometimes hard drive manufacturers disable write cache on their drives (in particular shucked drives) by default. This is not a problem per se, but you will see better performance by enabling the write cache on the drive in question. To do this, first make a note of the drive letter which you can get from the Main Tab Then, from unRaid's terminal enter in the following (changing the sdX accordingly) hdparm -W 1 /dev/sdm You should get a response similar to this: /dev/sdm: setting drive write-caching to 1 (on) write-caching = 1 (on) If write caching stays disabled, then either the drive is a SAS drive, in which case you will need to utilize the sdparm commands (google is your friend), or the drive may be connected via USB in which case you may not be able to do anything about this. 99% of the time, this command will permanently set write caching to be on. In some rare circumstances, this change is not permanent, and you will need to add the appropriate command to either the "go" file (/config/go on the flash drive), or execute it via the user scripts plugin (with it set to run at first array start only) It should be noted that even with write-caching disabled this is not a big deal. Only performance will suffer. No other ill-effects will happen. NOTE: If this does not work for you, then you will either need to contact the drive manufacturer as to why or simply ignore the warning from Fix Common Problems

Its coming from your UPS. https://forums.fedoraforum.org/showthread.php?285005-quot-hid-generic-control-queue-full-quot-from-apcupsd

All the errors are from python which is 100% nothing to do with mover or the plugin, unless mover is attempting to move something that your python script doesnt like being moved Sent via telekinesis

Impossible to do. I *suppose* I could check the date updated that the authors put in for the change logs, but since many / most authors don't do this because of their builds updating themselves every Friday at 23:00 GMT, it's rather pointless

@limetech I just managed to corrupt my sqllite db's on both Radarr and Sonarr (never checked Plex at the time it happened though). I have always used /mnt/user/appdata for everything, and I do not have any problems. But, in the course of testing something out for another user here, I enabled DirectIO (was previously at auto). With that enabled, the db's immediately crashed. After I noticed the corruption, I reverted DirectIO back to "No", and everything fired up correctly. Hopefully this is a data point you can use in solving this problem. Diagnostics attached which covers everything [v0.2.0.1344] NzbDrone.Core.Datastore.CorruptDatabaseException: Database file: /config/nzbdrone.db is corrupt, restore from backup if available. See: https://github.com/Radarr/Radarr/wiki/FAQ#i-am-getting-an-error-database-disk-image-is-malformed ---> System.Data.SQLite.SQLiteException: disk I/O error disk I/O error EDIT: Should actually clarify that no actual corruption happened. SQLite thought it was corrupted if DirectIO was enabled. With it disabled, everything came back alive with no issues servera-diagnostics-20190629-2304.zip

At least I'm off the hook to answer

You won't. It's the hardware causing it. It's pausing all I/O on other drives connected to the same controller waiting for the drive to spin up. Extremely common issue, and zip you can do about it.

Settings - Disk Settings, Use Spin Up Groups Then each individual drive from main, give it a named group (like "Movies", "TV", etc) Best solution is to increase the caching on the player(s). Kodi you can easily do this. Not sure about plex

Restart in safe mode

What version did you upgrade from? If there is a dynamix.plg file within /config/plugins on the flash drive, then delete it and reboot. Also try clearing out your browser's cached files in its history

This would be your starting point https://forums.unraid.net/topic/70951-how-to-stop-array-from-terminal-not-shutdown-server/?tab=comments#comment-651510

Screen shot?

None of this little discussion belongs in this thread, but it is what it is. But, every single user of CA has had to acknowledge this:

docker is weird with log rotations. The global setting (Settings - docker) only takes effect on new installs. Any existing installs aren't affected and need the extra params. It may be academic now, but by nuking docker.img, all the installs became "new", and wouldn't need the extra param if you had set up the global. There was a debate on GitHub about how to handle things because it isn't anywhere near intuitive how the system works on logs.

Some users have had a similar experience throughout 6.7 and their solution was to delete / rename /config/network.cfg on the flash and reboot. This will revert the system back to DHCP, etc so you will have to set it back up to your own preferences.

Not the real expert, but it seems to me that Windows will have its own mitigations installed via updates which will override these on the VM. You can also disable them via googling.

Top secret