Squid

You don't need to worry about categories or anything. Sab will pass through to sonarr the full path including the category. So long as the host path matches between the two. Right now, Sab says that a download is sitting at /data/category/TVShow.mkv This works out to a host path of /mnt/user/Downloads/Complete/category/TVShow.mkv Because the mappings don't match between Sab and Sonarr, sonarr is effectively looking for the file at /mnt/user/Downloads/Complete/Complete/Sonarr/category/TVShow.mkv And the file is obviously not there.

You host mappings on the /data do not match between the apps

Yes, the host paths are the same between the two. But on the template, what is the container path for each of them? Or post the docker run command for each. https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345

https://forums.unraid.net/topic/57181-real-docker-faq/page/2/#comment-584226

Personally, instead of pinning this I prioritize every other docker app to take precedence over this. https://forums.unraid.net/topic/57181-real-docker-faq/page/2/#comment-566087

Not that I have a DVD/BD attached to the server, but it should be with the = https://forums.unraid.net/topic/57181-real-docker-faq/page/2/#comment-566100

Doesn't affect anything, but in order to change it then you would have to do a Tools - New Config and reassign the drives accordingly.

Can you confirm that you're running v2019.10.06 Also, has anything ever showed up underneath the "... This may take a minute.." What browser are you running?

It's all good. Just keep navigating up the directory tree (..) until you get to / then go to media and you're on your array.

Have a single script that runs and calls each sub-script in turn

And what is the container path for Sabnzbd?

There is no "latest" tag for the container. The instructions you posted say to use a tag of 1.7.0-stretch (ie: repository entry is bpatrik/pigallery2:1.7.0-stretch)

Oct 7 16:07:09 c3server root: Fix Common Problems: Error: Machine Check Events detected on your server Oct 7 16:07:09 c3server root: Hardware event. This is not a software error. Oct 7 16:07:09 c3server root: MCE 0 Oct 7 16:07:09 c3server root: CPU 1 BANK 0 TSC 16c2e70e506 Oct 7 16:07:09 c3server root: TIME 1570489448 Mon Oct 7 16:04:08 2019 Oct 7 16:07:09 c3server root: MCG status: Oct 7 16:07:09 c3server root: MCi status: Oct 7 16:07:09 c3server root: Corrected error Oct 7 16:07:09 c3server root: Error enabled Oct 7 16:07:09 c3server root: MCA: Internal parity error Oct 7 16:07:09 c3server root: STATUS 9000004000010005 MCGSTATUS 0 Oct 7 16:07:09 c3server root: MCGCAP c09 APICID 2 SOCKETID 0 Oct 7 16:07:09 c3server root: MICROCODE 21 Oct 7 16:07:09 c3server root: CPUID Vendor Intel Family 6 Model 58 Quick googling suggests internal cache on the CPU. Are you overclocking?

The real key thing here is to reseat everything to the drives and mobo. Sata connectors aren't very robust, and the slightest touch when you're replacing a drive can cause this.

https://forums.unraid.net/topic/57181-real-docker-faq/page/2/#comment-566095

If you've made a backup of the appdata, then restore it. All of the settings for the templates though are on the flash drive, and will be restore-able via Apps - Previous Apps

That's 30 minutes Not saying its the issue, but if the drive is spun down at the time it goes to read the temp, it will be skipped over, and only read when the drive is spun up and the 30 minute timer is reached.

What drive are you expecting for it to see? WDC_WD20EURS-73TLHY0_WD-WCC4M018541 is showing up but not assigned to a slot.

Yeah, FCP will complain about that. But it's not valid and a false positive (that I never considered and will ultimately have to pop out an update to FCP to handle it -> although that'll be a catch-22 as you won't be able to install the update to stop the false positive) Eventually, most of my plugins will gradually be gravitating over to requiring 6.7+ as the fix that went into FCP is a far better way of handling certain things that the various plugins do. The next plugin queued up for me to fix is Cleanup Appdata. Followed possibly by Appdata Backup/Restore. I'd love to add the change into CA itself, but can't actually justify putting it in when there's no issues with it.

Because you set it to be 60GB in Settings - Docker. Not a problem in and by itself, but most users only require 20GB. In order to lower it, Settings - Docker - Disable the service Delete the image Change the image size to be 20GB Restart the image Apps - Previous Apps, check off all of your apps you want and hit install

It won't let you upgrade to the new version. But, when on 6.6 the plugin system will continually let you know an upgrade is available even though you can't upgrade to it (this behavior was fixed in 6.7.x)

I would think that you didnt try to actually read any file on the pulled drive. The read would have failed, which means that an immediate attempt to write to the drive would happen (which would obviously fail) which would trigger a notification (assuming you've set them up) Sent from my NSA monitored device

General rule with binhex containers is that they do not auto update. If / when the update gets pushed to whatever repo he pulls from then an update to the container gets pushed Sent from my NSA monitored device

And, any attribute which is listed as FAILING NOW

use -L usually theres no data loss