Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've a problem. Some days ago my root server crashes after a power outage. I realised that the MySQL server won't start. In the logs I find out that an error occured with InnoDB's ibdata1.

I've tried the automatic InnoDB recovery program (innodb_force_recovery). I reinstalled the MySQL server. All these ways didn't help. I've tried out some more which I get from forums and other community platforms (other variables in the my.cnf etc.). This ways didn't help me too. So I think that I need personal help. The problem is that I don't find any "real" resolution for this problem in the internet.

At the moment I have a MariaDB server (version 5.5) on my root.

The error message when I start the server directly (mysqld --console) is:

root@GPR0420:/var/lib# mysqld
131125 17:06:17 [Warning] An old style --language or -lc-message-dir value with language specific part detected: /usr/share/mysql/english/
131125 17:06:17 [Warning] Use --lc-messages-dir without language specific part instead.
131125 17:06:17 InnoDB: The InnoDB memory heap is disabled
131125 17:06:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131125 17:06:17 InnoDB: Compressed tables use zlib
131125 17:06:17 InnoDB: Using Linux native AIO
131125 17:06:17 InnoDB: Initializing buffer pool, size = 128.0M
131125 17:06:17 InnoDB: Completed initialization of buffer pool
131125 17:06:17 InnoDB: highest supported file format is Barracuda.
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
InnoDB: Error: trying to access page number 4294899583 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
131125 17:06:17  InnoDB: Assertion failure in thread 140125885400864 in file fil0fil.c line 5451
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
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: about forcing recovery.
131125 17:06:17 [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

 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.34-MariaDB-1~squeeze
 It is possible that mysqld could use up to
 key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 499482 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 0x30000
addr2line: 'mysqld': No such file
The manual page at contains
information that should help you find out what is causing the crash.

This error says me that there is an error in the ibdata1 or that this file is corrupt. Is it possible to repair the ibdata1-file? And when not, can we extract some data which aren't corrupt from this file?

I hope you can help me. It were nice to have the "new" (not in any backup) data back because the databases contains statistics.

Best regards, Jonniboy

share|improve this question

Looks like innodb_force_recovery is set to 6 in your my.cnf, so it will not try to recover based on binary logs, try setting it to 0 instead.

check also that you had binary logs activated at the time of crash:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.