After a power loss, the InnoDB/XtraDB database is not recoverable.

2015-09-30 20:17:29 140193769776992 [Note] /opt/mariadb-10.1.7-linux-x86_64/bin/mysqld (mysqld 10.1.7-MariaDB-log) starting as process 2319 ...
2015-09-30 20:17:29 140193769776992 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-09-30 20:17:29 140193769776992 [Note] InnoDB: The InnoDB memory heap is disabled
2015-09-30 20:17:29 140193769776992 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-09-30 20:17:29 140193769776992 [Note] InnoDB: Memory barrier is not used
2015-09-30 20:17:29 140193769776992 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-09-30 20:17:29 140193769776992 [Note] InnoDB: Not using CPU crc32 instructions
2015-09-30 20:17:29 140193769776992 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2015-09-30 20:17:29 140193769776992 [Note] InnoDB: Completed initialization of buffer pool
2015-09-30 20:17:29 140193769776992 [Note] InnoDB: Highest supported file format is Barracuda.
2015-09-30 20:17:29 140193769776992 [Note] InnoDB: Log scan progressed past the checkpoint lsn 84533366099
2015-09-30 20:17:29 140193769776992 [Note] InnoDB: Database was not shutdown normally!
2015-09-30 20:17:29 140193769776992 [Note] InnoDB: Starting crash recovery.
2015-09-30 20:17:29 140193769776992 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-09-30 20:17:29 140193769776992 [Note] InnoDB: Restoring possible half-written data pages
2015-09-30 20:17:29 140193769776992 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 84538608640
InnoDB: Doing recovery: scanned up to log sequence number 84543851520
InnoDB: Doing recovery: scanned up to log sequence number 84549094400
InnoDB: Set innodb_force_recovery to ignore this error.
2015-09-30 20:17:30 7f8167d8e760 InnoDB: Assertion failure in thread 140193769776992 in file log0recv.cc line 2846
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
150930 20:17:30 [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: 10.1.7-MariaDB-log
key_buffer_size=16777216
read_buffer_size=262144
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 = 371998 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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
mysys/stacktrace.c:247(my_print_stacktrace)[0xbe66be]
sql/signal_handler.cc:160(handle_fatal_signal)[0x754cc4]
/lib64/libpthread.so.0(+0xfd00)[0x7f816796fd00]
/lib64/libc.so.6(gsignal+0x35)[0x7f8166617d95]
/lib64/libc.so.6(abort+0x17b)[0x7f81666192ab]
log/log0recv.cc:2846(recv_scan_log_recs(unsigned long, unsigned long, unsigned char const*, unsigned long, unsigned long, unsigned long*, unsigned long*, dberr_t*))[0x93f15f]
log/log0recv.cc:3057(recv_group_scan_log_recs)[0x9401d7]
srv/srv0start.cc:2544(innobase_start_or_create_for_mysql())[0x9c13dc]
handler/ha_innodb.cc:4106(innobase_init)[0x8ecd90]
sql/handler.cc:513(ha_initialize_handlerton(st_plugin_int*))[0x75860e]
sql/sql_plugin.cc:1407(plugin_initialize)[0x5ba850]
sql/sql_plugin.cc:1684(plugin_init(int*, char**, int))[0x5bc5c2]
sql/mysqld.cc:5195(init_server_components)[0x518ece]
sql/mysqld.cc:5758(mysqld_main(int, char**))[0x51a7f4]
/lib64/libc.so.6(__libc_start_main+0xed)[0x7f816660423d]
/opt/mariadb-10.1.7-linux-x86_64/bin/mysqld[0x50fe49]
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.