• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Resolved mariadb corruption

jan1001

New Pleskian
Hello, overnight mariadb crashed and can not startet, because "Database page corruption on disk or a failed
InnoDB: file read of page 5102." How can I repair the system? I dont know how to find that corrupted file.
It seems I have to delete the database files to get mariadb started, but that means the plesk database is also deleted. (I have the files from the daily plesk backup.)
What can I do now?
 
Hi UFHH01, I solved the problem already. I found a InnoDB Crash Recovery Guide mixed with my knowledge about Plesk I deleted all Databases und restore them from a database dump. At moment I look for crash reason, it seems some Plesk Autoupdate Updates was the problem.
 
Back
Top