InnoDB: Database was not shut down normally! mysql 无法启动

最新推荐文章于 2025-08-11 15:08:12 发布
最新推荐文章于 2025-08-11 15:08:12 发布 · 26 阅读 · 0
文章标签：

#数据库

本文记录了一次因断电导致MySQL非正常关闭的问题及解决过程。错误日志显示InnoDB内存堆被禁用，数据库未正常关闭。通过重启服务器解决了这一问题。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

今天早上来了想重启mysql

发现停止mysql失败，查看mysql错误日志，发现错误日志中：

information that should help you find out what is causing the crash.
InnoDB: The InnoDB memory heap is disabled
InnoDB: use atomic builtins.
InnoDB: Log scan progressed past the checkpoint lsn 0 9223906

InnoDB: Database was not shut down normally!


InnoDB数据库非正常关闭，造成的错误，我猜想是我正在操作数据库，断电造成的。


重启下服务器就OK了& ……&


wapysun
关注
2022-04-21 mysql-innodb存储引擎srv_start处理记录
悟世之路
04-21 688
摘要: mysql-innodb存储引擎核心处理 核心函数: srv_start: dberr_t srv_start(bool create_new_db) { lsn_t flushed_lsn; /* just for assertions */ lsn_t previous_lsn; /* output from call to create_log_files(...) */ lsn_t new_checkpoint_lsn = 0; page..
【MySQL】mysql异常宕机无法启动处理过程
hh的博客
08-14 1001
* oom异常关闭导致 MySQL5.7 启动失败。 同事导入数据时异常关闭，应该是数据量太大导致mysql崩溃，尝试重启失败了提示如下
机房断电、MySQL启动失败，InnoDB数据损坏如何恢复
reading-conference-writing
07-02 5172
当MySQL非正常关机后启动失败后，如何使用innodb_force_recovery模式启动，恢复损坏的表结构或数据库状态。 常见ERROR LOG： InnoDB: Database was not shutdown normally! InnoDB: Error: could not open single-table tablespace
mysql innodb 修复_关于mysql的innodb无法启动修复的问题
weixin_30580403的博客
01-27 2051
我启用了innodb_force_recovery = 1对mysql数据库进行损坏修复.但是mysql很不给面子,CPU一直在吃,但是就是不给我启动...导致我无法导出,并回复数据,请问目前如何是好呢下面是错误的log140718 22:22:34 [Note] Plugin 'FEDERATED' is disabled.140718 22:22:34 InnoDB: The InnoDB m...
无法启动mysqll1006_遇到数据库非正常关闭导致mySQL无法启动
weixin_33510225的博客
12-24 547
2014.04.17今天在xampp中启动mysql启动不了，点start之后变绿之后又停止了，而前面一直是正常的。我首先马上检查是不是有端口占用，但是没有占用。然后我又网上大量搜索资料查看，但是也没有找到对口的解决办法。然后我在自己同步的笔记本上启动，是可以启动的，于是我通过beyond compare比较，查看启动不了时给出的log记录：140417 12:28:08 [Note] Plugi...
centos/windows服务器，Mysql数据库表结构损坏-已解决
qq_43047483的博客
08-15 1775
影响整个InnoDB存储引擎的恢复状况，默认值为0，表示当需要恢复时执行所有的恢复操作。：断电时往往数据结构都还是好的，只是mysql事务未完成，有坏的数据在这里，所以有错误。正常启动后，注意此时我们只是跳过了启动检查，表数据仍然是坏的。有的人建议直接直接物理删除目录和里面的frm与ibd文件，找到mysql的data目录，找到目标库，删除整个目录，但是我没有成功。(SRV_FORCE_NO_UNDO_LOG_SCAN):不查看重做日志，InnoDB存储引擎会将未提交的事务视为已提交。2）跳过当前表恢复。.
mysql启动时innodb_mysql 启动时停止（innodb）
weixin_30070339的博客
01-28 280
110406 23:49:40 [Note] Plugin 'FEDERATED' is disabled.110406 23:49:40 [注意]插件federated存储引擎已经禁用InnoDB: The log sequence number in ibdata files does not matchInnoDB引擎提示：ibdata文件中的日志序列号不能匹配InnoDB: the log...
mysql崩溃恢复过程_MySQL · 引擎特性 · InnoDB 崩溃恢复过程
weixin_36352025的博客
01-19 631
在前面两期月报中，我们详细介绍了 InnoDB redo log 和 undo log 的相关知识，本文将介绍 InnoDB 在崩溃恢复时的主要流程。本文代码分析基于 MySQL 5.7.7-RC 版本，函数入口为innobase_start_or_create_for_mysql，这是一个非常冗长的函数，本文只涉及和崩溃恢复相关的代码。初始化崩溃恢复首先初始化崩溃恢复所需要的内存对象：recv...
MySQL数据库OOM问题解决记录
monang1006的博客
10-03 955
记录一次MySQL内存异常升高的解决过程
linux崩溃mysql导出_解决MySQL数据库意外崩溃导致表数据文件损坏无法启动的问题...
weixin_39946239的博客
01-27 379
问题故障：MySQL数据库意外崩溃，一直无法启动数据库。报错日志：启动报错：service mysqld restartERROR! MySQL server PID file could not be found!Starting MySQL. ERROR! The server quit without updating PID file (/www/wdlinux/mysql/var/iZ2...
解决MySQL数据库意外崩溃导致表数据文件损坏无法启动的问题
12-14
"以及"Database was not shut down normally!"这样的错误信息时，这通常意味着数据库在上次关闭时并未正常完成事务，而是突然停止，可能导致InnoDB存储引擎的表空间信息不一致。 针对这个问题，我们可以采取以下...
断电mysql从库恢复_MySQL意外断电，InnoDB数据库恢复
weixin_28811227的博客
01-19 1001
数据库在运行中突然断电，当服务器重启发现MySQL无法启动，查看日志，报错如下：151105 11:24:52 mysqld_safe Starting mysqld daemon with databases from /data/mysql/datafile151105 11:24:52 [Warning] Using unique option prefix myisam_recover i...
Oracle数据库重启后打开异常状态的检查步骤
记录数字化转型过程中技术、管理等各种酸甜苦辣......
08-09 910
1、登录服务器，切换到oracle用户下：【直接在一个节点输入即可】OPEN：数据库实例已启动、挂载并打开，可以正常使用。MOUNTED：数据库实例已启动并挂载，但未打开。//说明：CHMesPdb是数据库。STARTED：数据库实例已启动，但未挂载。STARTED：实例已启动，但未挂载。SHUTDOWN：数据库未启动。MOUNTED：数据库已挂载。OPEN：数据库已完全打开。#以上提示信息是实例未启动。
LangChain4j终极指南：Spring Boot构建企业级Agent框架
夜雨的博客
08-08 1763
LangChain4j终极指南：Spring Boot构建企业级Agent框架。实时流量看板：QPS、错误率、响应时间；资源利用率：CPU/内存/GPU使用率；LLM性能分析：Token消耗、推理延迟分布；工具热力图：调用频率、执行时长排行
MySQL 临时表与复制表
kushue的博客
08-09 724
临时表是会话级别的临时数据载体，其设计初衷是为了满足短期数据处理需求，以下从技术细节展开说明。
【redis初阶】--------Set 集合类型
mr_yuanshen的博客
08-10 937
集合类型也是保存多个字符串类型的元素的，但和列表类型不同的是，集合中1）元素之间是无序的；2）元素不允许重复；如图所示。一个集合中最多可以存储 2^32 - 1 个元素。Redis 除了支持集合内的增删查改操作，同时还支持多个集合取交集、并集、差集，合理地使用好集合类型，能在实际开发中解决很多问题。基本命令2.1 SADD将一个或者多个元素添加到 set 中。注意，重复的元素无法添加到 set 中。本次添加成功的元素个数。示例：SMEMBERS。
JAVA 分布式锁的5种实现方式
gonghua0502的专栏
08-08 651
就是先select …每次更新修改，都会自增加一，然后去更新余额时，把查出来的那个版本号，带上条件去更新，如果是上次那个版本号，就更新，如果不是，表示别人并发修改过了，就继续重试。创建一个临时节点，获取当前父节点下的子节点，如果是为最小的节点，则表示获取锁成功，否则获取锁失败，阻塞等待，则监听上一个节点。多个jvm集群的定时任务，在触发的时候，获取分布式锁，如果能够获取到分布式锁的jvm，就能够执行定时任务，没有获取到的就不能执行定时任务。当我们定时任务服务集群的情况下，有可能会同时重复执行定时任务，
达梦数据库报错-2103：无效的模式名[DAMENG]
最新发布
染落林间色的博客
08-11 162
摘要：文章提示"报错-2103：无效的模式名[DAMENG]"，解决方案是直接去掉模式名中的"DAMENG"即可。该问题是由于使用了无效的模式名导致的，简单的删除操作就能解决这个错误。
2025-06-19 12:25:09 7716 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db_wcs/baglifeinfo uses space ID: 2 at filepath: .\db_wcs\baglifeinfo.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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. 2025-06-19 12:25:10 9448 [Note] Plugin 'FEDERATED' is disabled. 2025-06-19 12:25:10 224c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 2025-06-19 12:25:10 9448 [Note] InnoDB: Using atomics to ref count buffer pool pages 2025-06-19 12:25:10 9448 [Note] InnoDB: The InnoDB memory heap is disabled 2025-06-19 12:25:10 9448 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2025-06-19 12:25:10 9448 [Note] InnoDB: Memory barrier is not used 2025-06-19 12:25:10 9448 [Note] InnoDB: Compressed tables use zlib 1.2.3 2025-06-19 12:25:10 9448 [Note] InnoDB: Not using CPU crc32 instructions 2025-06-19 12:25:10 9448 [Note] InnoDB: Initializing buffer pool, size = 8.0G 2025-06-19 12:25:10 9448 [Note] InnoDB: Completed initialization of buffer pool 2025-06-19 12:25:10 9448 [Note] InnoDB: Highest supported file format is Barracuda. 2025-06-19 12:25:10 9448 [Note] InnoDB: Log scan progressed past the checkpoint lsn 31950847983 2025-06-19 12:25:10 9448 [Note] InnoDB: Database was not shutdown normally! 2025-06-19 12:25:10 9448 [Note] InnoDB: Starting crash recovery. 2025-06-19 12:25:10 9448 [Note] InnoDB: Reading tablespace information from the .ibd files... 2025-06-19 12:25:10 9448 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db_wcs/baglifeinfo uses space ID: 2 at filepath: .\db_wcs\baglifeinfo.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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. 2025-06-19 12:25:12 7396 [Note] Plugin 'FEDERATED' is disabled. 2025-06-19 12:25:12 2484 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 2025-06-19 12:25:12 7396 [Note] InnoDB: Using atomics to ref count buffer pool pages 2025-06-19 12:25:12 7396 [Note] InnoDB: The InnoDB memory heap is disabled 2025-06-19 12:25:12 7396 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2025-06-19 12:25:12 7396 [Note] InnoDB: Memory barrier is not used 2025-06-19 12:25:12 7396 [Note] InnoDB: Compressed tables use zlib 1.2.3 2025-06-19 12:25:12 7396 [Note] InnoDB: Not using CPU crc32 instructions 2025-06-19 12:25:12 7396 [Note] InnoDB: Initializing buffer pool, size = 8.0G 2025-06-19 12:25:12 7396 [Note] InnoDB: Completed initialization of buffer pool 2025-06-19 12:25:12 7396 [Note] InnoDB: Highest supported file format is Barracuda. 2025-06-19 12:25:12 7396 [Note] InnoDB: Log scan progressed past the checkpoint lsn 31950847983 2025-06-19 12:25:12 7396 [Note] InnoDB: Database was not shutdown normally! 2025-06-19 12:25:12 7396 [Note] InnoDB: Starting crash recovery. 2025-06-19 12:25:12 7396 [Note] InnoDB: Reading tablespace information from the .ibd files... 2025-06-19 12:25:12 7396 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db_wcs/baglifeinfo uses space ID: 2 at filepath: .\db_wcs\baglifeinfo.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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. 2025-06-19 12:25:13 1704 [Note] Plugin 'FEDERATED' is disabled. 2025-06-19 12:25:13 2d94 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 2025-06-19 12:25:13 1704 [Note] InnoDB: Using atomics to ref count buffer pool pages 2025-06-19 12:25:13 1704 [Note] InnoDB: The InnoDB memory heap is disabled 2025-06-19 12:25:13 1704 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2025-06-19 12:25:13 1704 [Note] InnoDB: Memory barrier is not used 2025-06-19 12:25:13 1704 [Note] InnoDB: Compressed tables use zlib 1.2.3 2025-06-19 12:25:13 1704 [Note] InnoDB: Not using CPU crc32 instructions 2025-06-19 12:25:13 1704 [Note] InnoDB: Initializing buffer pool, size = 8.0G 2025-06-19 12:25:13 1704 [Note] InnoDB: Completed initialization of buffer pool 2025-06-19 12:25:13 1704 [Note] InnoDB: Highest supported file format is Barracuda. 2025-06-19 12:25:13 1704 [Note] InnoDB: Log scan progressed past the checkpoint lsn 31950847983 2025-06-19 12:25:13 1704 [Note] InnoDB: Database was not shutdown normally! 2025-06-19 12:25:13 1704 [Note] InnoDB: Starting crash recovery. 2025-06-19 12:25:13 1704 [Note] InnoDB: Reading tablespace information from the .ibd files... 2025-06-19 12:25:13 1704 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db_wcs/baglifeinfo uses space ID: 2 at filepath: .\db_wcs\baglifeinfo.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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. 这是一开始的报错日志信息，请帮忙分析报错1067的原因
06-20
1.**系统表空间或单表表空间文件损坏**：特别是系统表`innodb_table_stats`和`innodb_index_stats`所在的表空间文件（`mysql`数据库下的表）损坏，导致InnoDB无法打开这些表，进而使得启动过程失败。2.**元数据不...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值