jademonkee

Hi there, This morning I received the following errors from my (recently rebuilt) server: Event: Unraid Disk 2 error Subject: Alert [WILLOW] - Disk 2 in error state (disk dsbl) Description: TOSHIBA_HDWG180_90G0A17XFAUG (sde) Importance: alert and Warning [WILLOW] - array has errors Array has 1 disk with read errors I immediately shut it down. I am of the mind that those errors are usually a loose cable, and I only recently built the server (moving my HBA and disks from an old one), so I assumed that was the problem, so I opened up the case, checked the power and SATA cables for the disk and rebooted. After starting the array, it says that the disk is being emulated. Though I then received the notifications: Warning [WILLOW] - udma crc error count is 74 TOSHIBA_HDWG180_90G0A17XFAUG (sde) and Notice [WILLOW] - array turned good Array has 0 disks with read errors As the disk was being emulated, I assumed it must still be a bad connection, so I shut it down and tried a different connector on my HBA card. It still says it's emulated. However, I can run a SMART test on the disk (it says it passed - report attached), so it must be connected, right? And if the SMART test passed, how come it still says that the disk is emulated? What do I do now? Do I make Unraid accept the disk? Or is the disk dead and I buy a new one? I've seen topics with a similar problem linking to this help article: https://docs.unraid.net/#Rebuilding_a_drive_onto_itself but the link is no longer working, so your insight is appreciated. EDIT: I have found the new URL for it: https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself I don't want to do the rebuild unless it's the right thing to do, though, so I will wait until someone here can confirm that my disk is ok, and that it was more than likely just a bad cable. Diagnostics attached (I was in a panic after receiving the notification, so I didn't think to download the diagnostics before shutting down the server - sorry), as is the SMART report for the disk in question. Thank you for your help. TOSHIBA_HDWG180_90G0A17XFAUG-20250125-0929.txt willow-diagnostics-20250125-0943.zip

Sorry, maybe I wasn't being clear enough: I detailed it in my original post, but it appears to be using my NVMe drive's temperature (as seen in the log - 47C), when I've set it to ignore the NVMe and SSDs in my system. Even though it's correctly showing the HDD temperature on the sensors page/dashboard (33C), the logs show it's reacting to the (much higher) NVMe temperature (47C). Thanks. Re the override: thanks for the clarification.

I think my post has gotten buried in all the talk of the script. I think there's a bug in the way that HDD temperature is being monitored. Am I right in thinking this?

