Skip to content
  • About
  • Contact
  • Docs
  • Features
  • Home

Configurations

5
  • Setup RAID Level 6
  • Setup RAID Level 5
  • How To Add Swap on RHEL or Centos based system
  • Website Migration to Non-Panel OpenLiteSpeed Server
  • Linux Server Performance Tuning

CyberPanel

9
  • Mounting /tmp on a Separate File
  • Updating CyberPanel Main VirtualHost Configuration
  • Updating CyberPanel vHosts Configuration
  • How to Change CLI PHP on CyberPanel
  • How to Update PHP Version to 8.1 in CyberPanel (From 7.3, 7.4, or 8.0)
  • CyberPanel Server Cleanup: Logs, Dumps, Backups
  • CyberPanel Full LSPHP Installation PHP 7.4 – 8.3
  • CyberPanel / OpenLiteSpeed: Clean LSPHP Session Files
  • SSL Certificate Management in CyberPanel via SSH

Hestia Control Panel

6
  • Fixing Email Bounce Back Issue in Hestia (Exim4 Blacklist Rejection)
  • Managing Fail2Ban in HestiaCP Server
  • Installing and Configuring PHP Versions in HestiaCP
  • phpMyAdmin Not Found in HestiaCP
  • Setting Up a Reverse Proxy for any Port in HestiaCP
  • How to Install Let’s Encrypt SSL in Hestia CP (Hostname, Admin Panel, and Email Server)

WHM/cPanel

6
  • Setting Up a Reverse Proxy on cPanel/WHM for Port 8081
  • How to increase the size of the cPanel-generated /tmp filesystem
  • Installing Old PHP Versions on a cPanel/WHM Server
  • Fixing “550: Your Country is Not Allowed to Connect to This Server” Error in Exim (cPanel)
  • Enable WP-CLI in CageFS on CloudLinux Servers (WHM/cPanel)
  • Securing /tmp and /var/tmp with a Dedicated Loopback Filesystem

Nagios

5
  • Service Checks
  • Uptime Checks
  • Disk Space Checks
  • Load Checks
  • Email Related Checks

WordPress

3
  • WordPress Core Reinstallation Guide
  • Managing WordPress Users via WP-CLI
  • Website Duplication, Migration, or Domain Change

Operating System

1
  • Server Reboot (RHEL or Centos based system)

AWS

1
  • How to Resize EBS Volumes on AWS

Databases

2
  • MySQL
    • Optimizing MySQL Performance
    • Recovering MySQL in Plesk When InnoDB Crashes

CloudLinux

4
  • Moving cagefs-skeleton directory
  • Enable WP-CLI in CageFS on CloudLinux Servers (WHM/cPanel)
  • Enable bc in CageFS on CloudLinux Servers(WHM/cPanel)
  • How to Upgrade MySQL 5.x to MySQL 8.0 on CloudLinux (WHM server) with MySQL Governor

Cloudflare

1
  • Configuring Security Headers in Cloudflare

ISPmanager

1
  • Install Free SSL (Let’s Encrypt) for domain.tld on ISPmanager with NGINX

Plesk

1
  • Plesk Admin Login Blocked – IP Restriction Recovery Guide

VPN

4
  • Install OpenVPN Open Source in Linux CentOS Ubuntu Debian Servers
  • Protected: OpenVPN Installation & Fix Wiki (CloudLinux / CentOS 7 & 8)
  • Outline VPN Installation & Management Guide
  • Installing AdGuard Home on Debian/Ubuntu (Docker)
View Categories
  • Home
  • Docs
  • Databases
  • MySQL
  • Recovering MySQL in Plesk When InnoDB Crashes

Recovering MySQL in Plesk When InnoDB Crashes

If MySQL encounters critical issues, such as an InnoDB crash, it may fail to start or become unstable. Follow these steps to recover MySQL and restore your databases in a Plesk environment.

Start MySQL in Recovery Mode

To force MySQL to start in recovery mode:

1. Edit the MySQL configuration file (`my.cnf`):

vim /etc/my.cnf

2. Add the following lines to enable recovery mode:

[mysqld]
innodb_force_recovery=1

– The `innodb_force_recovery` value can be set from `1` to `7`. Start with `1` and increase if needed.
– Higher values (`4-6`) make the database read-only and may cause data loss.

3. Restart MySQL:

systemctl restart mysqld

2. Backup MySQL Databases

Once MySQL starts in recovery mode, immediately back up your databases.

1. List available databases:

mysqlshow

2. Dump each database** (replace `[db_name]` with the actual database name):

mysqldump -u root -p [db_name] > [db_name].sql

3. Backup the entire MySQL data directory:

tar -czvf /var/lib/mysql.tar.gz /var/lib/mysql

3. Remove MariaDB and Corrupted Data

1. Find installed MariaDB packages:

rpm -qa | grep -i mariadb

2.Remove MariaDB without affecting dependencies:

rpm -e --nodeps mariadb-server

3. Delete the MySQL data directory (if necessary):

rm -rf /var/lib/mysql

4. Reinstall MariaDB

1. Install MariaDB again:

dnf install mariadb-server

2. Start and enable MariaDB service:

systemctl enable --now mysqld

5. Restore Databases from Backup

1. Create databases (before importing backups):

mysql -u root -p
CREATE DATABASE [db_name];

2. Restore each database:

mysql -u root -p [db_name] < [db_name].sql

3. Restore the MySQL system database (last):

mysql -u root -p mysql < mysql.sql

6. Final Cleanup and Restart

1. Remove `innodb_force_recovery` from `my.cnf`:

vim /etc/my.cnf

– Delete or comment out the `innodb_force_recovery` line.

2. Restart MySQL normally:

systemctl restart mysqld

Important Notes
✅ Always backup databases before making changes.
✅ Higher values of `innodb_force_recovery` can cause data loss.
✅ Removing MariaDB is a last resort—try repairing tables first.
✅ If the MySQL system database (`mysql.sql`) is corrupt, reinstallation may be required.

Following these steps should help recover MySQL in a Plesk environment when it’s in a problematic state. 🚀

Share This Article :

  • Facebook
  • X
  • LinkedIn
  • Pinterest

Was it helpful ?

  • Happy
  • Normal
  • Sad
  • About
  • Contact
  • Docs
  • Features
  • Home

© 2026 Panel Web Hosting

  • About
  • Contact
  • Docs
  • Features
  • Home