Коллеги добрый вечер! Нужно помощь имеется сервер Zabbix+MySQL\MariaDb база данных, после не понятного аварийного выключения сервера не стартует база данных ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111 "Connection refused"). к сожалению резервных копий базы нет, есть ли возможность как то выйти из положения не потеряв базу.

Log MySQL

2020-04-18 6:30:02 140113915100544 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to $

2020-04-18 6:30:02 140113915100544 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2020-04-18 6:30:02 140113915100544 [Note] InnoDB: The InnoDB memory heap is disabled
2020-04-18 6:30:02 140113915100544 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-04-18 6:30:02 140113915100544 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memor$
2020-04-18 6:30:02 140113915100544 [Note] InnoDB: Compressed tables use zlib 1.2.8
2020-04-18 6:30:02 140113915100544 [Note] InnoDB: Using Linux native AIO
2020-04-18 6:30:02 140113915100544 [Note] InnoDB: Using SSE crc32 instructions
2020-04-18 6:30:02 140113915100544 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-04-18 6:30:02 140113915100544 [Note] InnoDB: Completed initialization of buffer pool
2020-04-18 6:30:02 140113915100544 [Note] InnoDB: Highest supported file format is Barracuda.
2020-04-18 6:30:02 140113915100544 [Note] InnoDB: Starting crash recovery from checkpoint LSN=477152925$
2020-04-18 6:30:02 140113915100544 [Note] InnoDB: Restoring possible half-written data pages from the d$
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 85571840
2020-04-18 6:30:02 140113915100544 [Note] InnoDB: Starting final batch to recover 487 pages from redo l$
2020-04-18 06:30:02 7f6eb27fa700 InnoDB: Error: page 18372 log sequence number 47727719171
InnoDB: is in the future! Current system log sequence number 47715394842.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2020-04-18 06:30:02 7f6eb3ffd700 InnoDB: Error: page 9007 log sequence number 47728116466
InnoDB: is in the future! Current system log sequence number 47715394842.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2020-04-18 06:30:02 7f6eb2ffb700 InnoDB: Error: page 644 log sequence number 47715644975
InnoDB: is in the future! Current system log sequence number 47715394842.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2020-04-18 06:30:02 7f6eb27fa700 InnoDB: Error: page 16385 log sequence number 47728607343
InnoDB: is in the future! Current system log sequence number 47715394842.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.

Да пытался сделать, но не получилось.

На подобие как в этой статье https://linux-notes.org/ispravlyaem-povrezhdenny-e-innodb-tablitsy/

БД запускается при значении innodb_force_recovery = 6 вот при создании дампа возникли проблемы и т.д.

всё разобрался