Форум пользователей MySQL

Перестал запускаться mysql перед этим часто падал
Лог

140926 08:57:17 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140926 8:57:17 [Note] Plugin 'FEDERATED' is disabled.
140926 8:57:17 InnoDB: The InnoDB memory heap is disabled
140926 8:57:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140926 8:57:17 InnoDB: Compressed tables use zlib 1.2.7
140926 8:57:17 InnoDB: Using Linux native AIO
140926 8:57:17 InnoDB: Initializing buffer pool, size = 128.0M
140926 8:57:17 InnoDB: Completed initialization of buffer pool
140926 8:57:17 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140926 8:57:17 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...
140926 8:57:17 InnoDB: Assertion failure in thread 140705098303264 in file fsp0fsp.c line 2102
InnoDB: Failing assertion: inode
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/...-recovery.html
InnoDB: about forcing recovery.
06:57:17 UTC - 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.
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_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346682 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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7ff875bb8569]
/usr/sbin/mysqld(handle_fatal_signal+0x3d8)[0x7ff875aa0748]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf030)[0x7ff875252030]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7ff873ae5475]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x180)[0x7ff873ae86f0]
/usr/sbin/mysqld(+0x5eaad0)[0x7ff875c6bad0]
/usr/sbin/mysqld(+0x5f02ab)[0x7ff875c712ab]
/usr/sbin/mysqld(+0x5fc167)[0x7ff875c7d167]
/usr/sbin/mysqld(+0x5c8935)[0x7ff875c49935]
/usr/sbin/mysqld(+0x578d43)[0x7ff875bf9d43]
/usr/sbin/mysqld(+0x54543f)[0x7ff875bc643f]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_in t+0x41)[0x7ff875aa2ad1]
/usr/sbin/mysqld(+0x330e31)[0x7ff8759b1e31]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xa43)[0x7ff8759b3dc3]
/usr/sbin/mysqld(+0x2b3f85)[0x7ff875934f85]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7ff875939d4b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7ff873ad1ead]
/usr/sbin/mysqld(+0x2b0199)[0x7ff875931199]
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.
140926 08:57:17 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

Отключил innodb mysql  запустился.  Часть баз была в innodb и теперь не работает. Как  можно восстановить?