Hi there, I just upgraded my server (see sig) and have been so happy to find this plugin to control my fans. My motherboard supports two cooling zones - Fans 1-5 and Fans A-B - for a total of 7 fans. I have had my server running well with this plugin for a few days, but had my fans connected as follows: FAN_1: CPU (dual fans on a splitter) FAN_2: top front (inflow) FAN_3: middle front (inflow) FAN_4: bottom front (inflow) FAN_5: rear (outflow) FAN_A: SAS Card Fan FAN_B: (none) This is as the motherboard recommended it: FANS 1-5 are for CPU Temp, FANS A-B are for System temp. I had them all set to respond to the CPU temp. Note that the SAS card fan isn't PWM, so just runs at full speed all the time. However, I noticed under heavy IO load that the CPU didn't really rise much, but the HDDs did, so I decided to split the CPU cooler to the FANA & FANB zone (despite what the manual recommends), and the case fans all on the same zone. So now it is set up as: FAN_A: CPU (top) FAN_B: CPU (bottom) FAN_1: top front (inflow) FAN_2: middle front (inflow) FAN_3: bottom front (inflow) FAN_4: SAS Card Fan (non PWM) FAN_5: rear (outflow) I have set the FAN A-B zone to react to CPU temps, and the FANS 1-5 zone to react to HDD temps. You can see my setup in the attached screenshot (please ignore the floating footer - a quirk of the screencap plugin I use). One of my disks is set to never spin down, so I don't need to use the secondary sensor option for HDD temps. However, since moving to the new fan configuration, my case fans now no longer spin down to their lower values (they used to drop to about 140 RPM, sitting mostly at 280 RPM), but now they sit around 500-700 RPM. Taking a look in the ipmifan log, I see the following entries: 2025-01-24 11:04:12 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(23%):CPU Temp(44 °C) 2025-01-24 11:05:12 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(29%):CPU Temp(46 °C) 2025-01-24 11:07:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(26%):CPU Temp(45 °C) 2025-01-24 11:08:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(29%):CPU Temp(46 °C) 2025-01-24 11:10:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(26%):CPU Temp(45 °C) 2025-01-24 11:11:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(44%):CPU Temp(51 °C) 2025-01-24 11:12:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(23%):CPU Temp(44 °C) 2025-01-24 11:15:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(29%):CPU Temp(46 °C) 2025-01-24 11:16:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(44%):CPU Temp(51 °C) 2025-01-24 11:17:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(23%):CPU Temp(44 °C) 2025-01-24 11:20:14 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(32%):CPU Temp(47 °C) 2025-01-24 11:21:14 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(26%):CPU Temp(45 °C) 2025-01-24 11:23:14 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(32%):CPU Temp(47 °C) Looking at the other attached screenshot, you can see that the HDD temp reported by the plugin actually 33C. Though I do have an NVME in my server that is 46. I have unchecked that NVME (and my other NVME and SSDs) from the "Available HDDs" list, so they shouldn't be monitored. Indeed, as the IPMI dashboard shows, they are not. Yet is seems that the Fan Control is still including the excluded NVME drive(s). Can you please confirm if this is the case, or if I have some other setting that needs changing? FWIW, all the case fans are the same Noctua model, while the CPU fans are a different Noctua model. As Noctua fans can go to very low RPMs, I therefore had to set "Lower_Critical_Threshold" (using the config editor) to 0 for all of the fans - otherwise I was getting the pulsing problem where the mobo thinks fans have failed (anoher reason why this plugin has been so valuable for me - thank you). Also FWIW, I've never gotten the network connection to work, but it seems to work fine without it, so I never bothered troubleshooting it to get it to work. FINALLY AND ALSO: Since either the recent plugin update or the swap to FAN A-B, I now have the options to set: High temperature threshold Overide(°C): Low temperature threshold Overide(°C): Fan speed maximum Overide(%): Fan speed minimum Overide(%): Can you explain what these are used for? Is it so that if something goes extremely wrong (ie temps out of control), it will ignore the previously set max fan speed settings to ensure things get cool again? Similarly, if the temp gets unusually cool, it can slow the fans down even further? Thanks for your help, insight, and this great plugin - a real life saver.

Ah good, I was concerned that I straight up couldn't hot plug USB, but if passing through the controller gives the ability to plug/unplug then that's the answer I needed. Thanks. From what little knowledge I have, it looks like I can separate my controllers into those for Unraid and those for the VM without issue (it looks like i have enough IOMMU groups).

I upgraded my server hardware last week, and I'm going to dive into VMs for the first time. I plan to use the server as my Windows desktop. Any idea if/when the VM documentation will be updated to reflect the improvements to Windows VMs in v7? Many thanks. EDIT: I just read this in the documentation: USB hot-plugging is not currently supported, so devices must be attached before the VM is started in order for USB pass through to function. Ummm does that mean I can't plug in USB devices while I'm running the VM? That's a pretty normal thing to do, right? Can I fix this by passing through a USB hub? Or do I have to shutdown my Windows VM every time I want to copy the contents of my camera's SD card? Or do I have to go via unassigned devices or something? Thanks for your help and insight

I'm happy with my Cloud Gateway Ultra. I prefer having the console built in. I suspected that it wasn't quite as fast as my old USG (it doesn't have hardware offloading), but actually I upgraded my server last week (I'm yet to upgrade my forum sig...) and now my Usenet downloads hit the full 103MB/s that a gigabit connection can handle, so I don't actually know why they dropped when I upgraded to the CGU. Maybe just a coincidence? So, yes. If you are happy with spending the money, and are interested in 'unifying' your Unifi experience, then go for it. There's no messing around with external DBs, and you know that the software has been tested on your hardware. If you have any questions, feel free to ask.

