MySQL
mysql每次都可以正常启动，今天突然无法启动了
墨衍会员 · AI 创作全网分发 墨衍智能分发 通过墨衍一键同步至各平台 可同步平台 CSDN微信公众号微博知乎掘金百家号博客园抖音小红书 你的文章也可以这样分发 墨衍会员 ¥399起/年，写一次发全网
我也要 关注 + 加入社区日志信息是这样的：
这是正常启动时候的信息：
090216 14:46:03 mysqld started
090216 14:46:03 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
090216 14:46:03 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 18825290.
InnoDB: Doing recovery: scanned up to log sequence number 0 18825290
InnoDB: Last MySQL binlog file position 0 1797119, file name ./mysql-bin.000031
090216 14:46:04 InnoDB: Started; log sequence number 0 18825290
090216 14:46:04 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.22' socket: '/var/run/mysql/mysql.sock' port: 3306 Source distribution
紧接着就是今天的日志信息，报错了
090217 08:35:43 mysqld started
090217 8:35:43 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Error: tried to read 16384 bytes at offset 0 819200.
InnoDB: Was only able to read -1.
090217 8:36:19 InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
090217 08:36:19 mysqld ended
--------后来又尝试几次，都是报同样的日志信息
没找到类似的错误信息和解决办法，望高手不吝指教！
这是正常启动时候的信息：
090216 14:46:03 mysqld started
090216 14:46:03 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
090216 14:46:03 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 18825290.
InnoDB: Doing recovery: scanned up to log sequence number 0 18825290
InnoDB: Last MySQL binlog file position 0 1797119, file name ./mysql-bin.000031
090216 14:46:04 InnoDB: Started; log sequence number 0 18825290
090216 14:46:04 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.22' socket: '/var/run/mysql/mysql.sock' port: 3306 Source distribution
紧接着就是今天的日志信息，报错了
090217 08:35:43 mysqld started
090217 8:35:43 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Error: tried to read 16384 bytes at offset 0 819200.
InnoDB: Was only able to read -1.
090217 8:36:19 InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
090217 08:36:19 mysqld ended
--------后来又尝试几次，都是报同样的日志信息
没找到类似的错误信息和解决办法，望高手不吝指教！
...全文
相关推荐
MySQL无法启动服务的解决办法
MySQL无法启动服务的解决办法，亲身体验的，还是有用的
docker 启动mysql 成功又退出，无法正常启动.pdf
docker 启动mysql 成功又退出，无法正常启动
Mysql修改datadir导致无法启动问题解决方法
主要介绍了Mysql修改datadir导致无法启动问题解决方法,本文原因是SELINUX导致,用关闭SELINUX的方法解决了这个问题,需要的朋友可以参考下
Mysql服务无法启动的1067错误解决
无论安装何版本的mysql，在管理工具的服务中启动mysql服务时都会在中途报错。内容为：在 本地计算机 无法启动mysql服务 错误1067：进程意外中止。
MySQL 重装MySQL后, mysql服务无法启动
解决方法: 1: 先卸载mysql, 手动将其安装目录里没有删除干净的文件全部删除. 2: 将C:\ProgramData\MySQL 里有关mqsql的文件全部删除. 3: 重新安装 mysql 程序. mysql服务就可以正常启动了 您可能感兴趣的文章:Linux下卸载MySQL数据库MySQL数据库卸载的完整步骤解决MySQL安装重装时出现could not start the service mysql error:0问题的方法重装MySQL最后一步失败的完美解决方案(经验总结)MySQL的重装问题解决方法如何解决mysql重装失败方法介
