MariaDB failure after restoring from snapshot

So, after some fresh ZWave mayhem I restored my HA VM from a Virtualbox snapshot.

It seems that the MariaDB addon didn’t take too kindly to such treatment and is giving me this log:

2020-03-22 10:54:34 0 [Note] InnoDB: Completed initialization of buffer pool
2020-03-22 10:54:34 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-03-22 10:54:34 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=6962084107
2020-03-22 10:54:35 0 [ERROR] InnoDB: Page [page id: space=0, page number=4] log sequence number 6962420657 is in the future! Current system log sequence number 6962313800.
2020-03-22 10:54:35 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.

I looked at the link from the log, but am not sure how it applies to the HA MariaDB addon and how to configure it.

Any help would be greatly appreciated :frowning:

I had a thought to uninstall the MariaDB addon and reinstall it with the same addon config, but this has now led to an even bigger problem: the NGINX Proxy Manager addon has recently been tied at the hip to the MariaDB addon (btw, does anyone know why?), so my NGINX web ui user has disappeared. It seems that the bindings have been kept (I assume they’re kept in an NGINX container config file), so my URLs and certificates work, but I can’t configure NGINX anymore.

This is truly a terrible state of affairs and I assume I’ll have to go back to the VM snapshot again, but how can I afterwards fix MariaDB while preserving my NGINX config??

Fortunately Portainer had nearly all my NGINX port mappings, so that I could redo my NGINX config with the new database quite simply (and this has been a lesson to save all those mappings in Confluence for the future :slight_smile: ), but the question remains: if a snapshot restore stops MariaDB from starting, can anything be done to save that database instance?

I’m having the exact same problem. I’m researching, but I’m not finding a lot in the way of answers. Seems like a fairly serious risk associated with MariaDB. However, the default HA logging function had similar issues, I moved to Maria in hopes that I could quit renaming database files to get logging to run again after restores.