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

Здравствуйте.
ночью свалился mysql55-server-5.5.34 и больше подниматься отказывается.
Помогите советом.
в my.cnf выставлял
[mysqld]
innodb_force_recovery = 4

Вот лог:
131014 08:00:27 mysqld_safe mysqld from pid file /var/db/mysql/mz.mice.com.pid ended
131014 08:03:55 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
131014  8:03:55 [Warning] The syntax '--log' is deprecated and will be removed in a future release. Please use '--general-log'/'--general-lo
g-file' instead.
131014  8:03:55 [Warning] The syntax '--log' is deprecated and will be removed in a future release. Please use '--general-log'/'--general-lo
g-file' instead.
131014  8:03:55 InnoDB: The InnoDB memory heap is disabled
131014  8:03:55 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131014  8:03:55 InnoDB: Compressed tables use zlib 1.2.3
131014  8:03:55 InnoDB: Initializing buffer pool, size = 128.0M
131014  8:03:55 InnoDB: Completed initialization of buffer pool
131014  8:03:55 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 13507629376
131014  8:03:55  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 13507958251
131014  8:03:55  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 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 06:03:55 UTC - my
sqld 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=8388608
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 = 338465 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.