How to fix InnoDB corruption cases for the MySQL databases on Plesk for Windows?

Connect to the server via RDP

Create a backup of all current Plesk-related MySQL data and databases at %plesk_dir%MySQL\Data\.

Open the %plesk_dir%MySQL\my.ini file.

Add the following lines into the [PleskSQLServer] section:

CONFIG_TEXT: innodb_force_recovery = 1
skip-grant-tables

Try to start PleskSQLserver.

In case it fails once again, set innodb_force_recovery to a greater value and try starting it again.

Warning: Only set innodb_force_recovery to a value greater than 0 in an emergency situation, so that you can start InnoDB and dump your tables. Values of 4 or greater can permanently corrupt data files. Therefore, increase this value incrementally, as necessary. Please see more details in the official MySQL Documentation.

Once PleskSQLserver is started in force recovery mode, create dumps of all databases using the following command executed via the PowerShell:

PS cd $env:plesk_dir\mysql\bin\
mkdir .\data_restore
.\mysql.exe -uadmin -P8306 -e"SHOW DATABASES" > c:\db_list.txt
foreach ($var in get-content c:\db_list.txt) {.\mysqldump.exe -uadmin -P8306 $var > .\data_restore\$var.sql}

Stop PleskSQLserver service.

Remove all MySQL data except mysql folder and error logs from %plesk_dir%MySQL\Data\ directory.

Remove the line innodb_force_recovery from my.ini file and start PleskSQLserver.

Restore the databases from the dumps made during the step 7:

PS foreach ($var in get-content c:\db_list.txt) {.\mysql.exe -uadmin -P8306 -e"create database $var"}
foreach ($var in get-content c:\db_list.txt) {get-content .\data_restore\$var.sql | .\mysql.exe -uadmin -P8306 $var}

Remove the skip-grant-tables line from my.ini file and restart PleskSQLserver .

Connect to the server via RDP

Create a backup of all current MySQL data and databases at %plesk_dir%Databases\MySQL\data

Open the %plesk_dir%Databases\MySQL\my.ini file.

Add the following line into the [MySQLD] section:

CONFIG_TEXT: innodb_force_recovery = 1
skip-grant-tables

Try to start MySQL.

In case it fails once again, set innodb_force_recovery to a greater value and try starting it again.

Warning: Only set innodb_force_recovery to a value greater than 0 in an emergency situation, so that you can start InnoDB and dump your tables. Values of 4 or greater can permanently corrupt data files. Therefore, increase this value incrementally, as necessary. Please see more details in the Official MySQL Documentation.

Once MySQL is started in force recovery mode, create dumps of all databases using the following command executed via the PowerShell:

PS cd $env:plesk_dir\mysql\bin\
mkdir .\data_restore
.\mysql.exe -uadmin -P3306 -e"SHOW DATABASES" > c:\db_list.txt
foreach ($var in get-content c:\db_list.txt) {.\mysqldump.exe -uadmin -P3306 $var > .\data_restore\$var.sql}

Stop MySQL service.

Remove all MySQL data except mysql folder and error logs from %plesk_dir%Databases\MySQL\data directory.

Remove the line innodb_force_recovery from my.ini file and start MySQL.

Restore the databases from the dumps made during the step 7:

PS foreach ($var in get-content c:\db_list.txt) {.\mysql.exe -uadmin -P3306 -e"create database $var" }
foreach ($var in get-content c:\db_list.txt) {get-content .\data_restore\$var.sql | .\mysql.exe -uadmin -P3306 $var}

Remove the skip-grant-tables line from my.ini file and restart MySQL.