[MAMP]MySQLが起動しない「InnoDB: Attempted to open a previously opened tablespace.」のエラー

事象

MAMPで突然MySQLが起動しなくなりました。/Applications/MAMP/logs/mysql_error_log.errを確認したら下記のエラーが出力されていました。

2016-12-09 10:33:50 42369 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace [DB名]/[テーブル名]_st which uses space ID: 1 at filepath: ./[DB名]/[テーブル名]_st.ibd
2016-12-09 10:33:50 7fff9a4913c0  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./[DB名]/[テーブル名]_st.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.
161209 10:33:50 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended

対処方法についてご確認お願いします。

解決方法

エラーメッセージにも記載されているとおり、あるDBのテーブルが壊れてしまったようです。

/Applications/MAMP/db/mysql[バージョン]/[壊れたDB名]のフォルダを削除すれば起動できます。

もちろん、起動後はDBは削除されている状態ですので、再度DBを作り直す必要がありますのでその点は状況に合わせて判断してください。