在重裝MySQL5.6.25安裝到進行配置的時候，一直在等待服務的啟動。如果手動在系統服務啟動會提示1067錯誤，這個錯誤在網上很常見，然而我試過了很多方法均無法解決。

于是看ProgramData\MySQL Server 5.6\data下的 ***.err 錯誤日志，看出錯的部分：

2015-06-04 13:08:19 5200 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0

2015-06-04 13:08:19 5200 [ERROR] InnoDB: space header page consists of zero bytes in data file .\ibdata1

2015-06-04 13:08:19 5200 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!

2015-06-04 13:08:19 5200 [ERROR] Plugin 'InnoDB' init function returned error.

2015-06-04 13:08:19 5200 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2015-06-04 13:08:19 5200 [ERROR] Unknown/unsupported storage engine: INNODB

2015-06-04 13:08:19 5200 [ERROR] Aborting

看樣子像是文件內容出錯，刪除?ProgramData\MySQL Server 5.6\data 下的?ib_logfile0、ib_logfile1、ibdata1 三個文件。重新啟動MySQL服務，依然1067錯誤。繼續看錯誤日志：

2015-06-04 13:11:00 be8 InnoDB: Operating system error number 87 in a file operation.

InnoDB: Some operating system error numbers are described at

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html

2015-06-04 13:11:00 5932 [ERROR] InnoDB: File .\ib_logfile101: 'aio write' returned OS error 187. Cannot continue operation

于是在?ProgramData\MySQL Server 5.6的my.ini文件最后一行加上

innodb_flush_method=normal

問題得以解決。(如果還不行，就再刪除那三個文件再啟動)

總結

以上是生活随笔為你收集整理的mysql运行报错64bit_关于MySQL5.6.25在Win7 64bit下重装后无法启动的解决方法的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。