Failed to start mysql due to start_lsn and ens_lsn issue (21 replies)

I had a unexpected reboot which after mysql does not want to start.

There are not many resources regarding the issue most are for backup/incremental backup issues. This was just a plain server power issue.

I was doing a restore on a table while this happened.

It seems to be the start_lsn and end_lsn issue that is stopping the mysql service from starting but it could be that I am mistaken.

Below is an excerpt from the error.log . This error just repeat in the log file.

2022-08-03T16:12:13.712370Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.30-0ubuntu0.22.04.1) starting as process 82787
2022-08-03T16:12:13.741801Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-08-03T16:12:13.993798Z 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).
2022-08-03T16:12:13.993905Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
2022-08-03T16:12:14.391098Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2022-08-03T16:12:14.391463Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2022-08-03T16:12:14.391540Z 0 [ERROR] [MY-010119] [Server] Aborting
2022-08-03T16:12:14.392751Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.30-0ubuntu0.22.04.1) (Ubuntu).