I copied the following log. This may explain what happened and why. I have checked my data base. They both seems fine. It seems kind of unlikely that both would have gone bad at the same time however, it could be possible. I just don’t know enough about this.
The only thing that seems consistent is the #2002 error. Everything prior to this was normal.
MySQL log
2015-01-27 09:53:28 4688 [Note] InnoDB: The log sequence numbers 11969865 and 11969865 in ibdata files do not match the log sequence number 11974869 in the ib_logfiles!
2015-01-27 09:53:28 4688 [Note] InnoDB: Database was not shutdown normally!
2015-01-27 09:53:28 4688 [Note] InnoDB: Starting crash recovery.
2015-01-27 09:53:28 4688 [Note] InnoDB: Reading tablespace information from the .ibd files…
2015-01-27 09:53:30 4688 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace finishing/wp_commentmeta uses space ID: 11 at filepath: .\finishing\wp_commentmeta.ibd. Cannot open tablespace slowlane/wp_commentmeta which uses space ID: 11 at filepath: .\slowlane\wp_commentmeta.ibd
InnoDB: Error: could not open single-table tablespace file .\slowlane\wp_commentmeta.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.