Crash on startup

System running MariaDB had a power failure.
When power was restored, the mariadb cannot start.

Log says:

190822 2:22:10 [Note] /usr/libexec/mysqld (mysqld 5.5.60-MariaDB) starting as process 4608 ...
190822 2:22:10 InnoDB: The InnoDB memory heap is disabled
190822 2:22:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190822 2:22:10 InnoDB: Compressed tables use zlib 1.2.7
190822 2:22:10 InnoDB: Using Linux native AIO
190822 2:22:10 InnoDB: Initializing buffer pool, size = 128.0M
190822 2:22:10 InnoDB: Completed initialization of buffer pool
190822 2:22:10 InnoDB: highest supported file format is Barracuda.
190822 2:22:10 InnoDB: Starting crash recovery from checkpoint LSN=916851962310
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is C577600
190822 2:22:10 InnoDB: Starting final batch to recover 2 pages from redo log
InnoDB: Cleaning up trx with id C5760BC
190822 2:22:10 InnoDB: Waiting for the background threads to start
190822 2:22:10 InnoDB: Assertion failure in thread 140458583914240 in file trx0purge.c line 822
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
190822 2:22:10 [ERROR] mysqld got signal 6 ;
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 http://kb.askmonty.org/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: 5.5.60-MariaDB
key_buffer_size=134217728
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 = 466718 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 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x7fbf41ac8cbd]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x7fbf416dd4a5]
sigaction.c:0(__restore_rt)[0x7fbf40e08100]
:0(__GI_raise)[0x7fbf3f53c5f7]
:0(__GI_abort)[0x7fbf3f53dce8]
/usr/libexec/mysqld(+0x73983f)[0x7fbf4197283f]
/usr/libexec/mysqld(+0x73a349)[0x7fbf41973349]
/usr/libexec/mysqld(+0x83c804)[0x7fbf41a75804]
/usr/libexec/mysqld(+0x831787)[0x7fbf41a6a787]
/usr/libexec/mysqld(+0x73c55d)[0x7fbf4197555d]
/usr/libexec/mysqld(+0x7304d6)[0x7fbf419694d6]
pthread_create.c:0(start_thread)[0x7fbf40e00dc5]
/lib64/libc.so.6(clone+0x6d)[0x7fbf3f5fdced]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
190822 02:22:10 mysqld_safe mysqld from pid file /var/lib/mysql/mx.rg47c.dk.pid ended