MySQL Fails to Start with InnoDB Corruption

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

MySQL service fails at startup, causing application outage and potential data unavailability.

Environment & Reproduction

Ubuntu 20.04 database hosts after abrupt power loss, storage faults, or filesystem corruption events.

Root Cause Analysis

InnoDB pages/logs are inconsistent, preventing normal crash recovery during engine initialization.

Quick Triage

Protect data directory, collect error logs, and stop repeated restart attempts.

Step-by-Step Diagnosis

Determine corruption scope, storage health, and recoverability from backups/binlogs.

Solution – Primary Fix

Use controlled recovery mode, export data safely, rebuild tablespace, and restore verified backups.

Solution – Alternative Approaches

Promote replica, perform point-in-time recovery, or migrate workload to standby instance.

Verification & Acceptance Criteria

Service starts cleanly, integrity checks pass, and application transactions complete successfully.

Rollback Plan

Revert to replica or backup snapshot if repaired instance fails validation tests.

Prevention & Hardening

Implement backup verification, storage monitoring, and graceful shutdown controls.

Related Errors & Cross-Refs

`InnoDB: corruption`, redo log parse failures, and crash recovery loops.

Related tutorial: View the step-by-step tutorial for Ubuntu 20.04 LTS.

View all Ubuntu 20.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

MySQL InnoDB recovery procedures and Ubuntu database operations best practices.