时间：2021-07-01 10:21:17 帮助过：50人阅读
其中：
添加innodb_force_recovery=1或innodb_force_recovery=4后，会弹出mysqld.exe已停止工作的新问题。
在线求解
以下是Logs中的错误报告：
2016-04-28 14:33:51 1a84 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.
2016-04-28 14:33:52 6788 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-04-28 14:33:52 6788 [Note] InnoDB: The InnoDB memory heap is disabled
2016-04-28 14:33:52 6788 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-04-28 14:33:52 6788 [Note] InnoDB: Memory barrier is not used
2016-04-28 14:33:52 6788 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-04-28 14:33:52 6788 [Note] InnoDB: Using generic crc32 instructions
2016-04-28 14:33:52 6788 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-04-28 14:33:52 6788 [Note] InnoDB: Completed initialization of buffer pool
2016-04-28 14:33:52 6788 [Note] InnoDB: Restoring page 0 of tablespace 0
2016-04-28 14:33:52 6788 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2016-04-28 14:33:52 6788 [ERROR] InnoDB: space header page consists of zero bytes in data file C:xamppmysqldataibdata1
2016-04-28 14:33:52 6788 [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!
2016-04-28 14:33:52 6788 [ERROR] Plugin 'InnoDB' init function returned error.
2016-04-28 14:33:52 6788 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2016-04-28 14:33:52 6788 [Note] Plugin 'FEEDBACK' is disabled.
2016-04-28 14:33:52 6788 [ERROR] Unknown/unsupported storage engine: InnoDB
2016-04-28 14:33:52 6788 [ERROR] Aborting
以下是xampp控制台中的错误报告：
14:35:07 [mysql] Attempting to start MySQL app...
14:35:08 [mysql] Status change detected: running
14:35:08 [mysql] Status change detected: stopped
14:35:08 [mysql] Error: MySQL shutdown unexpectedly.
14:35:08 [mysql] This may be due to a blocked port, missing dependencies,
14:35:08 [mysql] improper privileges, a crash, or a shutdown by another method.
14:35:08 [mysql] Press the Logs button to view error logs and check
14:35:08 [mysql] the Windows Event Viewer for more clues
14:35:08 [mysql] If you need more help, copy and post this
14:35:08 [mysql] entire log window on the forums
已尝试：
删除data中的ibdata1
添加innodb_force_recovery=1或innodb_force_recovery=4
修改port3306为其他
都不起作用。
其中：
添加innodb_force_recovery=1或innodb_force_recovery=4后，会弹出mysqld.exe已停止工作的新问题。
在线求解
以下是Logs中的错误报告：
2016-04-28 14:33:51 1a84 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.
2016-04-28 14:33:52 6788 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-04-28 14:33:52 6788 [Note] InnoDB: The InnoDB memory heap is disabled
2016-04-28 14:33:52 6788 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-04-28 14:33:52 6788 [Note] InnoDB: Memory barrier is not used
2016-04-28 14:33:52 6788 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-04-28 14:33:52 6788 [Note] InnoDB: Using generic crc32 instructions
2016-04-28 14:33:52 6788 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-04-28 14:33:52 6788 [Note] InnoDB: Completed initialization of buffer pool
2016-04-28 14:33:52 6788 [Note] InnoDB: Restoring page 0 of tablespace 0
2016-04-28 14:33:52 6788 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2016-04-28 14:33:52 6788 [ERROR] InnoDB: space header page consists of zero bytes in data file C:xamppmysqldataibdata1
2016-04-28 14:33:52 6788 [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!
2016-04-28 14:33:52 6788 [ERROR] Plugin 'InnoDB' init function returned error.
2016-04-28 14:33:52 6788 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2016-04-28 14:33:52 6788 [Note] Plugin 'FEEDBACK' is disabled.
2016-04-28 14:33:52 6788 [ERROR] Unknown/unsupported storage engine: InnoDB
2016-04-28 14:33:52 6788 [ERROR] Aborting
以下是xampp控制台中的错误报告：
14:35:07 [mysql] Attempting to start MySQL app...
14:35:08 [mysql] Status change detected: running
14:35:08 [mysql] Status change detected: stopped
14:35:08 [mysql] Error: MySQL shutdown unexpectedly.
14:35:08 [mysql] This may be due to a blocked port, missing dependencies,
14:35:08 [mysql] improper privileges, a crash, or a shutdown by another method.
14:35:08 [mysql] Press the Logs button to view error logs and check
14:35:08 [mysql] the Windows Event Viewer for more clues
14:35:08 [mysql] If you need more help, copy and post this
14:35:08 [mysql] entire log window on the forums
重置mysql的启动配置 删除所有ibdata1 ibdataXX 和ib_logfile0 ib_logfile1 ..等等 重启mysql
卸载了重装吧