Восстановление базы mysql, из неправильного бэкапа

2019-12-01  2:30:15 139621252817472 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-12-01  2:30:15 139621252817472 [Note] InnoDB: The InnoDB memory heap is disabled
2019-12-01  2:30:15 139621252817472 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-12-01  2:30:15 139621252817472 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-12-01  2:30:15 139621252817472 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-12-01  2:30:15 139621252817472 [Note] InnoDB: Using Linux native AIO
2019-12-01  2:30:15 139621252817472 [Note] InnoDB: Using generic crc32 instructions
2019-12-01  2:30:15 139621252817472 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-12-01  2:30:16 139621252817472 [Note] InnoDB: Completed initialization of buffer pool
2019-12-01  2:30:16 139621252817472 [Note] InnoDB: Highest supported file format is Barracuda.
2019-12-01  2:30:16 139621252817472 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41936310197
2019-12-01  2:30:16 139621252817472 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2019-12-01 02:30:16 7efc1b2d6240 InnoDB: Error: page 545 log sequence number 41936346710
InnoDB: is in the future! Current system log sequence number 41936344617.
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.
2019-12-01 02:30:16 7efc1b2d6240 InnoDB: Error: page 465 log sequence number 41936346941
InnoDB: is in the future! Current system log sequence number 41936344617.
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.
2019-12-01 02:30:16 7efc1b2d6240 InnoDB: Error: page 491 log sequence number 41936347958
InnoDB: is in the future! Current system log sequence number 41936344617.
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.
2019-12-01 02:30:16 7efc1b2d6240 InnoDB: Error: page 806 log sequence number 41936348205
InnoDB: is in the future! Current system log sequence number 41936344617.
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.
2019-12-01 02:30:16 7efc1b2d6240 InnoDB: Error: page 566 log sequence number 41936349119
InnoDB: is in the future! Current system log sequence number 41936344617.
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.
2019-12-01 02:30:16 7efc1b2d6240 InnoDB: Error: page 536 log sequence number 41936350120
InnoDB: is in the future! Current system log sequence number 41936344617.
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.
2019-12-01  2:30:16 139621252817472 [Note] InnoDB: Starting final batch to recover 44 pages from redo log
191201  2:30:16 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.1.26-MariaDB-0+deb9u1
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 352445 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x30000
InnoDB: Probable data corruption on page 3498
InnoDB: Original record (compact record)
InnoDB: on that page.
InnoDB: Cannot find the dir slot for record (compact record)
InnoDB: on that page!
2019-12-01 02:30:16 7efbfdffb700 InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex d812c48200000daa00000d9f00000dab00000009c399540445bf000000000000000000002b4a00043f65801438ea07d303b2000500000010000000000000000000000000000000005bab000000000000000000000000000000002019-12-01  2:30:22 140240621142592 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.