[HELP] MYSQL InnoDB: Missing MLOG_CHECKPOINT

jazz1611

Hello,

I'm facing that issues. I tried remove the ib_logfile0 vs ib_logfile1 and restart mysql but still failed. Someone can help me? Thanks.

Error log

2020-09-01 17:30:49 0 [Note] InnoDB: Using Linux native AIO
2020-09-01 17:30:49 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-01 17:30:49 0 [Note] InnoDB: Uses event mutexes
2020-09-01 17:30:49 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2020-09-01 17:30:49 0 [Note] InnoDB: Number of pools: 1
2020-09-01 17:30:49 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-09-01 17:30:49 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2020-09-01 17:30:49 0 [Note] InnoDB: Completed initialization of buffer pool
2020-09-01 17:30:49 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-09-01 17:30:49 0 [ERROR] InnoDB: Missing MLOG_CHECKPOINT at 973050640940 between the checkpoint 973050599515 and the end 973050640896.
2020-09-01 17:30:49 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2020-09-01 17:30:49 0 [Note] InnoDB: Starting shutdown...
2020-09-01 17:30:50 0 [ERROR] Plugin 'InnoDB' init function returned error.
2020-09-01 17:30:50 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-09-01 17:30:50 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-09-01 17:30:50 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2020-09-01 17:30:50 0 [ERROR] Aborting

jazz1611

After restart, i get this error

2020-09-01 21:53:04 0 [Note] InnoDB: Using Linux native AIO
2020-09-01 21:53:04 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-01 21:53:04 0 [Note] InnoDB: Uses event mutexes
2020-09-01 21:53:04 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2020-09-01 21:53:04 0 [Note] InnoDB: Number of pools: 1
2020-09-01 21:53:04 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-09-01 21:53:04 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2020-09-01 21:53:04 0 [Note] InnoDB: Initializing buffer pool, total size = 1G, instances = 8, chunk size = 128M
2020-09-01 21:53:04 0 [Note] InnoDB: Completed initialization of buffer pool
2020-09-01 21:53:04 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-09-01 21:53:05 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=144282911586
2020-09-01 21:53:05 0 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace innodb_system page [page id: space=0, page number=351]. You may have to recover from a backup.
2020-09-01 21:53:05 0 [Note] InnoDB: Page dump in ascii and hex (16384 bytes):
................
InnoDB: End of page dump
2020-09-01 21:53:05 0 [Note] InnoDB: Uncompressed page, stored checksum in field1 1555871297, calculated checksums for field1: crc32 1555871297, innodb 2495496133,  page type 2 == UNDO LOG.none 3735928559, stored checksum in field2 1105759478, calculated checksums for field2: crc32 1555871297, innodb 1575272319, none 3735928559,  page LSN 33 2548987875, low 4 bytes of LSN at page end 2548986805, page number (if stored to page already) 351, space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an undo log page
2020-09-01 21:53:05 0 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
200901 21:53:05 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.4.8-MariaDB-log
key_buffer_size=536870912
read_buffer_size=2097152
max_used_connections=0
max_threads=502
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2592793 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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 = 0x0 thread_stack 0x60000
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x29)[0x555a2612d1b9]
mysys/stacktrace.c:270(my_print_stacktrace)[0x555a25c5544f]
sigaction.c:0(__restore_rt)[0x2b65a71db630]
/www/server/mysql/bin/mysqld(+0xb1754d)[0x555a25eee54d]
log/log0recv.cc:2122(recv_recover_corrupt_page(page_id_t))[0x555a2600785a]
buf/buf0buf.cc:6199(buf_page_io_complete(buf_page_t*, bool, bool))[0x555a2602459f]
buf/buf0rea.cc:205(buf_read_page_low(dberr_t*, bool, unsigned long, unsigned long, page_id_t, unsigned long, bool, bool))[0x555a2602502f]
include/sync0types.h:1129(simple_counter<unsigned long>::add(unsigned long))[0x555a260095ac]
buf/buf0buf.cc:4439(buf_page_get_gen(page_id_t, unsigned long, unsigned long, buf_block_t*, unsigned long, char const*, unsigned int, mtr_t*, dberr_t*))[0x555a25fc4c1b]
include/trx0undo.ic:118(trx_undo_page_get)[0x555a25fb24e8]
trx/trx0rseg.cc:430(trx_undo_lists_init)[0x555a25fbeb05]
trx/trx0trx.cc:744(trx_lists_init_at_db_start())[0x555a25f8e91b]
srv/srv0start.cc:1891(srv_start(bool))[0x555a25e93c58]
handler/ha_innodb.cc:4261(innodb_init(void*))[0x555a25c583d1]
sql/handler.cc:557(ha_initialize_handlerton(st_plugin_int*))[0x555a25a732b8]
sql/sql_plugin.cc:1438(plugin_initialize(st_mem_root*, st_plugin_int*, int*, char**, bool))[0x555a25a74372]
sql/sql_plugin.cc:1720(plugin_init(int*, char**, int))[0x555a259a9860]
sql/mysqld.cc:5203(init_server_components())[0x555a259ae342]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x2b65a8f87555]
/www/server/mysql/bin/mysqld(+0x5cc047)[0x555a259a3047]
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.
Writing a core file...
Working directory at /www/server/data
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            unlimited            unlimited            bytes
Max core file size        0                    unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             63457                63457                processes
Max open files            65535                65535                files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       63457                63457                signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0
Max realtime priority     0                    0
Max realtime timeout      unlimited            unlimited            us
Core pattern: core

