当遇到MySQL启动报错，提示InnoDB数据库页可能损坏时，可以通过设置`innodb_force_recovery`来跳过恢复步骤。根据错误级别，可设置1到6的值，然后备份数据，清除数据文件，并重新初始化MySQL。在修复过程中需要注意避免写操作，并修改`innodb_purge_thread`为0。完成备份、数据清理和初始化后，导入备份数据并重新设置密码，允许远程连接。
InnoDB: Page may be an index page where index id is 8005
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 84692.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
page 已经存在损坏，需要修改innodb_force_recovery=1(通常设置为1)，使mysqld跳过恢复步骤，启动后马上逻辑导出数据，重新初始化后再导入。
innodb_force_r
最低0.47元/天 解锁文章
1843
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
