Ubuntu 16.04 LTS MySQL service fails after abrupt disk full event

📖 ~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

Database service does not start, causing application outage and failed transactions.

Environment & Reproduction

Occurs when data volume or logs reach full capacity unexpectedly.

Root Cause Analysis

InnoDB cannot complete checkpoint or log writes due to no available disk space.

Quick Triage

Free emergency disk space and capture MySQL startup diagnostics immediately.

Step-by-Step Diagnosis

Review MySQL error log for table corruption, redo log issues, and permission state.

Solution – Primary Fix

Recover disk headroom, run safe startup recovery mode, and normalize storage layout.

Solution – Alternative Approaches

Restore from backup replica or promote standby if primary recovery exceeds RTO.

Verification & Acceptance Criteria

MySQL starts cleanly, replication and application checks pass, and logs stay healthy.

Rollback Plan

Fail back to restored snapshot if data consistency checks fail after restart.

Prevention & Hardening

Enforce volume alerts, log rotation, and growth forecasting for database hosts.

Related Errors & Cross-Refs

InnoDB: error writing file, table is marked as crashed, and cannot allocate memory.

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

View all Ubuntu 16.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

MySQL crash recovery and disk capacity planning on Ubuntu 16.04.