Squid

Remove the -n flag and re run

Add the --rebuild-tree to the command options like it suggests Sent from my NSA monitored device

Post the output from when you run the filesystem check on 7

Jinx

All port mappings are ignored when a container runs on its own dedicated IP. You will always use in your case 3000

Your UPS is reporting TIMELEFT is 0 seconds (ie: Time Left on Battery), so unRaid is handling everything correctly (because your settings says shutdown if there's less than 10 minutes remaining) You might want to try the NUT plugin and see if that makes any difference.

/media is the default for the container path. However if the host path on the template is /mnt/user, then you won't see any unassigned device. To do that, you need to change the host path to be /mnt. All of this of course assumes that you're using Unassigned Devices plugin. Yes. Via the unassigned devices plugin.

Might help if you also post a screenshot of the UPS details section

SMART attributes are only read every 30 minutes by default in the UI (Main / Dashboard) for performance reasons. This can be changed in Settings - Display Settings under Poll Attributes

Not sure what the error is all about, however it should be noted that depending upon how you copy the appdata folder for plex it can balloon exponentially in size due to Plex's very extensive use of hardlinks.

search https://hub.docker.com/

I don't run random commands, so not going to particularly analyze what you typed in, but will say that the script included with User Scripts that does the same thing is this: find /mnt/user -maxdepth 9999 -noleaf -type f -name ".DS_Store" -exec rm "{}" \; As far as recovering, you can pull the drive and attach it to your Mac and then install and run (and unfortunately pay for) https://www.ufsexplorer.com/ufs-explorer-standard-recovery.php (I've run this on Windows and it works great (albeit I used it for a different reason) )

correct You really should consider after fixing the problem switching the file systems to instead be xfs

Today's update should fix (and by that I mean damn well better fix) the occasional problem with some users and the "Scanning" popup never disappearing. One side-effect of the fix though is that now the minimum unRaid version required for FCP is 6.7.0 Upshot is that *if* for some reason the popup now never goes away, the test hanging will be displayed in the popup.

Main, Boot Device, SMB Security. Try setting it to be Public

The raw list is here. Doesnt look anywhere near as good, but will show you everything https://forums.unraid.net/topic/36282-all-unraid-application-template-repositories-support-threads/ (Thread and linked HTML still exists because I can't convince the powers that be to un-sticky it )

It looks like you've breathed on the SATA connectors too much (at the best of times its a very poor design). Reseat ALL cabling to the drives (both ends).

It is being emulated, but since it has corruption and is currently unmountable you won't see it's contents Did you stop the array and restart in maintenance mode?

It's rebuilding the drive. Until that happens, the disk's contents is invalid.

Yeah, but the main thing is that the diagnostics doesn't grab a "rotated" version of the docker log. I'll be getting around to fixing that in the next day or so.

You won't. As soon as an app is on its own separate IP address, all port mappings are meaningless as the container will utilize whatever ports that it chooses (ie: the default ones) IIRC there is an issue with the webUI entry when using an app on it's own IP. Either bookmark the appropriate URL in your browser, or try enabling authoring mode in settings - docker (you have to stop the service first), and explicitly specify the appropriate URL in the webUI entry (advanced view)

Highlighting the relevant info The container path doesn't match between deluge and sonarr

That would be my guess

Problem with the first part is that the docker.log in the diagnostics is empty. Best recourse right now is a reboot and then monitor the situation. Fix Common Problems will alert you if / when /var/log starts getting close to maximum size

Oct 2 13:05:15 WOPR kernel: EDAC sbridge MC1: HANDLING MCE MEMORY ERROR Oct 2 13:05:15 WOPR kernel: EDAC sbridge MC1: CPU 8: Machine Check Event: 0 Bank 9: 8c000051000800c1 Oct 2 13:05:15 WOPR kernel: EDAC sbridge MC1: TSC 31c3e6d31eaaa Oct 2 13:05:15 WOPR kernel: EDAC sbridge MC1: ADDR 73e0a2000 Oct 2 13:05:15 WOPR kernel: EDAC sbridge MC1: MISC 90004000400228c Oct 2 13:05:15 WOPR kernel: EDAC sbridge MC1: PROCESSOR 0:206d7 TIME 1570035915 SOCKET 1 APIC 20 Oct 2 13:05:15 WOPR kernel: EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#1_Ha#0_Chan#0_DIMM#0 (channel:0 slot:0 page:0x73e0a2 offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c1 socket:1 ha:0 channel_mask:1 rank:0) Memory issue