mysql80 not starting
Posted by: Benjamin Wolf
Date: April 25, 2024 02:35PM
Date: April 25, 2024 02:35PM
Hey,
iam working with mysql since a few weeks. I had a problem with a table. With heidi-sql i was not able to view the data of a table. heidisql crashed everytime. so i decided to make a stupid move and cut the table .ibd file from the "C:\ProgramData\MySQL\MySQL Server 8.0\Data" directory to my desktop and tried to start the service. Service crashed instant. Then i copied the ibd file back in place. But since that, the service is not starting anymore. Is there any help or advice, what i can do? i tried the "innodb_force_recovery = 2" parameter in the my.ini file unter the [mysql] tag. it also did not change the error. i tried 1 - 4 as parameters.
The error log says the following. Please help me.
2024-04-25T20:34:37.875545Z 0 [System] [MY-010116] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe (mysqld 8.0.34) starting as process 5332
2024-04-25T20:34:37.906234Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-04-25T20:34:40.011142Z 0 [ERROR] [MY-012685] [InnoDB] Probable data corruption on page 54902. Original record on that page;
(compact record)2024-04-25T20:34:40.011908Z 0 [ERROR] [MY-012686] [InnoDB] Cannot find the dir slot for this record on that page;
(compact record)2024-04-25T20:34:40.012459Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: page0page.cc:144 thread 10216
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.
2024-04-25T20:34:40Z UTC - mysqld got exception 0x16 ;
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...
7ff6f6b5a418 mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z()
7ff6f5cce841 mysqld.exe!?print_fatal_signal@@YAXH@Z()
7ff6f5cce583 mysqld.exe!?my_server_abort@@YAXXZ()
7ff6f6b3c6aa mysqld.exe!?my_abort@@YAXXZ()
7ff6f6d0f4d9 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6e1cd09 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6e6968a mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6e6b779 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6cc3737 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6cc48f9 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6cf714b mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6c2116b mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6c978b2 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6c94c34 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6c95369 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ffbee86268a ucrtbase.dll!_o_exp()
7ffbf0ea7ac4 KERNEL32.DLL!BaseThreadInitThunk()
7ffbf176a4e1 ntdll.dll!RtlUserThreadStart()
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.
2024-04-25T20:34:40.627227Z 0 [ERROR] [MY-012684] [InnoDB] [FATAL] is_short 0, info_and_status_bits 0, offset 8080, o_offset 8, mismatch index 18446744073709551609, end_seg_len 28 parsed len 3
2024-04-25T20:34:40.628242Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: page0cur.cc:1177:ib::fatal triggered thread 5664
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.
2024-04-25T20:34:40.629152Z 0 [ERROR] [MY-012685] [InnoDB] Probable data corruption on page 1096787. Original record on that page;
(compact record)2024-04-25T20:34:40.630610Z 0 [ERROR] [MY-012686] [InnoDB] Cannot find the dir slot for this record on that page;
(compact record)2024-04-25T20:34:40.631287Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: page0page.cc:144 thread 8212
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.
2024-04-25T20:34:40.632165Z 0 [ERROR] [MY-012684] [InnoDB] [FATAL] is_short 0, info_and_status_bits 0, offset 8080, o_offset 8, mismatch index 18446744073709551609, end_seg_len 28 parsed len 3
2024-04-25T20:34:40.632969Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: page0cur.cc:1177:ib::fatal triggered thread 4128
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.
iam working with mysql since a few weeks. I had a problem with a table. With heidi-sql i was not able to view the data of a table. heidisql crashed everytime. so i decided to make a stupid move and cut the table .ibd file from the "C:\ProgramData\MySQL\MySQL Server 8.0\Data" directory to my desktop and tried to start the service. Service crashed instant. Then i copied the ibd file back in place. But since that, the service is not starting anymore. Is there any help or advice, what i can do? i tried the "innodb_force_recovery = 2" parameter in the my.ini file unter the [mysql] tag. it also did not change the error. i tried 1 - 4 as parameters.
The error log says the following. Please help me.
2024-04-25T20:34:37.875545Z 0 [System] [MY-010116] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe (mysqld 8.0.34) starting as process 5332
2024-04-25T20:34:37.906234Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-04-25T20:34:40.011142Z 0 [ERROR] [MY-012685] [InnoDB] Probable data corruption on page 54902. Original record on that page;
(compact record)2024-04-25T20:34:40.011908Z 0 [ERROR] [MY-012686] [InnoDB] Cannot find the dir slot for this record on that page;
(compact record)2024-04-25T20:34:40.012459Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: page0page.cc:144 thread 10216
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.
2024-04-25T20:34:40Z UTC - mysqld got exception 0x16 ;
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...
7ff6f6b5a418 mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z()
7ff6f5cce841 mysqld.exe!?print_fatal_signal@@YAXH@Z()
7ff6f5cce583 mysqld.exe!?my_server_abort@@YAXXZ()
7ff6f6b3c6aa mysqld.exe!?my_abort@@YAXXZ()
7ff6f6d0f4d9 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6e1cd09 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6e6968a mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6e6b779 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6cc3737 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6cc48f9 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6cf714b mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6c2116b mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6c978b2 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6c94c34 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff6f6c95369 mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ffbee86268a ucrtbase.dll!_o_exp()
7ffbf0ea7ac4 KERNEL32.DLL!BaseThreadInitThunk()
7ffbf176a4e1 ntdll.dll!RtlUserThreadStart()
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.
2024-04-25T20:34:40.627227Z 0 [ERROR] [MY-012684] [InnoDB] [FATAL] is_short 0, info_and_status_bits 0, offset 8080, o_offset 8, mismatch index 18446744073709551609, end_seg_len 28 parsed len 3
2024-04-25T20:34:40.628242Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: page0cur.cc:1177:ib::fatal triggered thread 5664
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.
2024-04-25T20:34:40.629152Z 0 [ERROR] [MY-012685] [InnoDB] Probable data corruption on page 1096787. Original record on that page;
(compact record)2024-04-25T20:34:40.630610Z 0 [ERROR] [MY-012686] [InnoDB] Cannot find the dir slot for this record on that page;
(compact record)2024-04-25T20:34:40.631287Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: page0page.cc:144 thread 8212
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.
2024-04-25T20:34:40.632165Z 0 [ERROR] [MY-012684] [InnoDB] [FATAL] is_short 0, info_and_status_bits 0, offset 8080, o_offset 8, mismatch index 18446744073709551609, end_seg_len 28 parsed len 3
2024-04-25T20:34:40.632969Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: page0cur.cc:1177:ib::fatal triggered thread 4128
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.
Subject
Written By
Posted
Sorry, you can't reply to this topic. It has been closed.
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.