FWIW I don't use the Nextcloud Android app to sync my photos/files. I use Folder Sync Pro: https://play.google.com/store/apps/details?id=dk.tacit.android.foldersync.full There's a trial version available. It's more complicated, but more powerful, and offers many more services than Nextcloud. I don't know if you'd prefer it or not, but thought I'd pass the info on. Finally: there is no such thing as a "set and forget" service when it comes to running your own internet services. Like it or not, you're a SysAdmin now and it's up to you to maintain, troubleshoot, and fix the services you run. If you set something and leave it as is, eventually it becomes a security risk, or enough technologies change around it that it's pushed into incompatibility or obsolescence. There's a reason that Google Photos or other cloud services is the preferred approach for most people: they handle all the SysAdmin stuff on your behalf.

Upgrade from 6.12.14 went without a hitch. However, I'm unsure what the overlay2 driver is good for: https://docs.unraid.net/unraid-os/release-notes/7.0.0/#add-support-for-overlay2-storage-driver I use a docker.img file on a ZFS formatted cache pool. Is there any benefit for me to switch to overlay2, or should I just leave it as 'native'? Thanks.

They're effectively the same port nos as mine: type: bridge 172.17.0.10:3483/TCP > 192.168.200.40:3483 172.17.0.10:3483/UDP > 192.168.200.40:3483 172.17.0.10:9000/TCP > 192.168.200.40:9000 172.17.0.10:9090/TCP > 192.168.200.40:9090 You don't have any other Dockers using those ports? I found that I didn't have to delete the old LMS Docker, but it definitely needs to be shutdown. I know on my Unifi equipment I had to allow broadcasting for LMS to work the first time (at least I'm pretty sure I did... maybe that was for Chromecasts...?), but I don't think that any setting in your router/LAN would need to be updated just because you changed the Docker. Still: it might be a good place to investigate. Sorry I can't be more helpful.

Setup has gone well. Lots of manual tweaking was required to get my players back to how they were, but that is to be expected. I am getting this error in the logs (I think after performing a library rescan), however: [24-12-06 14:36:11.3568] Slim::Utils::ImageResizer::__ANON__ (67) daemon failed to connect: No such file or directory I note on this page for a third party image resizer that it states: LMS versions newer than 2023/07/15 try to automatically start a Perl-based resizing daemon, which will conflict with this package. The plugin should disable this, however, this hasn't been tested at all. So I presume the error above is related to that resizing daemon. Is it something you could fix, @dlandon (or is even necessary to)? Thanks.

It's probably only of interest if you have the old Logitech Squeezebox playback hardware. The new v9 gave it a much needed overhaul, interface wise, but it still feels kinda old. I use it because I have about 5 or 6 old Squeezeboxes around the house, and a 50k+ library of music amassed over the years. I'm not interested in streaming services. So it suits my needs well, and has done for 15 years now. Still, if you have a spare Raspberry Pi lying around, you can experiment. And if you like it, the old Squeezebox hardware is pretty cheap on eBay now. Feel free to reach out if you have any questions, either software or hardware related.

Player prefs etc will not carry over. The new support thread tells you how to transfer your favourites, at least. But it also says that it's such an overhaul that you can't just copy the preference directories and have them work. I remember that there used to be a third party plugin that allowed you to save and transfer settings. I have no idea if it will work or not. I've just installed the new version and am about to start setting things up. Wish me luck, heh.

You're a star, thank you!

Super excited for v9. It's been rebranded as as Lyrion Media Server, and it looks like development is quite active again. https://lyrion.org/getting-started/changelog-lms9/ Is it a simple update for this Docker @dlandon? EDIT: just saw this in the documentation. I don't know if it's helpful or not, but I thought I'd pass it on. https://lyrion.org/getting-started/beginners-guide-synology-docker/#migrating-from-lmscommunitylogitechmediaserver-to-lmscommunitylyrionmusicserver

I usually avoid 'latest' tags so that I don't inadvertently upgrade (as sometimes upgrades break things), so I use a version tag (linuxserver/nextcloud:version-29.0.3 - a list of other tags is here). LSIO have built the upgrade scripts into when the containers start, so I'd pin a container version now, and manually change it for next NC version upgrade (and see if it upgrades properly this time). If you have been using 'latest', and have been updating/restarting the Docker image, then it's all been happening in the background, so you should have had upgrades happening without your intervention. I think your initial error message showed that one such upgrade went wrong at some point, but it looks like you've now fixed it.

