Re: Failed to start mysql due to start_lsn and ens_lsn issue

[Hanru Jacobs]

Hi,

I have tried to reply to your post with as much info as possible but seems that the post has to be approved by a moderator first. Here is the reply minus the log out puts


Moving the log files to a different directory did not have the effect we were hoping for.

I will put a copy of the log files at the bottom.
After I moved the log files out I started mysql with innodb_force_recovery=1 working my way up to 5 where the server eventually started the "innodb_redo_log_files" table is still corrupt. But it did create a new log file and a bunch of temp files.

The link in the log file does not provide much more info that what I have already done.

So now the the server complains about "log sequence number is in the future!"
Which I might be able to fix but my worry is still the corrupt table.