[MDEV-10640] Failure to start after power failure (signal 6) Created: 2016-08-21  Updated: 2019-01-13  Resolved: 2016-09-25

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 5.5.47
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Niels Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

Synology NAS


Issue Links:
Relates
relates to MDEV-18223 Crash during insert (?) Closed

 Description   

I had a power outage and after that i was returned with these errors/bugs. I tried to fix it myself but thought that it was better to let someone with knowledge of the subject look at it rather then mess too much with the system and possibly end up corrupting the data.

160821 21:50:40 mysqld_safe Starting mysqld daemon with databases from /var/services/mysql
160821 21:50:40 [Note] /usr/bin/mysqld (mysqld 5.5.47-MariaDB) starting as process 3623 ...
160821 21:50:40 InnoDB: The InnoDB memory heap is disabled
160821 21:50:40 InnoDB: Mutexes and rw_locks use InnoDB's own implementation
160821 21:50:40 InnoDB: Compressed tables use zlib 1.2.8
160821 21:50:40 InnoDB: Initializing buffer pool, size = 16.0M
160821 21:50:40 InnoDB: Completed initialization of buffer pool
160821 21:50:40 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 4431495501107
160821 21:50:40  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 4431496420711
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 426753 row operations to undo
InnoDB: Trx id counter is B0FFF100
160821 21:50:41  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51$
InnoDB: Apply batch completed
InnoDB: Starting in background the rollback of uncommitted transactions
160821 21:50:42  InnoDB: Rolling back trx with id B0FFEF77, 426753 rows to undo
 
InnoDB: Progress in percents: 1160821 21:50:42  InnoDB: Waiting for the background threads to start
160821 21:50:42  InnoDB: Assertion failure in thread 3882875760 in file btr0btr.c line 3013
InnoDB: Failing assertion: btr_page_get_prev(next_page, mtr) == page_get_page_no(page)
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
160821 21:50:42 [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.47-MariaDB
key_buffer_size=16384
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 = 50662 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 0x3c000
/usr/bin/mysqld(my_print_stacktrace+0x29)[0x86c6889]
/usr/bin/mysqld(handle_fatal_signal+0x514)[0x82fb444]
[0xf77be400]
[0xf77be430]
/lib/libc.so.6(gsignal+0x4f)[0xf723594f]
/lib/libc.so.6(abort+0x175)[0xf72371d5]
/usr/bin/mysqld[0x85a2c4f]
/usr/bin/mysqld[0x85ad864]
/usr/bin/mysqld[0x85b3ab0]
/usr/bin/mysqld[0x85b566b]
/usr/bin/mysqld[0x86891cd]
/usr/bin/mysqld[0x8689853]
/usr/bin/mysqld[0x8683adc]
/usr/bin/mysqld[0x8678717]
/usr/bin/mysqld[0x858ff6b]
/usr/bin/mysqld[0x8590772]
/lib/libpthread.so.0(+0x6cfa)[0xf776bcfa]
/lib/libc.so.6(clone+0x5e)[0xf72d72be]
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.
160821 21:50:42 mysqld_safe mysqld from pid file /run/mysqld/mysqld.pid ended
160821 21:50:43 mysqld_safe Starting mysqld daemon with databases from /var/services/mysql
160821 21:50:43 [Note] /usr/bin/mysqld (mysqld 5.5.47-MariaDB) starting as process 4023 ...
160821 21:50:44 InnoDB: The InnoDB memory heap is disabled
160821 21:50:44 InnoDB: Mutexes and rw_locks use InnoDB's own implementation
160821 21:50:44 InnoDB: Compressed tables use zlib 1.2.8
160821 21:50:44 InnoDB: Initializing buffer pool, size = 16.0M
160821 21:50:44 InnoDB: Completed initialization of buffer pool
160821 21:50:44 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 4431495501107
160821 21:50:44  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 4431496420711
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 426753 row operations to undo
InnoDB: Trx id counter is B0FFF100
160821 21:50:44  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51$
InnoDB: Apply batch completed
InnoDB: Starting in background the rollback of uncommitted transactions
160821 21:50:45  InnoDB: Rolling back trx with id B0FFEF77, 426753 rows to undo
 
InnoDB: Progress in percents: 1160821 21:50:45  InnoDB: Waiting for the background threads to start
160821 21:50:45  InnoDB: Assertion failure in thread 3882875760 in file btr0btr.c line 3013
InnoDB: Failing assertion: btr_page_get_prev(next_page, mtr) == page_get_page_no(page)
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
160821 21:50:45 [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.47-MariaDB
key_buffer_size=16384
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 = 50662 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 0x3c000
/usr/bin/mysqld(my_print_stacktrace+0x29)[0x86c6889]
/usr/bin/mysqld(handle_fatal_signal+0x514)[0x82fb444]
[0xf77c1400]
[0xf77c1430]
/lib/libc.so.6(gsignal+0x4f)[0xf723894f]
/lib/libc.so.6(abort+0x175)[0xf723a1d5]
/usr/bin/mysqld[0x85a2c4f]
/usr/bin/mysqld[0x85ad864]
/usr/bin/mysqld[0x85b3ab0]
/usr/bin/mysqld[0x85b566b]
/usr/bin/mysqld[0x86891cd]
/usr/bin/mysqld[0x8689853]
/usr/bin/mysqld[0x8683adc]
/usr/bin/mysqld[0x8678717]
/usr/bin/mysqld[0x858ff6b]
/usr/bin/mysqld[0x8590772]
/lib/libpthread.so.0(+0x6cfa)[0xf776ecfa]
/lib/libc.so.6(clone+0x5e)[0xf72da2be]
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.
160821 21:50:45 mysqld_safe mysqld from pid file /run/mysqld/mysqld.pid ended



 Comments   
Comment by Elena Stepanova [ 2016-08-24 ]

Did you try innodb_force_recovery, as the error message suggests?

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.

Please read documentation first! Levels of recovery that you will need will be most likely dangerous, but it might be the only way to retrieve your data.

Comment by Elena Stepanova [ 2016-09-25 ]

Please comment to re-open if you have further information on the issue.

Comment by Niels [ 2016-10-14 ]

Forgot to mention anything here, but I was able to get it working after using the force recovery.
I lost a significant amount of data as a result but was able to recover the rest without any issues.

Exporting the table first helped too (followed some tutorial online at the time.

Generated at Thu Feb 08 07:43:47 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.