MySQL Forums
Forum List  »  InnoDB

Re: Failed to start mysql due to start_lsn and ens_lsn issue
Posted by: Hanru Jacobs
Date: August 06, 2022 12:43AM

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.



>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Directory after starting:
&&@&&&&&&&:/var/lib/mysql/#innodb_redo# ls
'#ib_redo0' '#ib_redo13_tmp' '#ib_redo17_tmp' '#ib_redo20_tmp' '#ib_redo24_tmp' '#ib_redo28_tmp' '#ib_redo31_tmp' '#ib_redo6_tmp'
'#ib_redo10_tmp' '#ib_redo14_tmp' '#ib_redo18_tmp' '#ib_redo21_tmp' '#ib_redo25_tmp' '#ib_redo29_tmp' '#ib_redo3_tmp' '#ib_redo7_tmp'
'#ib_redo11_tmp' '#ib_redo15_tmp' '#ib_redo19_tmp' '#ib_redo22_tmp' '#ib_redo26_tmp' '#ib_redo2_tmp' '#ib_redo4_tmp' '#ib_redo8_tmp'


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Here is the table information for nnodb_redo_log_files
*************************** 56. row ***************************
Name: innodb_redo_log_files
Engine: PERFORMANCE_SCHEMA
Version: 10
Row_format: Dynamic
Rows: 0
Avg_row_length: 0
Data_length: 0
Max_data_length: 0
Index_length: 0
Data_free: 0
Auto_increment: NULL
Create_time: 2022-07-29 06:38:11
Update_time: NULL
Check_time: NULL
Collation: utf8mb4_0900_ai_ci
Checksum: NULL
Create_options:
Comment: Table 'performance_schema.innodb_redo_log_files' doesn't exist


mysql> describe innodb_redo_log_files;
+----------------+---------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+----------------+---------------+------+-----+---------+-------+
| FILE_ID | bigint | NO | | NULL | |
| FILE_NAME | varchar(2000) | NO | | NULL | |
| START_LSN | bigint | NO | | NULL | |
| END_LSN | bigint | NO | | NULL | |
| SIZE_IN_BYTES | bigint | NO | | NULL | |
| IS_FULL | tinyint | NO | | NULL | |
| CONSUMER_LEVEL | int | NO | | NULL | |
+----------------+---------------+------+-----+---------+-------+
7 rows in set (0.06 sec)

mysql>






>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

WITH innodb reccovery at 1-4


