MySQL 1067 process unexpected termination failed to start

View Log Data/xxx.err

Found the following error

[ERROR] innodb:attempted to open a previously opened tablespace. Previous tablespace Mysql/innodb_index_stats uses space id:2 at filepath:. \mysql\innodb_index_stats.ibd. Cannot open tablespace Mydatabase/blackboard which uses space id:2 at filepath:. \tum_mitfahrer_app\blackboard.ibdinnodb : Error:could not open single-table tablespace file. \tum_mitfahrer_app\blackboard.ibdinnodb:we does not continue the CRAs h 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 Cannotinnod B: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 would 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, canSet innodb_force_recovery > 0 in My.cnfInnoDB:and Force InnoDB to continue crash recovery here. 

Workaround:

Add the following in the config file My.ini

[Mysqld]innodb_force_recovery = 1

The MySQL service started successfully!

But... When querying some tables, you are prompted with an error:

Table ' XXX ' doesn ' t exist

fuck!

Then change My.ini:

Innodb_force_recovery = 0

Yes! Change to 0 again! Then restart the MySQL service!

OK! Damn it, ~~~!!.

Nearly ruined the customer's data, crouching trough! Got a day!!

　　

MySQL 1067 process unexpected termination failed to start