emod

These solutions are extremely confusing!!!!! First there was a recommendation to follow: https://github.com/linuxserver/docker-nextcloud/issues/288 This recommendation did NOT work because the person forgot to state that MAINTENANCE MODE MUST be turned off. (And the person failed to state how to do that) Then I followed subsequent recommendations and changed docker container to lscr.io/linuxserver/nextcloud:25.0.2 Then, I disabled MAINTENANCE MODE. So now things work Question: (1) Where EXACTLY in nextcloud user interface do you DISABLE auto-updates? (2) What now? Eeveryone will be stuck using "lscr.io/linuxserver/nextcloud:25.0.2" and we can NEVER AGAIN upgrade to a newer Nextcloud vesion? In nextcloud GUI->Administration->Overview I see under "Update" section following: "A new version is available: Nextcloud 26.0.2"....What now? Should I "Open Updater" and update, or do nothing??? Should I chang docker image to something eslese BEFORE update or not? Thx

I think you are correct. Mobo was getting hot, and might have triggered some safety mechanism. I left the server overnight in OFF position. Turned it back in the morning, and literally everything was working fine. Even the mover moved everything (including Apps backup) from CACHE to array. Scary experience but a good lesson. I have had issues with MOVER not working since Sept 2021, and after upgrading UNRAID OS to the next development branch, it suddenly started to work again (that was a pleasant surprise).

I cannot access GUI - CACHE M2 drive is likely dead, USB might be as well - NOW what? (specific questions are further below) I think this time, something really bad went wrong on my UNRAID server. I need help in identifying how to find where the problem is. I appreciate help. UNRAID basic config: 1 Parity drive, 2 HDDs, 1 M.2 SSD (cache), on latest development branch: 6.10.0-rc2 -CACHE drive contains apps, and some other data....but all personal data was on arrays and parity. I have a backup of USB BOOT, but not CACHE. Here is what happened (I'll give all info to the best of my knowledge): During copying 25GB data (Resilio sync and Plex indexing) on my UNRAID box...CACHE drive got hot to over 67C for 5mins or so, CPU temps went to 100C for same amount of time. I used "Edust for electronics" duster to try to move air, cool down motherboard and remove some excess dust. I was unable to access Docker to shut down the offending processes (Resilio sync and Plex) I was unable to reboot from within GUI I then turned off the server (directly on the box) I restarted the server but cannot access GUI (browser said "Problem loading page") I could not PING server from my PC. On my router I saw that Ethernet link to UNRAID is UP. I thought USB might be dead, I created a new UNRAID USB boot drive (from UNRAID website), and switched it with the old one -> restarted UNRAID -> still cannot access GUI. I connected mini-monitor, keyboard and mouse directly to the server; then restarted the server On the monitor I saw an error saying :"CPU FAN failure, press F1 - I did to no avail" I open server case and notice that CPU fan is not moving at all. I touched it a bit, and it started working (there was some dust around the propeler so that might have prevented normal function) I reboot the server, and now server enters BIOS mode (by itself). I exited BIOS, and the server restarted on its own and reenters the BIOS. I enter BIOS and notice that: Parity drive and 2 array drives are identified M.2 slot (where SSD cache is): says N/A CPU is running, CPU fan is running Memory sticks are identified. All other Hardware readings, incl. temperatures for CPU and MoBo seem normal. MY ASSUMPTIONS: M.2 SSD CACHE drive is dead Bootable USB might be dead too -> I assume that only bootable USB is required to bring system up (even without CACHE)...but when I inserted a brand new USB with fresh UNRAId, the system still wasn't accessible via GUI or via monitor. The fact that server, when turned on, goes instantly into BIOS mode, and when I exit BIOS mode, the server restarts into BIOS again - tells me there is something wrong going on but I cannot figure out whether it's USB, motherboard, or SSD CACHE? QUESTIONS: I assume CACHE is dead. How do I verify that? For example, can UNRAID GUI start with USB only (without CACHE) Is it possible that even some components on motherboard are dead? If CACHE is dead, and once I buy a new CACHE, what is the process for installing it (I assume I'll have to reinstall all apps, since nothing from CACHE was backed up on array) Do I just switch the old for new, and restart the server? Is there some hardware or tool I can buy to try to recover data from CACHE? Thanks.

My USB is dead, and my USB backup, app backup is all on encrypted drive. What are steps to get back up and running? My idea is to create a new bootable USB, start UNRAID, then de-crypt the drives, then restore USB configuration from backup. Is that the right sequence? Also how do I find out the order of my drives. I only have parity drive (10TB) and 2 discs (4TB and 2TB). So I KNOW which is parity drive. How do I find out sequence of other drives?

No. Issues I first saw with 6.8.3 remained, plus: I cannot access apps (loading apps never finishes), Docker returned but many apps have "?" in lieu of app icon. mail server is stopped and cannot be started. Unable to access diagnostics page (the one I provided I manually copied from server onto USB - I attached monitor/mouse/keyb directly to server).

