I have tried that before. below you can find the error.log. one thing that I also picked up was that if I log at the innodb_redo_log_files table it is there but no quires can be run against it all other in the performance_schema I can query.
mysql> SELECT * FROM innodb_redo_log_files;
ERROR 1146 (42S02): 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.23 sec)
mysql> show table status \G;
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
hj@le-cock:~$ tail -f /var/log/mysql/error.log
2022-08-09T08:10:55.603839Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 8.0.30-0ubuntu0.22.04.1).
2022-08-09T08:10:56.213304Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.30-0ubuntu0.22.04.1) (Ubuntu).
2022-08-09T08:10:56.637155Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.30-0ubuntu0.22.04.1) starting as process 4744
2022-08-09T08:10:56.666728Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-08-09T08:13:32.541775Z 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 445646996579.
2022-08-09T08:13:32.542049Z 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-09T08:13:32.640628Z 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-09T08:13:32.640697Z 0 [ERROR] [MY-012154] [InnoDB] Server exits.
2022-08-09T08:13:32.640723Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7531 thread 140533793121856
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.
08:13:32 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) [0x55b089ea6b61]
/usr/sbin/mysqld(print_fatal_signal(int)+0x2e4) [0x55b0894dfd14]
/usr/sbin/mysqld(my_server_abort()+0x7e) [0x55b0894dfe3e]
/usr/sbin/mysqld(my_abort()+0xe) [0x55b089e9c50e]
/usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55b08a048423]
/usr/sbin/mysqld(+0x1daeb98) [0x55b08a6b6b98]
/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) [0x55b08a176fbf]
/usr/sbin/mysqld(fil_io(IORequest const&, bool, page_id_t const&, page_size_t const&, unsigned long, unsigned long, void*, void*)+0x86) [0x55b08a177076]
/usr/sbin/mysqld(buf_read_page_low(dberr_t*, bool, unsigned long, unsigned long, page_id_t const&, page_size_t const&, bool)+0x176) [0x55b08a0d24a6]
/usr/sbin/mysqld(buf_read_page(page_id_t const&, page_size_t const&)+0x4a) [0x55b08a0d353a]
/usr/sbin/mysqld(+0x179ce54) [0x55b08a0a4e54]
/usr/sbin/mysqld(Buf_fetch_normal::get(buf_block_t*&)+0x3e6) [0x55b08a0a53d6]
/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) [0x55b08a0a6e95]
/usr/sbin/mysqld(+0x174b754) [0x55b08a053754]
/usr/sbin/mysqld(trx_rseg_init_thread(void*, unsigned long)+0x29e) [0x55b08a05e8be]
/usr/sbin/mysqld(+0x17439ad) [0x55b08a04b9ad]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc2c3) [0x7fd0bc4e22c3]
/lib/x86_64-linux-gnu/libc.so.6(+0x94b43) [0x7fd0bc169b43]
/lib/x86_64-linux-gnu/libc.so.6(+0x126a00) [0x7fd0bc1fba00]
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.