aaPanel_Jose

jazz1611
It seems that your database has table corruption causing this problem. Please backup the data directory /www/server/data first

Add the following parameters to the mysql configuration
[mysql] innodb_force_recovery = 6

Then restart MySQL and immediately use mysqldump to export the data to the database. After completion, remove innodb_force_recovery, then re-create the database and import the data.

jazz1611

aaPanel_Jose
hello, i can export all database to .sql and remove "innodb_force_recovery" then restart mysql is failed again. Also tried remove database is success but it folder still existed in /www/server/data/(database). should i uninstall mysql and install again?

aaPanel_Jose

jazz1611
You can uninstall the mysql and reinstall after backing up the mysql data directory /www/server/data

aaP_stalker_torrent40

And my trouble happened, 4 databases broke down, the power was turned off, and they started it up, the database is broken, nothing helps, I'm very upset, everything is in a bad way

2022-10-26T18:22:04.982004Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_package_fields in the cache. Attempting to load the tablespace with space id 8149
2022-10-26T18:22:04.983187Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_package_filters in the cache. Attempting to load the tablespace with space id 8177
2022-10-26T18:22:04.984677Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_package_filters_map in the cache. Attempting to load the tablespace with space id 8179
2022-10-26T18:22:04.985342Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_package_filters_values in the cache. Attempting to load the tablespace with space id 8178
2022-10-26T18:22:04.986482Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_package_groups in the cache. Attempting to load the tablespace with space id 8211
2022-10-26T18:22:04.987665Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_package_images in the cache. Attempting to load the tablespace with space id 8152
2022-10-26T18:22:04.988639Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_packages in the cache. Attempting to load the tablespace with space id 8212
2022-10-26T18:22:04.990014Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_packages_ads in the cache. Attempting to load the tablespace with space id 8163
2022-10-26T18:22:04.991137Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_packages_hosting in the cache. Attempting to load the tablespace with space id 8162
2022-10-26T18:22:04.992258Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_packages_products in the cache. Attempting to load the tablespace with space id 8147
2022-10-26T18:22:04.993277Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_paymethods in the cache. Attempting to load the tablespace with space id 8102
2022-10-26T18:22:04.994619Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_payouts in the cache. Attempting to load the tablespace with space id 8111
2022-10-26T18:22:04.995906Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_product_options in the cache. Attempting to load the tablespace with space id 8150
2022-10-26T18:22:04.997338Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_purchases in the cache. Attempting to load the tablespace with space id 8224
2022-10-26T18:22:04.998925Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_referral_rules in the cache. Attempting to load the tablespace with space id 8164
2022-10-26T18:22:04.999955Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_reviews in the cache. Attempting to load the tablespace with space id 8151
2022-10-26T18:22:05.001156Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_ship_orders in the cache. Attempting to load the tablespace with space id 8110
2022-10-26T18:22:05.002403Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_shipping in the cache. Attempting to load the tablespace with space id 8107
2022-10-26T18:22:05.003424Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_support_departments in the cache. Attempting to load the tablespace with space id 8125
2022-10-26T18:22:05.004944Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_support_fields in the cache. Attempting to load the tablespace with space id 8131
2022-10-26T18:22:05.006475Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_support_notify in the cache. Attempting to load the tablespace with space id 8133
2022-10-26T18:22:05.007394Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_support_ratings in the cache. Attempting to load the tablespace with space id 8132
2022-10-26T18:22:05.008869Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_support_replies in the cache. Attempting to load the tablespace with space id 8112
2022-10-26T18:22:05.010918Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_support_request_log in the cache. Attempting to load the tablespace with space id 8168
2022-10-26T18:22:05.012011Z 90 [ERROR] InnoDB: Failed to find tablespace for table sql_stalker_torr.nexus_support_requests in the cache. Attempting to load the tablespace with space id 8124
2022-10-26T18:22:05.013349Z 90 [ERROR]

aaPanel_Kern

aaP_stalker_torrent40
Hello, it is recommended to find a professional data recovery company to help you recover

aaP_stalker_torrent40

It turns out that I need to turn to professionals every time when the lights are turned off urgently? Or maybe there is a problem with the panel?

aaP_stalker_torrent40

I specifically turned off the power of the server in test mode, and then turned it on,
databases crash.
I've already suffered so much, destroyed four sites
I wish you the very best.
Glory to Ukraine

aaP_stalker_torrent40

For those who break innodb

delete
innodb_data_home_dir = /www/server/data innodb_data_file_path = ibdata1:10M:autoextend innodb_log_group_home_dir = /www/server/data innodb_buffer_pool_size = 256M innodb_log_file_size = 128M innodb_log_buffer_size = 32M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 innodb_max_dirty_pages_pct = 90 innodb_read_io_threads = 2 innodb_write_io_threads = 2
and prescribe
innodb=OFF default-storage-engine = MyISAM
service mysql restart
And everything works

aaP_stalker_torrent40

I forgot to write, before that you need to convert to MyISAM