Hi all. FWIW, I upgraded from a USG to the Unifi Cloud Gateway Ultra last week, which contains its own Unifi Network application. The switch over was really easy, and I'm grateful to have simplified the management of the Unifi Network software. The device was about the same cost as the old Cloud Key v2 (£106 inc shipping), but also includes a gigabit compatible router (my USG needed to have IPS/IDS disabled to handle gigabit internet speeds), and a 4 port gigabit switch. It's a great device!

The method to update changed, yes: you need to change the docker tag to update. If you'd changed the tag and were still getting the "update needed" message, then I'm glad you solved it. If you hadn't changed the tag, then I think your update won't stick next time there is an update to the Docker container (not a Nextcloud update, a LinuxServer.io Docker image update, which happen weekly). So do make sure that your Docker tag and current Nextcloud version are aligned. I'd also avoid using the web upgrade and stick to the Docker method, as that's how LSIO have designed it to work. Stepping outside of that has potential for gubbins, gruffins, and other mischief in your system.

I occaionally get these errors in my Nextcloud v28.0.4 (using MariaDB v10.11.5 ) An exception occurred while executing a query: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-2934029-files' for key 'PRIMARY' 31 May 2024, 1:09:31 pm An exception occurred while executing a query: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-2934029-files' for key 'PRIMARY' 31 May 2024, 12:47:17 pm An exception occurred while executing a query: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-2931449-files' for key 'PRIMARY' 27 May 2024, 4:56:24 pm Does anyone have an idea what they mean, what I can do about it, or how I can find out more information? Many thanks.

