How to resolve a machine restart after the MySQL service does not run up 1067, attached to the resolution process

This person's MySQL can't run up, before still good, ask me how to recover, I did not in her problem of machine, on her own machine to try, finally solved, is now recorded here. 1, first of all her MySQL installation folder, data structure files, files all copied over (in short, according to the original MySQL directory configuration are all taken over the right, if not configured so complex, it is all in a directory that directly copied this directory line), Put it in the corresponding directory below the My.ini configuration. 2, then install the service through the command line (step reference this blog MySQL installation related) 3, start the service, the results also reported 1067, view DataDir (configured in My.ini) under the *.err log found the following

160908 17:40:52  InnoDB:Error:page 7 log sequence number 35279318566innodb:is in the future! Current system log sequence number 32193064972.innodb:your database may corrupt or we have copied the Innodbinnod B:tablespace but not the InnoDB log files. Seeinnodb:http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html

go along:http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html looked at it for a moment

4, then add Innodb_force_recovery=6 in My.ini, start service, success.

How to resolve a machine restart after the MySQL service does not run up 1067, attached to the resolution process