启动mysql的时候无法启动，报错
1067：进程意外终止
查看错误日志(错误日志为data目录下的err后缀文件)显示了如下错误：
2015-11-04 22:50:30 5044 [Note] Plugin 'FEDERATED' is disabled.
2015-11-04 22:50:30 1ac8 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.
2015-11-04 22:50:30 5044 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-04 22:50:30 5044 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-04 22:50:30 5044 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-04 22:50:30 5044 [Note] InnoDB: CPU does not support crc32 instructions
2015-11-04 22:50:30 5044 [Note] InnoDB: Initializing buffer pool, size = 24.0M
2015-11-04 22:50:30 5044 [Note] InnoDB: Completed initialization of buffer pool
2015-11-04 22:50:30 5044 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-04 22:50:30 5044 [Note] InnoDB: The log sequence numbers 13142202 and 13142202 in ibdata files do not match the log sequence number 13142212 in the ib_logfiles!
2015-11-04 22:50:30 5044 [Note] InnoDB: Database was not shutdown normally!
2015-11-04 22:50:30 5044 [Note] InnoDB: Starting crash recovery.
2015-11-04 22:50:30 5044 [Note] InnoDB: Reading tablespace information from the .ibd files...
__2015-11-04 22:50:30 5044 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace laravel/users uses space ID: 2 at filepath: .\laravel\users.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.
分析下是innodb的文件损坏了，找到mysql data目录默认是在安装目录下，但是如果安装过程中有改动，则在那个位置把底下的innodb相关文件删除即可，让mysql重建相关的文件，我删除了下面几个文件就可以恢复启动了。
ib_logfile0 ib_logfile1 ibdata1
有问题看错误日志，切忌卸载重装！__