AncientVale

I'm wondering if someone can help me resolve the following error on my nextcloud install on unraid, or at least point me in the right direction?

So I lost power at my house last night and my Unraid server was down for the evening. Everything is back up and running now but I have an error showing on my server of Can someone tell me what command I would use to get those to run today? Or should I just wait and let them run at their normally scheduled times?

I'm not overclocking, so I'll try reseating. It just started being a problem though, so I might have to replace a CPU then. It doesnt go further and potentially tell you which CPU it is does it?

Can anyone help me out with this? I followed the instructions from Fix Common Problems.

I received this message in my Fix Common Problems Log: Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the unRaid forums. The output of mcelog (if installed) has been logged Can someone please help me out with this? Thanks! ancientvalemkii-diagnostics-20191230-1846.zip

Im still getting the calltraces, the only docker containers on a custom docker network are Nextcloud, Collabora, and Letsencrypt. How can I figure out which container it is and fix it?

Thank you!

Here they are ancientvalemkii-diagnostics-20190704-1125.zip

I did what you told me and it was fine for a little over a month. now I am getting the below in the log: Should I do that again? And does this mean my Cache drive is dying?

So I've had basically all of these issues at one point or another in my Fix Common Problems extended tests. For the first problem of the shares with different cases, you should check all of your docker container settings and see if you have a differing case there. You will likely need to use dolphin or krusader to move the files to the proper share before deleting the one with the wrong case For the duplicated file, go into the user share and delete the duplicate file. For the final issue, run the docker safe new permissions process in tools.

Hi guys, I was hoping someone could take a look at this call trace and let me know what they think it may be? I am not nearly as versed in this kind of stuff and it looks like this is a very specific error. I have ECC Memory and am running a Gigabyte GA-7TESM motherboard. Thank you!

How would I go about that if the system is read only? I tried running the appdata backup plugin (as that is really the only thing on there) and it didnt back anything up.

I tried the above and still got a "read only filesystem" error when trying the balance. Please find attached my diag, I also have an earlier copy in the OP of this thread. ancientvalemkii-diagnostics-20190530-1730.zip

I tried running the command that you give in the thread there, and I get the following: How can I force the cache to mount not read only? Some additional Errors when I go to mount the system:

When i try to recreate the docker image I get the following: And when I look at the check filesystem status, I get the below:

I am getting my Cache Drive (not pool) mounting as read only and very few of my docker containers are able to start. I have attached my Full Diag zip file below, and I did run a readonly BTRFS check on the cache drive, but I am at a loss on how to repair it as it isnt a pool so SCRUB isnt working. SCRUB actually is aborted when I click the button immediately. I also have these errors in my log: ancientvalemkii-diagnostics-20190530-1559.zip

Twitter is AncientVale

Hi, I was currently on Nextcloud 13.05 and the next newest update wasa 14.3, so following the instructions about a page back I initiated the update to 14.03 from within nextcloud itself. That was about 12 hours ago, and when I got to login all I get is "This Nextcloud instance is currently in maintenance mode, which may take a while. This page will refresh itself when the Nextcloud instance is available again. Contact your system administrator if this message persists or appeared unexpectedly. Thank you for your patience." The logs are also unhelpful as the only warnings are: PHP Warning: require_once(/config/www/nextcloud/lib/versioncheck.php): failed to open stream: No such file or directory in /config/www/nextcloud/cron.php on line 37 PHP Fatal error: require_once(): Failed opening required '/config/www/nextcloud/lib/versioncheck.php' (include_path='.:/usr/share/php7') in /config/www/nextcloud/cron.php on line 37 Any asssstance would be greatly appreciated. This instance was set up using SPO's instructions.