MAMP MySQL在突然關機後未啓動; InnoDB錯誤

Question

當我在通過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想要做的就是重新安裝...不會讓我看到希望仍然存在的網站。

需要多少費用才能修復？

Answer 1

最近有類似的問題 - 在這裏發佈解決方案 - 希望它有幫助。

https://stackoverflow.com/a/42741757/3407817