当我在通过MAMP在本地托管的WordPress页面上工作时，我的MacBook突然关闭（电量不足），现在我弄得一团糟，我无法理清。帮助
这是mysql_error_log.err文件告诉我的内容：
2017-01-27 22:34:27 700000934000 InnoDB: Recalculation of persistent statistics requested for table "eit_wp"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
170225 16:15:36 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
2017-02-25 16:15:36 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-02-25 16:15:36 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-02-25 16:15:36 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.34) starting as process 86306 ...
2017-02-25 16:15:36 86306 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
2017-02-25 16:15:36 86306 [Warning] One can only use the --user switch if running as root
2017-02-25 16:15:37 86306 [Note] Plugin 'FEDERATED' is disabled.
2017-02-25 16:15:37 86306 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-02-25 16:15:37 86306 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-25 16:15:37 86306 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-02-25 16:15:37 86306 [Note] InnoDB: Memory barrier is not used
2017-02-25 16:15:37 86306 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-02-25 16:15:37 86306 [Note] InnoDB: Using CPU crc32 instructions
2017-02-25 16:15:37 86306 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-02-25 16:15:37 86306 [Note] InnoDB: Completed initialization of buffer pool
2017-02-25 16:15:37 86306 [Note] InnoDB: Highest supported file format is Barracuda.
2017-02-25 16:15:37 86306 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 4566660 in the ib_logfiles!
2017-02-25 16:15:37 86306 [Note] InnoDB: Database was not shutdown normally!
2017-02-25 16:15:37 86306 [Note] InnoDB: Starting crash recovery.
2017-02-25 16:15:37 86306 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-02-25 16:15:38 86306 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace eit_wp/wp_usermeta uses space ID: 2 at filepath: ./eit_wp/wp_usermeta.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: ./mysql/innodb_index_stats.ibd
2017-02-25 16:15:38 7fff74e0d000 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 ./mysql/innodb_index_stats.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.
170225 16:15:38 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
从我看到的内容来看，不存在权限问题。获取信息显示我对文件具有读写功能。我错过了什么吗？
我找到了innodb_index_stats.ibd。将它移出目录什么也没做。为什么呢？
我无法编辑my.cnf文件。它被锁定了。再一次，不是我的强项，所以我迷失了......
TimeMachine不会给我一个不间断的MAMP版本和网站。
我是一名设计师，所以这让我很困惑。我不知道如何让网站恢复运行......或者我丢失了所有内容并且搞砸了？我在mysql56文件夹中有一个完整的wp_文件夹。
删除ib_logfiles会启动MySQL，但是所有WordPress想要做的就是重新安装......不会告诉我那些希望仍然存在的网站。
固定费用多少钱？