由于意外错误，MYSQL 无法启动答案

【问题标题】：MYSQL can't start due to unexpected error由于意外错误，MYSQL 无法启动
【发布时间】：2018-01-08 18:48:09
【问题描述】：

当我打开 XAMPP 并单击启动 MySQL 按钮时，它给了我一个错误，我之前启动了它，但现在它不工作了

这是日志文件中的错误，请帮助我。

2017-08-01 23:43:15 2790 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.
2017-08-01 23:43:15 10128 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-08-01 23:43:15 10128 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-08-01 23:43:15 10128 [Note] InnoDB: The InnoDB memory heap is disabled
2017-08-01 23:43:15 10128 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-08-01 23:43:15 10128 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-08-01 23:43:15 10128 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-08-01 23:43:15 10128 [Note] InnoDB: Using generic crc32 instructions
2017-08-01 23:43:15 10128 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-08-01 23:43:15 10128 [Note] InnoDB: Completed initialization of buffer pool
2017-08-01 23:43:15 10128 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-08-01 23:43:15 10128 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-08-01 23:43:15 10128 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1
2017-08-01 23:43:15 10128 [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!
2017-08-01 23:43:15 10128 [ERROR] Plugin 'InnoDB' init function returned error.
2017-08-01 23:43:15 10128 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-08-01 23:43:15 10128 [Note] Plugin 'FEEDBACK' is disabled.
2017-08-01 23:43:15 10128 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-08-01 23:43:15 10128 [ERROR] Aborting

【问题讨论】：

XAMPP - MySQL shutdown unexpectedly的可能重复
没有兄弟它没有重复它工作得很好我重新启动了我的系统，然后发生这种情况
嘿@Mohsin 今天和我有同样的问题，你能找到任何有用的答案吗？请帮忙
嘿@Mohsin 我发现了一个solution 这个问题，我希望这个解决方案对你有用，因为我也面临这个问题重启我的系统后

标签： php laravel-5

【解决方案1】：

基于这个答案 XAMPP - MySQL shutdown unexpectedly

退出 Xampp 服务器
转到您的 C:\xampp\mysql\data 目录
删除ibdata1文件
重启xampp服务器
应该可以工作

【讨论】：

我已经尝试过这个解决方案，但问题仍然存在。我也尝试过更改端口，但也没有用