Ayer inesperadamente se fue la luz, el nobreak no aguanto por consiguiente el servidor local que tengo montado en la oficina se apago.
Todo bien pero de repente veo que el servidor de MySQL no arrancó y me arroja el siguiente error:
080808 18:07:01 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...
080808 18:07:01 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 2643719067.
InnoDB: Doing recovery: scanned up to log sequence number 0 2643719067
InnoDB: Last MySQL binlog file position 0 3719, file name /var/log/mysql/mysql-bin.000546
080808 18:07:01 InnoDB: Started; log sequence number 0 2643719067
InnoDB: !!! innodb_force_recovery is set to 2 !!!
080808 18:07:01 [Note] Recovering after a crash using /var/log/mysql/mysql-bin
080808 18:07:01 [Note] Starting crash recovery...
080808 18:07:01 [Note] Crash recovery finished.
080808 18:07:01 - 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.
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.
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x8b01a78
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...
Cannot determine thread, fp=0xbffd3508, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81ea513
0x823066a
0x82284bb
0x8229a5e
0x822a254
0x822a53f
0x8281548
0x82826ca
0x81ecec1
0xb7c29ebc
0x8160581
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/us...ack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is invalid pointer
thd->thread_id=825241198
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
Ya he buscado en internet y no he encontrado una solución. Existe alguna forma de recuperar el servidor de mysql sin perder mis bases de datos?
O bien existe alguna forma de recuperar bases de datos innodb unicamente con los archivos FRM e ibdata??
Espero alguien pueda ayudarme.
