MySQL Forums
Forum List  »  InnoDB

Re: Failed to start mysql due to start_lsn and ens_lsn issue
Posted by: Hanru Jacobs
Date: August 04, 2022 07:56AM

Hi Peter,

No, I have not followed "Point-in-Time Recovery Using Binary Log".

MySQL did not want to start after a power outage and I could not get it started at all so could not get into MySQL to do anything.

I have now started the server with innodb_force_recovery=6 , which is risky at best, all the tables and data seems to be there. If I restart with innodb_force_recovery=5 or less the same error is logged:
2022-08-04T13:42:01.248079Z 1 [ERROR] [MY-013881] [InnoDB] The redo log file ./#innodb_redo/#ib_redo27250 has start_lsn 445543588864 but expected 445648380928 (end_lsn of the previous redo log file).

From here I'm currently stuck, I did read somewhere that I can see and change the start_lsn number from within mysql but now that I'm in at least I can try to find that doc and see if I can find anything that might help.

If you perhaps have any idea what I should do next I'm all ears. :)


Options: ReplyQuote

Written By
Re: Failed to start mysql due to start_lsn and ens_lsn issue
August 04, 2022 07:56AM

Sorry, only registered users may post in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.