bluuurb

Thanks for the steps, this is exactly the information I was looking for! Unfortunately my MongoDB is locked even though I stopped the controller. I stopped the controller via the Unraid UI and is shows 'stopped'. The docker status via docker ps -a is Existed (143). Any ideas on what might be causing this? This is the log after I ran the upgrade command Unable to find image 'mbentley/omada-controller:mongodb-upgrade-3.6-to-8' locally mongodb-upgrade-3.6-to-8: Pulling from mbentley/omada-controller dfd139f7c731: Already exists 1ff20e015d5e: Pull complete 1caa0849ae6b: Pull complete 7df1face0c7b: Pull complete 27f6c810ffa2: Pull complete Digest: sha256:fe699702a9d238897b4c7a65b09f4310aaf659869689fe240752ef9144c1250e Status: Downloaded newer image for mbentley/omada-controller:mongodb-upgrade-3.6-to-8 INFO: running hardware prerequisite check for AVX support on x86_64 to ensure your system can run MongoDB 8...done INFO: running pre-flight checks on MongoDB... ERROR: mongod.lock exists and isn't empty! Either the MongoDB wasn't shut down cleanly or there is another process accessing the persistent data files! Unable to execute upgrade!

I think I've figured it out. Somehow my unraid GUI was available on two ports. I used organizer on port 80 and mappen unraid to another. After the last update, unraid became available at Port 80 and the (old) mapped port. After changing the port back to 80 in the settings of unraid the problem stopped (so far).

My unraid server has become unreachable two times in the last months since the upgrade to 6.12.8. Sometimes the docker page doesn't load. So far I could fix it by disabling/enabling docker or rebooting the server. In the syslog I noticed the following errors this morning: https://pastebin.com/n0DV2eXU I read some things about the docker network, I have it set to ipvlan. My docker settings are: https://imgur.com/a/yMoV66h I'm out of my debt here and any support would be greatly appreciated.

Yesterday I upgraded to V6.12.8 and today my server became unreachable. After a reboot it came back online without errors. No clue as to what happened.. If it happens again I'll directly connect a monitor to get logs before reboot report back here. Not sure if useful but these are my diagnostics after reboot server-max-diagnostics-20240225-1549.zip

If you have problems with installing new nodes via the manage pallete: turn on hardlinks in the global share settings of Unraid.

Any update on this topic? :)

Works like a charm, thanks

That fix works, thanks!

Noticed this issue today as well. Updates are still being done via the CA Auto update plugin but no way to check the versions now.