[MariaDB]因为机房断电后 MYSQL无法启动

以下为报错信息，麻烦高手给个解决办法


160330 11:45:57 [Note] InnoDB: Using mutexes to ref count buffer pool pages
160330 11:45:57 [Note] InnoDB: The InnoDB memory heap is disabled
160330 11:45:57 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
160330 11:45:57 [Note] InnoDB: Compressed tables use zlib 1.2.3
160330 11:45:57 [Note] InnoDB: Not using CPU crc32 instructions
160330 11:45:57 [Note] InnoDB: Initializing buffer pool, size = 128.0M
160330 11:45:58 [Note] InnoDB: Completed initialization of buffer pool
160330 11:45:58 [Note] InnoDB: Highest supported file format is Barracuda.
160330 11:45:58 [Note] InnoDB: The log sequence numbers 3127058 and 3127058 in ibdata files do not match the log sequence number 3127068 in the ib_logfiles!
160330 11:45:58 [Note] InnoDB: Database was not shutdown normally!
160330 11:45:58 [Note] InnoDB: Starting crash recovery.
160330 11:45:58 [Note] InnoDB: Reading tablespace information from the .ibd files...

图片：QQ截图20160330135710.png

上面都是note报告，没有error信息，可以删除data下的.err文件重新启动后看报错，如果有innodb数据表突然断电很容易损坏临时数据，先看看有没有报错再说吧。

动力火锅：上面都是note报告，没有error信息，可以删除data下的.err文件重新启动后看报错，如果有innodb数据表突然断电很容易损坏临时数据，先看看有没有报错再说吧。回到原帖

删除后的报错信息是


160330 19:09:19 [Note] InnoDB: Using mutexes to ref count buffer pool pages
160330 19:09:19 [Note] InnoDB: The InnoDB memory heap is disabled
160330 19:09:19 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
160330 19:09:19 [Note] InnoDB: Compressed tables use zlib 1.2.3
160330 19:09:19 [Note] InnoDB: Not using CPU crc32 instructions
160330 19:09:19 [Note] InnoDB: Initializing buffer pool, size = 128.0M
160330 19:09:19 [Note] InnoDB: Completed initialization of buffer pool
160330 19:09:19 [Note] InnoDB: Highest supported file format is Barracuda.
160330 19:09:19 [Note] InnoDB: The log sequence numbers 3127058 and 3127058 in ibdata files do not match the log sequence number 3127068 in the ib_logfiles!
160330 19:09:19 [Note] InnoDB: Database was not shutdown normally!
160330 19:09:19 [Note] InnoDB: Starting crash recovery.
160330 19:09:19 [Note] InnoDB: Reading tablespace information from the .ibd files...
160330 19:09:19 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace 1yyg/go_article uses space ID: 7 at filepath: .\1yyg\go_article.ibd. Cannot open tablespace mx/wp_wpgmza which uses space ID: 7 at filepath: .\mx\wp_wpgmza.ibd
InnoDB: Error: could not open single-table tablespace file .\mx\wp_wpgmza.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.
看不懂。。。。