2017-02-16 16:42:10 11376 [Note] Plugin 'FEDERATED' is disabled.

2017-02-16 16:42:10 11376 [Note] InnoDB: Using atomics to ref count buffer pool pages

2017-02-16 16:42:10 11376 [Note] InnoDB: The InnoDB memory heap is disabled

2017-02-16 16:42:10 11376 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions

2017-02-16 16:42:10 11376 [Note] InnoDB: Compressed tables use zlib 1.2.3

2017-02-16 16:42:10 11376 [Note] InnoDB: Not using CPU crc32 instructions

2017-02-16 16:42:10 11376 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2017-02-16 16:42:10 11376 [Note] InnoDB: Completed initialization of buffer pool

2017-02-16 16:42:10 11376 [Note] InnoDB: Highest supported file format is Barracuda.

2017-02-16 16:42:10 11376 [Note] InnoDB: The log sequence numbers 1793940 and 1793940 in ibdata files do not match the log sequence number 1793950 in the ib_logfiles!

2017-02-16 16:42:10 11376 [Note] InnoDB: Database was not shutdown normally!

2017-02-16 16:42:10 11376 [Note] InnoDB: Starting crash recovery.

2017-02-16 16:42:10 11376 [Note] InnoDB: Reading tablespace information from the .ibd files...

2017-02-16 16:42:10 11376 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace my/ss uses space ID: 2 at filepath: .\my\ss.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.

修改数据库引擎导致的问题

在\mysql\bin下面的my.ini中添加

innodb_force_recovery = 1

就OK了。