MySQL Service Startup error: 1067, unexpected Process Termination

Find the Error log, the default log in: C: ProgramDataMySQLMySQLServer5.6dataLI-PC. err Error log is as follows: InnoDB: Error: couldnotopensingle-tabletablespacefile.mysqlinnodb_index_stats.ibdInnoDB: Wedonotcontinuethecrashrecovery, because

Find the Error log, the default log in: C: \ ProgramData \ MySQL Server 5.6 \ data \ LI-PC.err Error log is as follows: InnoDB: Error: cocould not open single-table tablespace file. \ mysql \ innodb_index_stats.ibdInnoDB: We do not continue the crash recovery, because

Find the error log. The default log is:
C: \ ProgramData \ MySQL Server 5.6 \ data \ LI-PC.err
The error log is as follows:

InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibdInnoDB: We do not continue the crash recovery, because the table may becomeInnoDB: 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 cannotInnoDB: 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 normalInnoDB: crash recovery and ignore that table.InnoDB: 3) If the file system or the disk is broken, and you cannot removeInnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnfInnoDB: and force InnoDB to continue crash recovery here.140424  9:34:06 [Note] Plugin 'FEDERATED' is disabled.140424  9:34:06 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.140424  9:34:06 InnoDB: The InnoDB memory heap is disabled140424  9:34:06 InnoDB: Mutexes and rw_locks use Windows interlocked functions140424  9:34:06 InnoDB: Compressed tables use zlib 1.2.3140424  9:34:06 InnoDB: CPU does not support crc32 instructions140424  9:34:06 InnoDB: Initializing buffer pool, size = 49.0M140424  9:34:06 InnoDB: Completed initialization of buffer pool140424  9:34:06 InnoDB: highest supported file format is Barracuda.InnoDB: The log sequence number in ibdata files does not matchInnoDB: the log sequence number in the ib_logfiles!140424  9:34:06  InnoDB: Database was not shut down normally!InnoDB: Starting crash recovery.InnoDB: Reading tablespace information from the .ibd files...140424  9:34:06 [ERROR] InnoDB:  InnoDB: Error: Attempt to open a tablespace previously opened.Previous tablespace hibernate/teacher uses space ID: 2 at filepath: .\hibernate\teacher.ibdCannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibdInnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibdInnoDB: We do not continue the crash recovery, because the table may becomeInnoDB: 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 cannotInnoDB: 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 normalInnoDB: crash recovery and ignore that table.InnoDB: 3) If the file system or the disk is broken, and you cannot removeInnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnfInnoDB: and force InnoDB to continue crash recovery here.

Solution: only from the above information, innodb's data file is corrupted. In the data directory where Mysql is installed: C: \ ProgramData \ MySQL Server 5.6 \ data, generally, directly Delete ibdata1, ib_logfile0 ,.. and so on.