Mysql – Recover a MySQL InnoDB from ibdata1 that won’t repair using innodb_force_recovery

ib_logfile-s store only recent changes, so you won't recover all data from them.

It's possible however to fetch records directly from disk image, you don't need to restore ibdata1. Actually you even don't need a filesystem.

Check out data recovery toolkit from http://www.percona.com/software/mysql-innodb-data-recovery-tools .

You need something like

./page_parser -f disk.img

And then you can fetch records from InnoDB indexes.

UPDATE: Data recovery toolkit moved to GitHub

Your InnoDB tables are definitely have errors, but it seems to be that the reason why mysql can't start is lack of memory. It's from your error log:

key_buffer_size=33554432
read_buffer_size=134217728
max_used_connections=0
max_threads=5000
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 = 819301283 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Please make sure your server have enough RAM (should have at least 820G of RAM). If not - decrease some parameters in my.cnf There are many memory allocating parameter including some for InnoDB engine. Please consider them also. If it is the problem then again start recovering from innodb_force_recovery = 1 to 6