Не запускается MySQL

А что сейчас в логе, когда запускаете с форсрекавери?

---------- Добавлено 30.10.2015 в 14:03 ----------

Попробуйте с разными значениями, примером innodb_force_recovery=1 --- с этим должно стартануть, даже если есть ошибки.

151030 14:02:16  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page directory corruption: supremum not pointed to
151030 14:02:16  InnoDB: Page dump in ascii and hex (16384 bytes):
тут нули
151030 14:02:16  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
151030 14:02:16InnoDB: Error: trying to access a stray pointer 0x80007f1a449dbff8
InnoDB: buf pool start is at 0x7f1a449d0000, end at 0x7f1a451d0000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: how to force recovery.
151030 14:02:16InnoDB: Assertion failure in thread 139750909191920 in file ./../include/buf0buf.ic line 268
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.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
151030 14:02:16 - 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.

Вот тут описаны более детально статусы для innodb_force_recovery https://dev.mysql.com/doc/refman/5.0/en/forcing-innodb-recovery.html

Действительно с 1 должно поднять. А вообще, если есть бэкапы, то забэкапьте действительно всю директорию mysql и удалите файлы ib_data* и ib_log*. После попробуйте поднять даже без force_recovery

Браво! Огромное спасибо! Всё заработало!

И спасибо всем, кто давал советы.

нет, это вот так:

Добавляем строку в /etc/my.cnf:

innodb_force_recovery = 2

далее уровень принудительности до 6 поднимаем, до тех пор, пока не запустится.

---------- Добавлено 30.10.2015 в 14:03 ----------

а данные таблиц с типом innodb ?