📖 ~1 min read
Table of contents
Symptom & Impact
MariaDB fails to start with InnoDB corruption messages.
Environment & Reproduction
Unclean shutdown after power loss or storage error.
Root Cause Analysis
Tablespace pages are inconsistent and recovery aborts.
Quick Triage
Inspect `journalctl -u mariadb` and `/var/log/mariadb/mariadb.log`.
Step-by-Step Diagnosis
Start with `innodb_force_recovery=1..6` in `/etc/my.cnf.d/server.cnf`.

Solution – Primary Fix
Dump all databases with `mysqldump –all-databases > all.sql`.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Reinitialize the data dir and reimport from the dump.
Verification & Acceptance Criteria
MariaDB restarts cleanly and queries succeed.
Rollback Plan
Restore from a known-good backup if dump fails.
Prevention & Hardening
Use point-in-time backups and replicas for resilience.
Related Errors & Cross-Refs
Pairs with disk I/O errors and underlying XFS issues.
Related tutorial: View the step-by-step tutorial for centos-stream-9.
View all centos-stream-9 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
MariaDB InnoDB recovery documentation.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.