mysql5服停止后不能启动_mysql不明原因停止后不能启动，请高手分析-CSDN博客

本文链接：https://blog.csdn.net/weixin_39884323/article/details/113716961

在尝试启动MySQL数据库时遇到错误，日志显示存在数据库页的损坏情况。具体表现为mysqld启动过程中检测到空间0的ibdata1文件第5页存在错误，可能导致数据库无法正常工作。建议进行数据库恢复操作，可能需要从备份中恢复数据。

摘要由CSDN通过智能技术生成

该楼层疑似违规已被系统折叠隐藏此楼查看此楼

mysql停止后不能再启动，请高手帮忙分析分析

2017-06-08 18:56:26 9923 mysqld_safe Starting mysqld daemon with databases from /opt/lampp/var/mysql

2017-06-08 18:56:26 139874995287808 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.

2017-06-08 18:56:26 139874995287808 [Note] /opt/lampp/sbin/mysqld (mysqld 10.1.13-MariaDB) starting as process 10069 ...

2017-06-08 18:56:26 139874995287808 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2017-06-08 18:56:26 139874995287808 [Note] InnoDB: The InnoDB memory heap is disabled

2017-06-08 18:56:26 139874995287808 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2017-06-08 18:56:26 139874995287808 [Note] InnoDB: Memory barrier is not used

2017-06-08 18:56:26 139874995287808 [Note] InnoDB: Compressed tables use zlib 1.2.8

2017-06-08 18:56:26 139874995287808 [Note] InnoDB: Using SSE crc32 instructions

2017-06-08 18:56:26 139874995287808 [Note] InnoDB: Initializing buffer pool, size = 16.0M

2017-06-08 18:56:26 139874995287808 [Note] InnoDB: Completed initialization of buffer pool

2017-06-08 18:56:26 139874995287808 [ERROR] InnoDB: Database page corruption on disk or a failed

2017-06-08 18:56:26 139874995287808 [ERROR] InnoDB: Space 0 file /opt/lampp/var/mysql/ibdata1 read of page 5.

2017-06-08 18:56:26 139874995287808 [ERROR] InnoDB: You may have to recover from a backup.

2017-06-08 18:56:26 7f372f683700 InnoDB: Page dump in ascii and hex (16384 bytes):

len 16384; hex