drrevenge

Just wanted to add that I had the same issue as vessosa. Whilst my cache name was different (in my instance it was nvme500g - which makes sense as that was what the pool was previously called) the above syntax worked for me by renaming the file and rebooting so it regenerated it.

Hi all, I have a bit of an unusual question. I have two unraid licenses, one which is on the grandfathered plan of lifetime and the other which is unleashed (ie need to pay for updates every twelve months.) My lifetime license is currently my primary box with the unleashed being my backup. Earlier in the year my backup server experienced a catastrophic failure so I’m in the process of building a new server and I want this one to be my primary server and my existing primary to become my backup. My issue is this: How do I copy the config between the two so that I can make my new server have the lifetime key which is currently in use on the primary server (I would be starting this machine from scratch with no config and no existing drives) and the unleashed key take the config from my current primary server and make this my backup server. In a perfect world I would have upgraded my secondary key, but Australian exchange rates at the moment make that as about as pleasant as trying to buy RAM currently.

I would be suspecting possibly an issue with the systemboard. While I don't know the reason for the igpu error listed above, your screenshot is also still calling out errors from ata2 and also a little bit further in the logs ata4. I did have a look to see if there was a bios update for your machine, but it looks like it was updated not too long ago. Before version 7, I did have the issue where the GUI would become unresponsive but could ssh into it at least initially. It was having the web gui open for long periods would cause the issue. Interestingly, searching that syslog file, I don't see any reference to version 7 of unraid, I only see version 6.12.54 mentioned. (But I am no unraid guru.) As mentioned by JorgeB above, I'd be checking out the hardware, try and run some diagnostics on the board and CPU to see if that helps. Good luck!

The issue turned out not to be an issue with Nextcloud, but my certificates via SWAG. For some reason like this user who had issues with their lets encrypt certificates, I had two directories. Once I moved the older one and restarted my swag and cloudflare containers, all came good. https://www.claudiokuenzler.com/blog/1033/letsencrypt-certbot-unable-issue-certificate-please-choose-account I'm all for running an N-1 approach with container maintenance, although from what I hear that's not the best way to run things anymore. Anyway, turns out as I said, not a nextcloud issue preventing me from getting access to the server.

I'm also seeing it after an update. My nextcloud instance whilst showing as starting is unable to be connected to so unfortunately it appears to have broken something. :( I'm going to try and reboot the whole server and see if that helps at all.

I’ve not had any further repeats of the problem since closing all instances of the management GUI. Not a huge fan of the solution, I would imagine that you’d be able to leave it open, but I can deal with it. Thanks again for the assistance!

It's one of the computers in my house. I would have had the GUI open at some point. But is this honestly the reason for max CPU? This seems a like a bug that the GUI can't handle being open all the time. I will make sure I have nothing open on the GUI from here and see how we go.

Apologies I thought it was included in the diags.zip. syslog-192.168.0.34.log

Hi All, I've had my unraid server setup and running ok for about the last 8 months or so. However, since upgrading to 6.12.4, I have had two instances where my NAS becomes unresponsive. The first time it happened, I powered it off and then back on again, performed a parity scan and no issues were found. Unfortunatly I hadn't had syslog enabled. So any data then was lost after the power cycle. When I had it happen last time, I was unable to ping the machine or connecting a display to the unit didn't give me anything. So there wasn't a lot I could do. The second time around (happened this weekend just gone) I had syslog enabled. My first indication anything was wrong, was that one of the Docker containers I normally connect to was really slow to respond. I was able to log into the main GUI on my phone and I could see that the CPU was running 100% utilised across all the cores. Unfortunately I didn't have SSH enabled on the system, so I couldn't connect into it that way, and when I tried to goto the web gui to enable SSH again, it was no longer responsive, and I had to hard power it off again. (This time the parity scan did find one error, but it was corrected.) I now have SSH enabled if it was to happen again to try and see what is hammering the CPU at the time. I have updated all my docker containers to their latest versions, but I don't have any culpret at this point as to what is causing the NAS to be unresponsive. I've checked the disk logs for all the drives attached to the system (including the USB) and I can't see any specific reason as to why this is happening. I'm open to any suggestions. Thanks in advance! bignas-diagnostics-20231023-1115.zip