innodb启动失败无法重启的处理方法

电脑死机，重启后发现mysql没有启动成功，查看错误日志发现是innodb出现问题导致mysql启动失败

$ mysql.server start
Starting MySQL
. ERROR! The server quit without updating PID file (/usr/local/var/mysql/fdipzonedeMacBook-Air.local.pid).22:08:37 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
2016-04-23 22:08:38 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-04-23 22:08:38 0 [Note] /usr/local/Cellar/mysql/5.6.24/bin/mysqld (mysqld 5.6.24) starting as process 3604 ...
2016-04-23 22:08:38 3604 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
2016-04-23 22:08:38 3604 [Note] Plugin 'FEDERATED' is disabled.
2016-04-23 22:08:38 3604 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-04-23 22:08:38 3604 [Note] InnoDB: The InnoDB memory heap is disabled
2016-04-23 22:08:38 3604 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-04-23 22:08:38 3604 [Note] InnoDB: Memory barrier is not used
2016-04-23 22:08:38 3604 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-04-23 22:08:38 3604 [Note] InnoDB: Using CPU crc32 instructions
2016-04-23 22:08:38 3604 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-04-23 22:08:38 3604 [Note] InnoDB: Completed initialization of buffer pool
2016-04-23 22:08:38 3604 [Note] InnoDB: Highest supported file format is Barracuda.
2016-04-23 22:08:38 3604 [Note] InnoDB: Log scan progressed past the checkpoint lsn 68929933440
2016-04-23 22:08:38 3604 [Note] InnoDB: Database was not shutdown normally!
2016-04-23 22:08:38 3604 [Note] InnoDB: Starting crash recovery.
2016-04-23 22:08:38 3604 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-04-23 22:08:38 3604 [ERROR] InnoDB: checksum mismatch in tablespace ./test_user/user_recommend_code#P#pmax.ibd (table test_user/user_recommend_code#P#pmax)
2016-04-23 22:08:38 3604 [Note] InnoDB: Page size:1024 Pages to analyze:64
2016-04-23 22:08:38 3604 [Note] InnoDB: Page size: 1024, Possible space_id count:0
2016-04-23 22:08:38 3604 [Note] InnoDB: Page size:2048 Pages to analyze:48
2016-04-23 22:08:38 3604 [Note] InnoDB: Page size: 2048, Possible space_id count:0
2016-04-23 22:08:38 3604 [Note] InnoDB: Page size:4096 Pages to analyze:24
2016-04-23 22:08:38 3604 [Note] InnoDB: Page size: 4096, Possible space_id count:0
2016-04-23 22:08:38 3604 [Note] InnoDB: Page size:8192 Pages to analyze:12
2016-04-23 22:08:38 3604 [Note] InnoDB: Page size: 8192, Possible space_id count:0
2016-04-23 22:08:38 3604 [Note] InnoDB: Page size:16384 Pages to analyze:6
2016-04-23 22:08:38 3604 [Note] InnoDB: VALID: space:2947354 page_no:3 page_size:16384
2016-04-23 22:08:38 3604 [Note] InnoDB: Page size: 16384, Possible space_id count:1
2016-04-23 22:08:38 3604 [Note] InnoDB: space_id:2947354, Number of pages matched: 1/1 (16384)
2016-04-23 22:08:38 3604 [Note] InnoDB: Chosen space:29473542016-04-23 22:08:38 3604 [Note] InnoDB: Restoring page 0 of tablespace 2947354
2016-04-23 22:08:38 3604 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 2947354
2016-04-23 22:08:38 7fff79b9e300 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./test_user/user_recommend_code#P#pmax.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

解决