Does it? Can you elaborate? I have set my Mac/SMB settings up as per the following post: Which includes vetoing the Mac dot files. I note on the 6.12.6 changelog it mentions fruit changes to help TimeMachine restore. Currently my SMB Extra is as follows: veto files = /._*/.DS_Store/ aio read size = 1 aio write size = 1 strict locking = No use sendfile = No server multi channel support = Yes readdir_attr:aapl_rsize = no readdir_attr:aapl_finder_info = no readdir_attr:aapl_max_access = no fruit:posix_rename = yes fruit:metadata = stream Is there something you recommend I change? Either deleting it entirely (perhaps it's setup by default now?) or anything in particular? Are the recommended settings for Mac OS available somewhere so that I can set them up? Sorry to hijack the thread (I just wanted to respond to the news that veto slows things down), and thanks for your help.

UPDATE: I remembered that I updated the plugin this morning (hours after the backup had run), so thought I'd take a look at all the settings and manually run a backup. All the files are in the new directory, as expected. I don't know what caused it, but it's working as expected now. Please discard my previous post.

My weekly backup ran successfully this morning, however the directory is empty. Logs are as follows: [28.02.2024 05:00:01][ℹ️][Main] 👋 WELCOME TO APPDATA.BACKUP!! :D [28.02.2024 05:00:01][ℹ️][Main] Backing up from: /mnt/cache/appdata [28.02.2024 05:00:01][ℹ️][Main] Backing up to: /mnt/user/Backup/ca_backup_app/ab_20240228_050001 [28.02.2024 05:00:01][ℹ️][Main] Selected containers: DiskSpeed, LogitechMediaServer, MongoDB, QDirStat, Redis, Sonarr, binhex-sabnzbdvpn, gPodder, mariadb-nextcloud, nextcloud, phpmyadmin, plex, radarr, swag, unifi-network-application [28.02.2024 05:00:01][ℹ️][Main] Saving container XML files... [28.02.2024 05:00:01][ℹ️][Main] Method: Stop all container before continuing. [28.02.2024 05:00:01][ℹ️][unifi-network-application] Stopping unifi-network-application... done! (took 8 seconds) [28.02.2024 05:00:09][ℹ️][MongoDB] Stopping MongoDB... done! (took 1 seconds) [28.02.2024 05:00:10][ℹ️][QDirStat] No stopping needed for QDirStat: Not started! [28.02.2024 05:00:10][ℹ️][DiskSpeed] No stopping needed for DiskSpeed: Not started! [28.02.2024 05:00:10][ℹ️][phpmyadmin] No stopping needed for phpmyadmin: Not started! [28.02.2024 05:00:10][ℹ️][gPodder] Stopping gPodder... done! (took 5 seconds) [28.02.2024 05:00:15][ℹ️][Sonarr] Stopping Sonarr... done! (took 4 seconds) [28.02.2024 05:00:19][ℹ️][radarr] Stopping radarr... done! (took 5 seconds) [28.02.2024 05:00:24][ℹ️][nextcloud] Stopping nextcloud... done! (took 5 seconds) [28.02.2024 05:00:29][ℹ️][swag] Stopping swag... done! (took 4 seconds) [28.02.2024 05:00:33][ℹ️][Redis] Stopping Redis... done! (took 0 seconds) [28.02.2024 05:00:33][ℹ️][plex] Stopping plex... done! (took 4 seconds) [28.02.2024 05:00:37][ℹ️][LogitechMediaServer] Stopping LogitechMediaServer... done! (took 3 seconds) [28.02.2024 05:00:40][ℹ️][mariadb-nextcloud] Stopping mariadb-nextcloud... done! (took 4 seconds) [28.02.2024 05:00:44][ℹ️][binhex-sabnzbdvpn] Stopping binhex-sabnzbdvpn... done! (took 2 seconds) [28.02.2024 05:00:46][ℹ️][Main] Starting backup for containers [28.02.2024 05:00:46][ℹ️][unifi-network-application] Should NOT backup external volumes, sanitizing them... [28.02.2024 05:00:46][ℹ️][unifi-network-application] Calculated volumes to back up: /mnt/cache/appdata/unifi-network-application [28.02.2024 05:00:46][ℹ️][unifi-network-application] Backing up unifi-network-application... [28.02.2024 05:00:46][ℹ️][unifi-network-application] Backup created without issues [28.02.2024 05:00:46][⚠️][unifi-network-application] Skipping verification for this container because its not wanted! [28.02.2024 05:00:46][ℹ️][MongoDB] Should NOT backup external volumes, sanitizing them... [28.02.2024 05:00:46][⚠️][MongoDB] MongoDB does not have any volume to back up! Skipping. Please consider ignoring this container. [28.02.2024 05:00:46][ℹ️][QDirStat] Should NOT backup external volumes, sanitizing them... [28.02.2024 05:00:46][ℹ️][QDirStat] Calculated volumes to back up: /mnt/cache/appdata/QDirStat [28.02.2024 05:00:46][ℹ️][QDirStat] Backing up QDirStat... [28.02.2024 05:00:46][ℹ️][QDirStat] Backup created without issues [28.02.2024 05:00:46][⚠️][QDirStat] Skipping verification for this container because its not wanted! [28.02.2024 05:00:46][ℹ️][DiskSpeed] Should NOT backup external volumes, sanitizing them... [28.02.2024 05:00:46][ℹ️][DiskSpeed] Calculated volumes to back up: /mnt/cache/appdata/DiskSpeed [28.02.2024 05:00:46][ℹ️][DiskSpeed] Backing up DiskSpeed... [28.02.2024 05:00:46][ℹ️][DiskSpeed] Backup created without issues [28.02.2024 05:00:46][⚠️][DiskSpeed] Skipping verification for this container because its not wanted! [28.02.2024 05:00:46][ℹ️][phpmyadmin] Should NOT backup external volumes, sanitizing them... [28.02.2024 05:00:46][ℹ️][phpmyadmin] Calculated volumes to back up: /mnt/cache/appdata/phpmyadmin [28.02.2024 05:00:46][ℹ️][phpmyadmin] Backing up phpmyadmin... [28.02.2024 05:00:46][ℹ️][phpmyadmin] Backup created without issues [28.02.2024 05:00:46][⚠️][phpmyadmin] Skipping verification for this container because its not wanted! [28.02.2024 05:00:46][ℹ️][gPodder] Should NOT backup external volumes, sanitizing them... [28.02.2024 05:00:46][ℹ️][gPodder] Calculated volumes to back up: /mnt/cache/appdata/gPodder [28.02.2024 05:00:46][ℹ️][gPodder] Backing up gPodder... [28.02.2024 05:00:46][ℹ️][gPodder] Backup created without issues [28.02.2024 05:00:46][⚠️][gPodder] Skipping verification for this container because its not wanted! [28.02.2024 05:00:46][ℹ️][Sonarr] Should NOT backup external volumes, sanitizing them... [28.02.2024 05:00:46][ℹ️][Sonarr] Calculated volumes to back up: /mnt/cache/appdata/sonarr [28.02.2024 05:00:46][ℹ️][Sonarr] Backing up Sonarr... [28.02.2024 05:00:49][ℹ️][Sonarr] Backup created without issues [28.02.2024 05:00:49][⚠️][Sonarr] Skipping verification for this container because its not wanted! [28.02.2024 05:00:49][ℹ️][radarr] Should NOT backup external volumes, sanitizing them... [28.02.2024 05:00:49][ℹ️][radarr] Calculated volumes to back up: /mnt/cache/appdata/radarr [28.02.2024 05:00:49][ℹ️][radarr] Backing up radarr... [28.02.2024 05:00:58][ℹ️][radarr] Backup created without issues [28.02.2024 05:00:58][⚠️][radarr] Skipping verification for this container because its not wanted! [28.02.2024 05:00:58][ℹ️][nextcloud] Should NOT backup external volumes, sanitizing them... [28.02.2024 05:00:58][ℹ️][nextcloud] Calculated volumes to back up: /mnt/cache/appdata/nextcloud [28.02.2024 05:00:58][ℹ️][nextcloud] Backing up nextcloud... [28.02.2024 05:01:11][ℹ️][nextcloud] Backup created without issues [28.02.2024 05:01:11][⚠️][nextcloud] Skipping verification for this container because its not wanted! [28.02.2024 05:01:11][ℹ️][swag] Should NOT backup external volumes, sanitizing them... [28.02.2024 05:01:11][ℹ️][swag] Calculated volumes to back up: /mnt/cache/appdata/swag [28.02.2024 05:01:11][ℹ️][swag] Backing up swag... [28.02.2024 05:01:12][ℹ️][swag] Backup created without issues [28.02.2024 05:01:12][⚠️][swag] Skipping verification for this container because its not wanted! [28.02.2024 05:01:12][ℹ️][Redis] Should NOT backup external volumes, sanitizing them... [28.02.2024 05:01:12][ℹ️][Redis] Calculated volumes to back up: /mnt/cache/appdata/redis/data [28.02.2024 05:01:12][ℹ️][Redis] Backing up Redis... [28.02.2024 05:01:12][ℹ️][Redis] Backup created without issues [28.02.2024 05:01:12][⚠️][Redis] Skipping verification for this container because its not wanted! [28.02.2024 05:01:12][ℹ️][plex] Should NOT backup external volumes, sanitizing them... [28.02.2024 05:01:12][ℹ️][plex] Calculated volumes to back up: /mnt/cache/appdata/plex [28.02.2024 05:01:12][ℹ️][plex] Backing up plex... [28.02.2024 05:05:29][ℹ️][plex] Backup created without issues [28.02.2024 05:05:29][⚠️][plex] Skipping verification for this container because its not wanted! [28.02.2024 05:05:29][ℹ️][LogitechMediaServer] Should NOT backup external volumes, sanitizing them... [28.02.2024 05:05:29][ℹ️][LogitechMediaServer] Calculated volumes to back up: /mnt/cache/appdata/LogitechMediaServer [28.02.2024 05:05:29][ℹ️][LogitechMediaServer] Backing up LogitechMediaServer... [28.02.2024 05:05:45][ℹ️][LogitechMediaServer] Backup created without issues [28.02.2024 05:05:45][⚠️][LogitechMediaServer] Skipping verification for this container because its not wanted! [28.02.2024 05:05:45][ℹ️][mariadb-nextcloud] Should NOT backup external volumes, sanitizing them... [28.02.2024 05:05:45][ℹ️][mariadb-nextcloud] Calculated volumes to back up: /mnt/cache/appdata/mariadb [28.02.2024 05:05:45][ℹ️][mariadb-nextcloud] Backing up mariadb-nextcloud... [28.02.2024 05:05:50][ℹ️][mariadb-nextcloud] Backup created without issues [28.02.2024 05:05:50][⚠️][mariadb-nextcloud] Skipping verification for this container because its not wanted! [28.02.2024 05:05:50][ℹ️][binhex-sabnzbdvpn] '/mnt/cache/appdata/binhex-sabnzbdvpn/data' is within mapped volume '/mnt/cache/appdata/binhex-sabnzbdvpn'! Ignoring! [28.02.2024 05:05:50][ℹ️][binhex-sabnzbdvpn] Should NOT backup external volumes, sanitizing them... [28.02.2024 05:05:50][ℹ️][binhex-sabnzbdvpn] Calculated volumes to back up: /mnt/cache/appdata/binhex-sabnzbdvpn [28.02.2024 05:05:50][ℹ️][binhex-sabnzbdvpn] Backing up binhex-sabnzbdvpn... [28.02.2024 05:05:50][ℹ️][binhex-sabnzbdvpn] Backup created without issues [28.02.2024 05:05:50][⚠️][binhex-sabnzbdvpn] Skipping verification for this container because its not wanted! [28.02.2024 05:05:50][ℹ️][Main] Set containers to previous state [28.02.2024 05:05:50][ℹ️][binhex-sabnzbdvpn] Starting binhex-sabnzbdvpn... (try #1) done! [28.02.2024 05:05:58][ℹ️][mariadb-nextcloud] Starting mariadb-nextcloud... (try #1) done! [28.02.2024 05:05:58][ℹ️][mariadb-nextcloud] The container has a delay set, waiting 5 seconds before carrying on [28.02.2024 05:06:03][ℹ️][LogitechMediaServer] Starting LogitechMediaServer... (try #1) done! [28.02.2024 05:06:05][ℹ️][plex] Starting plex... (try #1) done! [28.02.2024 05:06:08][ℹ️][Redis] Starting Redis... (try #1) done! [28.02.2024 05:06:10][ℹ️][swag] Starting swag... (try #1) done! [28.02.2024 05:06:10][ℹ️][swag] The container has a delay set, waiting 15 seconds before carrying on [28.02.2024 05:06:25][ℹ️][nextcloud] Starting nextcloud... (try #1) done! [28.02.2024 05:06:28][ℹ️][radarr] Starting radarr... (try #1) done! [28.02.2024 05:06:30][ℹ️][Sonarr] Starting Sonarr... (try #1) done! [28.02.2024 05:06:32][ℹ️][gPodder] Starting gPodder... (try #1) done! [28.02.2024 05:06:35][ℹ️][phpmyadmin] Starting phpmyadmin is being ignored, because it was not started before (or should not be started). [28.02.2024 05:06:35][ℹ️][DiskSpeed] Starting DiskSpeed is being ignored, because it was not started before (or should not be started). [28.02.2024 05:06:35][ℹ️][QDirStat] Starting QDirStat is being ignored, because it was not started before (or should not be started). [28.02.2024 05:06:35][ℹ️][MongoDB] Starting MongoDB... (try #1) done! [28.02.2024 05:06:35][ℹ️][MongoDB] The container has a delay set, waiting 5 seconds before carrying on [28.02.2024 05:06:40][ℹ️][unifi-network-application] Starting unifi-network-application... (try #1) done! [28.02.2024 05:06:43][ℹ️][Main] Backing up the flash drive. [28.02.2024 05:07:16][ℹ️][Main] Flash backup created! [28.02.2024 05:07:16][ℹ️][Main] Checking retention... [28.02.2024 05:07:16][ℹ️][Main] Delete old backup: /mnt/user/Backup/ca_backup_app/ab_20240124_050001 [28.02.2024 05:07:18][ℹ️][Main] DONE! Thanks for using this plugin and have a safe day ;) [28.02.2024 05:07:18][ℹ️][Main] ❤️ I also created a private debug log. The debug log id is: 36756508-9131-4a72-9764-cd0ed83a1b75

I just specify the IP address of the Mongo host, rather than a hostname. So delete the Unifi controller image (it only evaluates the name on the first run) and set MONGO_HOST as: 192.168.1.200 Note that I don't use "bridge" but a custom network, but I think you'll be fine specifying your server's IP.

Yeah, I'm clueless as to if it made any difference for me, but figure that I've gone to to the trouble of setting it up and it takes up so little resources that I might as well keep it around. I initially installed it to try and get my photos to load faster in my photo app. I applied so many fixes that I have no idea what fixed it, but it's working well enough now, so I don't want to rock the boat.

Sooooo the Mongo docker now starts/runs fine again... There was an update to the Mongo container, so maybe it was just a bug? Or maybe some lock on some file expired? I don't know what's going on anymore lol