Issue Maria DB 10.11 > 11.4 upgrade results in issues with Plesk Repair Tool - reports innodb corruption in ibdata1

[Sebahat.hadzhi]

@opus68 , it's an upstream bug in MariaDB. It hasn't been fixed yet. I cannot provide an ETA at this point, as the fix depends on MariaDB rather than Plesk.

@Megaboss , have you checked if the MariaDB service is active?

 

[Megaboss]

Yes it is.

It was Plesk repair tool that killed my database...
Spent the hole weekend building up my server again.

 

[webart]

I can confirm the issue still exists on Plesk Obsidian 18.0.76 Update #2.

Fresh installation, MariaDB 10.x > MariaDB 11.8.6 Upgrade results in issues with Plesk Repair Tool - reports InnoDB corruption in ibdata1.

However, I can also confirm that after clicking on the restart service button, MariaDB service is becomes active, can't see any damaged databases.

 

[RC-Devil]

It was Plesk repair tool that killed my database...

I can confirm this; I have the same problem. The Plesk Repair Tool killed my database. Now I have to rebuild the entire server, including all client websites. That's going to be fun, rebuilding almost 500 GB of websites.

 

[Sebahat.hadzhi]

@Megaboss @RC-Devil if you can open a ticket with Plesk support for further investigation on your server, please do. I am unable to replicate the issue on a test environment, so the root cause might be somewhere else.

 

[RC-Devil]

@Sebahat.hadzhi After the bug corrupted all databases, internal systems were also affected, as their databases were also damaged. This led to errors in the mail servers, Fail2Ban, and several other system areas. Rather than spend ages trying to fix everything, I opted for a clean install and restoration of all 30 websites from a backup. This only took me a weekend; a repair would have taken much longer.
Apparently, the days of bug-free updates are over.

 

[tethis IT]

I just stumbled into the same issue, updating MariaDB from 10.x to 11.8.6 worked just fine, but the Plesk Repair Kit reports:

[2026-03-28 19:51:33+01:00] ERROR: InnoDB tablespace file '/var/lib/mysql/ibdata1' is corrupted. The database has been stopped to prevent further damage. To avoid data loss, restore the database from a backup before attempting to start it again.
[2026-03-28 19:51:37+01:00] INFO: Repair of InnoDB corruption will require at least 2.7G of free disk space on / mount point. Currently 82G of disk space is available on it.

Luckily I did read this thread before initiating the repair, so the server and all websites on it are still running fine.
In other words, I did not run the repair yet.
The update process suggested in the Plesk backend (Tools and Settings / Database Server => Update to 11.8) didn't work, because the mariadb website changed their download URLs. But following the process described in Question - MariaDB upgrade via Plesk fails worked fine.
This machine is to some extend a test system, so @Sebahat.hadzhi , if you want to take a look and try to replicate something, let me know.

Kind regards,
Christian
tethis IT

 

[Azurel]

Is this issue fixed? Its look like you must first upgrade to minimum 10.11.15 (there is MDEV-37138 fixed) and than upgrade to 11.8? Have anybody successful upgraded to 11.8 from 10.11.16?