如果数据不重要或已经有备份，只需要恢复mysql启动
1. 进入mysql目录，一般是：/usr/local/var/mysql/
2. 删除ib_logfile*
3. 删除ibdata*
4. 删除所有数据库物理目录（例如数据库为test_db,则执行rm -rf test_db）
5. 重启动mysql
6. 重新建立数据库或使用备份覆盖
如果数据很重要且没有备份
可以使用innodb_force_recovery参数，使mysqld跳过恢复步骤，启动mysqld，将数据导出然后重建数据库。
innodb_force_recovery 可以设置为1-6，大的数字包含前面所有数字的影响
1. (SRV_FORCE_IGNORE_CORRUPT):忽略检查到的corrupt页。
2. (SRV_FORCE_NO_BACKGROUND):阻止主线程的运行，如主线程需要执行full purge操作，会导致crash。
3. (SRV_FORCE_NO_TRX_UNDO):不执行事务回滚操作。
4. (SRV_FORCE_NO_IBUF_MERGE):不执行插入缓冲的合并操作。
5. (SRV_FORCE_NO_UNDO_LOG_SCAN):不查看重做日志，InnoDB存储引擎会将未提交的事务视为已提交。
6. (SRV_FORCE_NO_LOG_REDO): 不执行前滚的操作。

在my.cnf(windows是my.ini)中加入

innodb_force_recovery = 6
innodb_purge_thread = 0

重启mysql

这时只可以执行select,create,drop操作，但不能执行insert,update,delete操作
执行逻辑导出，完成后将innodb_force_recovery=0，innodb_purge_threads=1，然后重建数据库，最后把导出的数据重新导入

innodb启动失败无法重启的处理方法相关推荐

mysql innodb启动失败_关于mysql innodb启动失败无法重启的处理方法讲解
电脑在使用过程中死机,重启后发现mysql没有启动成功,查看错误日志发现是innodb出现问题导致mysql启动失败. 错误日志$ mysql.server start Starting MySQL ...
win10无限重启服务器,win10系统更新kb4284835补丁失败无限重启的解决方法
‍‍ 微软发布最新KB4284835补丁,但是win10系统更新补丁却失败出现无限重启的问题,kb4284835更新失败该怎么解决呢?针对此故障问题,接下去教程和大家分享win10系统更新kb4284 ...
apmserv mysql5.1启动失败_apmserv启动失败的原因以及解决方法
在本地测试环境当中,很多人遇到过apmserv集成软件启动失败的问题:有apache启动失败.mysql启动失败:系统天堂小编针对apmserv启动失败的原因整理了对应的解决方法在这里分享给大家. 现 ...
Failed to start LSB 网络服务启动失败的四种解决方法
1.执行 service network restart 出现以下错误 Restarting network (via systemctl): Job for network.service fai ...
MySQL启动失败排查过程及解决方法
MySQL 启动失败的常见原因 MySQL 启动失败的最常见的原因有两类,分别是无法访问系统资源和参数设置错误造成的,下面分别分析如下. 一.无法访问系统资源 MySQL 不能访问启动需要的资源是造成 ...
mysql innodb启动失败_mysql启动失败
环境: mysql55 redhat5.7 首先阐明,去年用arch时玩mariadb,用的很顺风顺水.... 但是今年在arch下我的mariadb也一直没安装成功,情况基本跟现在一样...之前没有 ...
springboot启动失败的原因及其解决方法
前言: 对于springboot的启动失败,相信大家都有经历,但是为什么会启动失败,以及怎么解决都只能通过日志进行查看,在这里,我会将常见的springboot启动失败的报错一一展示报错: 1:端口 ...
jira mysql 启动失败_重启机器导致mysql启动失败
一.问题二.常见解决方案网上的解决方法大致为 ①空间不足(df -h 查看) ②权限不足(/var/lib文件夹)chown -R mysql:mysql /vdb1/lib/ ③修改my.cnf ...
关于mysql启动失败 3534 报错解决方法
我的MySQL安装好后,使用一周后的同一时间必定报连接失败,然后查找发现是MySQL本地服务没有启动(应该是一段时间会自动关闭?),手动启动该服务项提示: 尝试在管理员身份下启动终端,并输入:net ...

innodb启动失败无法重启的处理方法

innodb启动失败无法重启的处理方法相关推荐

最新文章

热门文章