Not absolutely certain but I think it would not work since your new Nextcloud setup has a new instance id. So you can indeed setup a new Nextcloud instance but I think the client apps will need a re-login and act like it is another Nextcloud instance (what it is).
You can of course try to copy the database files, config.php and data directory from the old Nextcloud instance to the new one. But it is kind of tinkering around and you should backup the files on clients first.
Not absolutely sure atm but yes I think when you search for mce in syslog you should find info about critical hardware errors.
If you use flashmemory plugin it may be necessary to disable it. (It moves logs to ram and so they get lost on a crash. After reboot you can only find logs from before last normal shutdown)
Lot of things can cause that. Anything in the logs? Syslog or journal may be of help. Eventually sth like mce what are typ. hardware errors. However, when I had problems with system crashs it always in the end turned out as RAM problem. Thus out of practical experience I personally would recommend to buy a new ram kit and see if the problem is gone.
Can you also post your docker compose code, your swag proxy-confs/*.nextcloud.conf and proxy.conf? Is your swag a fresh setup or an older one? I think the problem is in the swag proxy conf. Maybe some outdated files or so.
Please stop with the useless comments and just answer my original question!!!!!
You asked for instructions on a repair attempt without risking further damage. That is not possible. How to do it with minimum risk of damage is the way I just described. A new drive is necessary for that. When you cannot effort it, you should put it aside and wait until you can. No offense, no insult, no attitude. Simple facts.
Next time you may give some more information, like what docker image do you actually use, what guide did you use to setup. Not all users here have a magic glass ball.
Seems like nginx/Apache is not configured properly. How did you setup Nextcloud? Used any tutorial? Docker? Non-docker?
I know it is a unfortunate situation, but what you say makes no sense at all. Every try to read from the drive results in I/o errors but you know it is not dead, because it was working fine before and makes no clicking noises? Bro, every drive was working fine before it died. Clicking noises may be an indicator the same way as bad SMART values are.
What you can do is use dd with -noerror flag to force clone the whole drive to a new one while ignoring read errors. That is because every touching of the bad drive may result in even more data damage. You can now try to repair the broken filesystem and read data from the new drive without any risk.
Green SMART is no guarantee that your drive is ok. There are lots of problems SMART doesn’t cover. Your drive has obviously died.
I would simply replace it and recover data from latest backup.
Also you should really consider OMV6. OMV3 is outdated since a very long time.
Where exactly do you have problems with it? äöüß work out of the box for me.
Finally after 2 years he can start doing sth 😂
Unfortunately the best way is fresh setup. Take screenshots of your settings so you can restore them easily.
MySQL server has gone away
It depends on what services you wanna expose to the internet and how much would it worth it for a hacker to get in. Is it just like Nextcloud or ssh as well? Is it ‚just‘ some personal data or are there top secret federal documents saved on it?
In general. You should always disable UPnP in your router to prevent any port openings you did not intend. Only open single ports when you really know why you need to.
Nextcloud behind a swag proxy is already pretty save. It comes with pre-configured fail2ban and other protective stuff. I have never seen someone trying to get in. What I see are regular scans of WordPress or phpmyadmin setups and queries trying to make php execute code.
If you wanna expose ssh as well, use another port for it and forbid password authentication. Public key auth only. You could also setup a honeypot on default port. There are some projects out there. Just google it.
Those things are minimum. If you want more than that you could think about making your services accessible via vpn only.
I don't see that log location on my system.
docker logs -f nextcloud should also show the log however (or you could click the log icon next to the nextcloud container, if you have Portainer)
There are different logs. You described how to show the log of the docker container. I was talking about the app log. But I was wrong nevertheless. Using linuxserver.io image, under /config/log you should find the logs of nginx and php. The app log of nextcloud is at /data/nextcloud.log.
What about Nextcloud logs? You will find them in sth like appdata/nextcloud/config/log or whatever you bind mounted to Nextclouds /config
But yeah looks like your drive died.
You probably right but it is not certain. I myself once had a faulty drive that passed bad blocks test. Not sure what the problem was. I just swapped the drive.
Thus I don’t know if a communication error would even be interpreted as bad block or if it would just rescan the block
Why do you think a passed bad blocks check means your cable is ok?
USB drives have a dedicated power supply?
