- Plesk for Linux
Unable to start mysqld service. In
/var/log/mysqld.log the following error can be found:
CONFIG_TEXT: 32370 [ERROR] InnoDB: Space id in fsp header 1751741216,but in the page header 540740180
32370 [ERROR] InnoDB: innodb-page-size mismatch in tablespace ./phpmyadmin_rq_U9tqAuU26/pma_central_columns.ibd (table phpmyadmin_rq_U9tqAuU26/pma_central_columns)
InnoDB: Error: could not open single-table tablespace file ./phpmyadmin_rq_U9tqAuU26/pma_central_columns.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.
Crush recovery of InnoDB cannot be finished because the table
is corrupted during the recovery process.
- Log in to the server via SSH.
- Move the file to the
# mv /var/lib/mysql/phpmyadmin_rq_U9tqAuU26/pma_central_columns.ibd ~/
- Start the mysqld service (InnoDB recovery process will be executed automatically):
# service mysqld start
If the issue persists, refer to InnoDB corruption cases for the MySQL database in order to proceed with force InnoDB recovery.