MySQL Forums
Forum List  »  InnoDB

mysql stopped suddenly / can't recover
Posted by: Robert Tee
Date: December 16, 2021 07:18AM

Hello, today MySQL stopped. Here's what the log file:

2021-12-16T07:16:44.027953-06:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2021-12-16T07:16:44.027968-06:00 0 [ERROR] InnoDB: Page [page id: space=0, page number=4903] log sequence number 128507606772 is in the future! Current system log sequence number 128507371550.
2021-12-16T07:16:44.027973-06:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2021-12-16T07:16:44.027992-06:00 0 [ERROR] InnoDB: Page [page id: space=0, page number=32791] log sequence number 128507638823 is in the future! Current system log sequence number 128507371550.
2021-12-16T07:16:44.027997-06:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2021-12-16T07:16:44.028016-06:00 0 [ERROR] InnoDB: Page [page id: space=0, page number=63] log sequence number 128507639104 is in the future! Current system log sequence number 128507371550.
2021-12-16T07:16:44.028022-06:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2021-12-16T07:16:44.028037-06:00 0 [ERROR] InnoDB: Page [page id: space=0, page number=32793] log sequence number 128507639104 is in the future! Current system log sequence number 128507371550.
2021-12-16T07:16:44.028042-06:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2021-12-16T07:16:44.028067-06:00 0 [ERROR] InnoDB: Page [page id: space=0, page number=4828] log sequence number 128507569937 is in the future! Current system log sequence number 128507371550.
2021-12-16T07:16:44.028072-06:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2021-12-16T07:16:44.028093-06:00 0 [ERROR] InnoDB: Page [page id: space=0, page number=192] log sequence number 128507513884 is in the future! Current system log sequence number 128507371550.
2021-12-16T07:16:44.028100-06:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2021-12-16T07:16:44.028115-06:00 0 [ERROR] InnoDB: Page [page id: space=0, page number=32781] log sequence number 128507513884 is in the future! Current system log sequence number 128507371550.
2021-12-16T07:16:44.028120-06:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2021-12-16T07:16:44.028136-06:00 0 [ERROR] InnoDB: Page [page id: space=0, page number=382] log sequence number 128507692718 is in the future! Current system log sequence number 128507371550.
2021-12-16T07:16:44.028142-06:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2021-12-16T07:16:44.028163-06:00 0 [ERROR] InnoDB: Trying to access page number 4294967295 in space 0, space name innodb_system, 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.
2021-12-16T07:16:44.028168-06:00 0 [ERROR] InnoDB: Server exits


Nothing seemingly caused this to happen. Can someone please help me in understanding step by step in how to recover?

Options: ReplyQuote


Subject
Views
Written By
Posted
mysql stopped suddenly / can't recover
546
December 16, 2021 07:18AM


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.