Done. ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=10.8 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=13.3 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=6.22 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=9.14 ms ping www.google.com PING www.google.com (172.217.8.4) 56(84) bytes of data. 64 bytes from iad23s59-in-f4.1e100.net (172.217.8.4): icmp_seq=1 ttl=118 time=9.50 ms 64 bytes from iad23s59-in-f4.1e100.net (172.217.8.4): icmp_seq=2 ttl=118 time=12.1 ms 64 bytes from iad23s59-in-f4.1e100.net (172.217.8.4): icmp_seq=3 ttl=118 time=5.28 ms 64 bytes from iad23s59-in-f4.1e100.net (172.217.8.4): icmp_seq=4 ttl=118 time=8.18 ms 64 bytes from iad23s59-in-f4.1e100.net (172.217.8.4): icmp_seq=5 ttl=118 time=11.1 ms 64 bytes from iad23s59-in-f4.1e100.net (172.217.8.4): icmp_seq=6 ttl=118 time=4.77 ms 64 bytes from iad23s59-in-f4.1e100.net (172.217.8.4): icmp_seq=7 ttl=118 time=6.83 ms v 6.8.2. Per original post, as soon as I discovered issue with 6.8.3, first thing was downgrading to 6.8.2. System remained on that version.

1. PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=9.32 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=12.2 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=5.64 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=9.27 ms .... 2. 64 bytes from yul03s04-in-f4.1e100.net (172.217.13.164): icmp_seq=1 ttl=117 time=18.8 ms 64 bytes from yul06s04-in-f4.1e100.net (172.217.13.164): icmp_seq=2 ttl=117 time=23.3 ms 64 bytes from yul06s04-in-f4.1e100.net (172.217.13.164): icmp_seq=3 ttl=117 time=17.1 ms 64 bytes from yul06s04-in-f4.1e100.net (172.217.13.164): icmp_seq=4 ttl=117 time=20.6 ms 64 bytes from yul06s04-in-f4.1e100.net (172.217.13.164): icmp_seq=5 ttl=117 time=23.8 ms 64 bytes from yul06s04-in-f4.1e100.net (172.217.13.164): icmp_seq=6 ttl=117 time=17.4 ms 64 bytes from yul06s04-in-f4.1e100.net (172.217.13.164): icmp_seq=7 ttl=117 time=20.7 ms .....

It's interesting that I never initiated personal attacks against any forum member (I did react to few insulting ones that were targeting me for sure), yet you quoted me? Very interesting. And after you posted your plea, another member just posted another post, not adding anything to the solution, but, unsuccessfully, trying to be cynical.

I posted diagnostics more than an hour before you posted your reply. Why didn't you read them? You might give an example of a "rational person" if you read posts before you react. If you'd like to set an example of a "rational person", then carefully read the entire thread before reacting. If the way you react you seem fit (given ignorance of not reading the post and data provided), then you are no better than me. The problem was triggered exclusively by updating UNRAID (and I've done that numerous time), with no changes to any other infrastructure components. "Bashing"? No, warning of a very serious issue, which severely compromised the server. If other users of UNRAID see how raising issues results in personal attacks on the person who raised the issue, what is the likelihood that UNRAID problems will be raised to begin with?

I'm not sure what you mean by "eliminate that"? I already looked into pfsense: no changes made since May this year (firewall rules and NAT are set up correctly). From pfsense I can ping UNRAID just fine. DHCP server correctly assigns a static IP to UNRAID server: the assignment is active. Server is using the same gateway like the wifi for few other devices. If access to internet were not possible, those devices wouldn't have access to internet either.

Good question. For all things I modified on UNRAID I followed SpaceinvaderOne videos - so maybe there were network changes there? Still, I haven't installed or removed anything on UNRAID in over 6 months, and had restarted the server 4-5 times during that time. I did not encounter issue like the one today. I'll delete config/network.cfg from the flash drive, reboot and see what happens.

I raised an issue in CAPS, consistent with the severity of problem that I encountered, and which showed SEVERELY corrupted UNRAID functions that might even have corrupted personal data on my disk (maybe that's another discovery). I attacked the problem, you attack me. Is that "proper" action in your mind? Is that example you are trying to set? Why don't you ask yourself what is the "proper action" to reacting to issues raised: attack the problem or attack the person?

I'll be glad to wait and follow intelligent advice, but apparently one user finds it important to make a political statement, another one makes personal attacks, and so on. I pointed a problem at UNRAID software, not at any person on this forum. Instead of trying to solve the problem, some are engaging in personal attacks. You think that helps?

I posted diagnostics 20 minutes before you posted your comment. Why are writing that I have not posted diagnostics?

And replying/commenting like one won't help either. I posted a serious problems to alert other users. You downplaying it or making fun of it (or making a political issue out of it) will not make it any less sever - it will just raise questions if you are trying to silence someone because there is a problem that you do not know solution to. It erodes your credibility, not mine.