mysql突然啟動不起來了
mysql.ini配置也沒發(fā)生更改過咬荷，替換初始的mysql.ini文件后也報(bào)一樣的錯冠句。3306端口也沒被占用。
2018-01-02 13:46:35 7fffaa5a6340 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 ./ridu/rd_indexpage.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.
方法1（推薦使用）
刪除data目錄下的ib_logfile0和ib_logfile1文件幸乒，如果是xampp的的話路徑在/Applications/XAMPP/xamppfiles/var/mysql下懦底，親測好用
方法2
如果上面方法1不好使的話，就只能在配置文件里加這個innodb_force_recovery=4強(qiáng)制啟動
然后盡快導(dǎo)出能導(dǎo)出的數(shù)據(jù)