45977257 is in the future! Current system log sequence number 356434320908.
2022-08-05T16:03:12.785766Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:03:12.785791Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=23043] log sequence number 445597105764 is in the future! Current system log sequence number 356434320908.
2022-08-05T16:03:12.785788Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=25216] log sequence number 445645975053 is in the future! Current system log sequence number 356434320908.
2022-08-05T16:03:12.785828Z 0 [ERROR] [MY-012153] [InnoDB] Trying to access page number 100843007 in space 4294967278, space name innodb_undo_002, which is outside the tablespace bounds. Byte offset 0, len 16384, i/o type read. If you get this error at mysqld startup, please check that your my.cnf matches the ibdata files that you have in the MySQL server.
2022-08-05T16:03:12.785818Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:03:12.785789Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:03:12.785840Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:03:12.785867Z 0 [ERROR] [MY-012154] [InnoDB] Server exits.
2022-08-05T16:03:12.785940Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7531 thread 139901518583360
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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:03:12 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x100000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x5627ca3a1b61]
/usr/sbin/mysqld(print_fatal_signal(int)+0x2e4) [0x5627c99dad14]
/usr/sbin/mysqld(my_server_abort()+0x7e) [0x5627c99dae3e]
/usr/sbin/mysqld(my_abort()+0xe) [0x5627ca39750e]
/usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x5627ca543423]
/usr/sbin/mysqld(+0x1daeb98) [0x5627cabb1b98]
/usr/sbin/mysqld(Fil_shard::do_io(IORequest const&, bool, page_id_t const&, page_size_t const&, unsigned long, unsigned long, void*, void*)+0xc3f) [0x5627ca671fbf]
/usr/sbin/mysqld(fil_io(IORequest const&, bool, page_id_t const&, page_size_t const&, unsigned long, unsigned long, void*, void*)+0x86) [0x5627ca672076]
/usr/sbin/mysqld(buf_read_page_low(dberr_t*, bool, unsigned long, unsigned long, page_id_t const&, page_size_t const&, bool)+0x176) [0x5627ca5cd4a6]
/usr/sbin/mysqld(buf_read_page(page_id_t const&, page_size_t const&)+0x4a) [0x5627ca5ce53a]
/usr/sbin/mysqld(+0x179ce54) [0x5627ca59fe54]
/usr/sbin/mysqld(Buf_fetch_normal::get(buf_block_t*&)+0x3e6) [0x5627ca5a03d6]
/usr/sbin/mysqld(buf_page_get_gen(page_id_t const&, page_size_t const&, unsigned long, buf_block_t*, Page_fetch, ut::Location, mtr_t*, bool)+0x925) [0x5627ca5a1e95]
/usr/sbin/mysqld(+0x174b754) [0x5627ca54e754]
/usr/sbin/mysqld(trx_rseg_init_thread(void*, unsigned long)+0x29e) [0x5627ca5598be]
/usr/sbin/mysqld(+0x17439ad) [0x5627ca5469ad]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc2c3) [0x7f3d85ca72c3]
/lib/x86_64-linux-gnu/libc.so.6(+0x94b43) [0x7f3d8592eb43]
/lib/x86_64-linux-gnu/libc.so.6(+0x126a00) [0x7f3d859c0a00]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2022-08-05T16:03:13.964997Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.30-0ubuntu0.22.04.1) starting as process 85122
2022-08-05T16:03:13.994635Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-08-05T16:03:14.263979Z 1 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_system' Page [page id: space=0, page number=5] log sequence number 445646700120 is in the future! Current system log sequence number 356434320908.
2022-08-05T16:03:14.264035Z 1 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:03:14.266297Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=132] log sequence number 445647167383 is in the future! Current system log sequence number 356434320908.
........
2022-08-05T16:03:14.272247Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=116] log sequence number 445646292599 is in the future! Current system log sequence number 356434320908.
2022-08-05T16:03:14.271570Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:03:14.272344Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=37702] log sequence number 445641802021 is in the future! Current system log sequence number 356434320908.
2022-08-05T16:03:14.272371Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
....
2022-08-05T16:03:14.283547Z 0 [ERROR] [MY-012153] [InnoDB] Trying to access page number 100843007 in space 4294967278, space name innodb_undo_002, which is outside the tablespace bounds. Byte offset 0, len 16384, i/o type read. If you get this error at mysqld startup, please check that your my.cnf matches the ibdata files that you have in the MySQL server.
2022-08-05T16:03:14.283598Z 0 [ERROR] [MY-012154] [InnoDB] Server exits.
2022-08-05T16:03:14.283621Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7531 thread 140594736330304
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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:03:14 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x100000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55b151800b61]
/usr/sbin/mysqld(print_fatal_signal(int)+0x2e4) [0x55b150e39d14]
/usr/sbin/mysqld(my_server_abort()+0x7e) [0x55b150e39e3e]
/usr/sbin/mysqld(my_abort()+0xe) [0x55b1517f650e]
/usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55b1519a2423]
/usr/sbin/mysqld(+0x1daeb98) [0x55b152010b98]
/usr/sbin/mysqld(Fil_shard::do_io(IORequest const&, bool, page_id_t const&, page_size_t const&, unsigned long, unsigned long, void*, void*)+0xc3f) [0x55b151ad0fbf]
/usr/sbin/mysqld(fil_io(IORequest const&, bool, page_id_t const&, page_size_t const&, unsigned long, unsigned long, void*, void*)+0x86) [0x55b151ad1076]
/usr/sbin/mysqld(buf_read_page_low(dberr_t*, bool, unsigned long, unsigned long, page_id_t const&, page_size_t const&, bool)+0x176) [0x55b151a2c4a6]
/usr/sbin/mysqld(buf_read_page(page_id_t const&, page_size_t const&)+0x4a) [0x55b151a2d53a]
/usr/sbin/mysqld(+0x179ce54) [0x55b1519fee54]
/usr/sbin/mysqld(Buf_fetch_normal::get(buf_block_t*&)+0x3e6) [0x55b1519ff3d6]
/usr/sbin/mysqld(buf_page_get_gen(page_id_t const&, page_size_t const&, unsigned long, buf_block_t*, Page_fetch, ut::Location, mtr_t*, bool)+0x925) [0x55b151a00e95]
/usr/sbin/mysqld(+0x174b754) [0x55b1519ad754]
/usr/sbin/mysqld(trx_rseg_init_thread(void*, unsigned long)+0x29e) [0x55b1519b88be]
/usr/sbin/mysqld(+0x17439ad) [0x55b1519a59ad]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc2c3) [0x7fdef098e2c3]
/lib/x86_64-linux-gnu/libc.so.6(+0x94b43) [0x7fdef0615b43]
/lib/x86_64-linux-gnu/libc.so.6(+0x126a00) [0x7fdef06a7a00]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.htm





>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>



