No access after restart

[izgimmer]

Today, I restartet tried to shutdown my AS5402T to connect a UPS.
As always, the NAS does not shut down but stays running and blinking until I use the power button to turn in off.
Actually, why is that? Another thing I do not like about it. ADM will not be accessible, while docker e.g. containers are still running.

But now, in contrast to prior restarts, Nextcloud is not working anymore. After some troubleshooting, I am beginning to think that the problem is connected to mariadb

When I use phpadmin to login the database, I receive the following error:
mysqli::real_connect(): (HY000/2002): Connection refused

I tried changing and resetting the password of the database in ADM which also results in errors.

Does anyone have an idea?

It's really frustrating, the NAS is not running without errors for more than a few month. I never experienced something like this with my Synology before.

[Nazar78]

Try disabling then enable it back. If that doesn't work probably the db crashed. Try to repair the db or last resort initialize then restore hopefully you had scheduled some backup dumps. It's all about db administration and it can happen on any system, if you're unsure do look for online guides.

[izgimmer]

Thanks for the reply. Deactivating and activating did not help, unfortunately.
The only mariadb related command I can use in the CLI is mariadb_config which does not help.
mariadb_check (https://mariadb.com/kb/en/mariadb-check/) is not available. How would you repair the db?

[Nazar78]

First you'll need to figure out what's wrong before attempting to repair. It could also be other issues like permission. Take a look at the log, /usr/local/AppCentral/mariadb/data/error.log.

[izgimmer]

Thanks for guiding me to the error log!

This error is occuring again and again:

Code: Select all

[ERROR] InnoDB: Missing FILE_CREATE, FILE_DELETE or FILE_MODIFY before FILE_CHECKPOINT for tablespace 5
[ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
[ERROR] Plugin 'InnoDB' init function returned error.	
[ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
[ERROR] Unknown/unsupported storage engine: InnoDB	
[ERROR] Aborting	

And in addition there is this warning:

Code: Select all

[Warning] 'innodb-file-format' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
[Warning] 'innodb-large-prefix' was removed. It does nothing now and exists only for compatibility with old my.cnf files.

[Nazar78]

Append innodb_force_recovery=6 to [mysqld] in your my.cnf, disable then enable back the mariadb from the app central. If everything ok undo the previous step then restart again. Start doing backups for your db.

[izgimmer]

Thanks, I was able to recover part of the database. But in the end I had to reinitialize MariaDB.

Is it possible to automate backups?