WITH innodb reccovery at 5

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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:12:23 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x100000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55d87317ab61]
/usr/sbin/mysqld(print_fatal_signal(int)+0x2e4) [0x55d8727b3d14]
/usr/sbin/mysqld(my_server_abort()+0x7e) [0x55d8727b3e3e]
/usr/sbin/mysqld(my_abort()+0xe) [0x55d87317050e]
/usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55d87331c423]
/usr/sbin/mysqld(+0x1daeb98) [0x55d87398ab98]
/usr/sbin/mysqld(Fil_shard::do_io(IORequest const&, bool, page_id_t const&, page_size_t const&, unsigned long, unsigned long, void*, void*)+0xc3f) [0x55d87344afbf]
/usr/sbin/mysqld(fil_io(IORequest const&, bool, page_id_t const&, page_size_t const&, unsigned long, unsigned long, void*, void*)+0x86) [0x55d87344b076]
/usr/sbin/mysqld(buf_read_page_low(dberr_t*, bool, unsigned long, unsigned long, page_id_t const&, page_size_t const&, bool)+0x176) [0x55d8733a64a6]
/usr/sbin/mysqld(buf_read_page(page_id_t const&, page_size_t const&)+0x4a) [0x55d8733a753a]
/usr/sbin/mysqld(+0x179ce54) [0x55d873378e54]
/usr/sbin/mysqld(Buf_fetch_normal::get(buf_block_t*&)+0x3e6) [0x55d8733793d6]
/usr/sbin/mysqld(buf_page_get_gen(page_id_t const&, page_size_t const&, unsigned long, buf_block_t*, Page_fetch, ut::Location, mtr_t*, bool)+0x925) [0x55d87337ae95]
/usr/sbin/mysqld(+0x174b754) [0x55d873327754]
/usr/sbin/mysqld(trx_rseg_init_thread(void*, unsigned long)+0x29e) [0x55d8733328be]
/usr/sbin/mysqld(+0x17439ad) [0x55d87331f9ad]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc2c3) [0x7fa0ccc6c2c3]
/lib/x86_64-linux-gnu/libc.so.6(+0x94b43) [0x7fa0cc8f3b43]
/lib/x86_64-linux-gnu/libc.so.6(+0x126a00) [0x7fa0cc985a00]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2022-08-05T16:12:34.069340Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.30-0ubuntu0.22.04.1) starting as process 85849
2022-08-05T16:12:34.102124Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-08-05T16:12:34.356343Z 1 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_system' Page [page id: space=0, page number=5] log sequence number 445646700120 is in the future! Current system log sequence number 356434320908.
2022-08-05T16:12:34.356429Z 1 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:12:34.401290Z 1 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_system' Page [page id: space=0, page number=0] log sequence number 396089762962 is in the future! Current system log sequence number 356434320918.
2022-08-05T16:12:34.401337Z 1 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:12:34.502234Z 1 [ERROR] [MY-011971] [InnoDB] Tablespace 'mysql' Page [page id: space=4294967294, page number=1100] log sequence number 356434414994 is in the future! Current system log sequence number 356434320918.
2022-08-05T16:12:34.502271Z 1 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:12:34.511778Z 1 [ERROR] [MY-011971] [InnoDB] Tablespace 'mysql' Page [page id: space=4294967294, page number=5] log sequence number 445647663343 is in the future! Current system log sequence number 356434320918.
2022-08-05T16:12:34.511809Z 1 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:12:34.518429Z 1 [Warning] [MY-011018] [InnoDB] Skip updating information_schema metadata in InnoDB read-only mode.
2022-08-05T16:12:34.518502Z 1 [Warning] [MY-010005] [Server] Skip re-populating collations and character sets tables in InnoDB read-only mode.
2022-08-05T16:12:34.521275Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'mysql' Page [page id: space=4294967294, page number=1360] log sequence number 424451367544 is in the future! Current system log sequence number 356434320918.
2022-08-05T16:12:34.521321Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:12:34.521519Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'mysql' Page [page id: space=4294967294, page number=682] log sequence number 424451011128 is in the future! Current system log sequence number 356434320918.
2022-08-05T16:12:34.521545Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:12:34.521646Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'mysql' Page [page id: space=4294967294, page number=1323] log sequence number 424454847526 is in the future! Current system log sequence number 356434320918.
2022-08-05T16:12:34.521671Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:12:34.527099Z 2 [Warning] [MY-011018] [Server] Skip updating information_schema metadata in InnoDB read-only mode.
2022-08-05T16:12:34.528180Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'mysql' Page [page id: space=4294967294, page number=58] log sequence number 356434349996 is in the future! Current system log sequence number 356434320918.
2022-08-05T16:12:34.528212Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:12:34.528385Z 0 [Warning] [MY-010970] [Server] Skipped updating resource group metadata in InnoDB read only mode.
2022-08-05T16:12:34.528410Z 0 [Warning] [MY-010970] [Server] Skipped updating resource group metadata in InnoDB read only mode.
2022-08-05T16:12:34.651788Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2022-08-05T16:12:34.651856Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2022-08-05T16:12:34.661661Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'mysql' Page [page id: space=4294967294, page number=1305] log sequence number 356434414994 is in the future! Current system log sequence number 356434320918.
2022-08-05T16:12:34.661702Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:12:34.662221Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'mysql' Page [page id: space=4294967294, page number=701] log sequence number 424454847526 is in the future! Current system log sequence number 356434320918.
2022-08-05T16:12:34.662250Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-08-05T16:12:34.689309Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.30-0ubuntu0.22.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu).
2022-08-05T16:12:34.689332Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '127.0.0.1' port: 33060, socket: /var/run/mysqld/mysqlx.sock

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Failed to start mysql due to start_lsn and ens_lsn issue
89
August 06, 2022 12:43AM


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.