Repair WordPress Database Tables

The Problem

WordPress or phpMyAdmin shows a table is "marked as crashed" or you're seeing database errors that don't match a simple connection problem — one or more actual database tables have become corrupted, often after an improper server shutdown or a failed import.

About this problem

Table corruption is different from a connection error — the database server is reachable and working, but a specific table's data or index has become internally inconsistent, usually after an abrupt server restart during a write operation, a disk-level fault, or an interrupted import/restore. MySQL/MariaDB can often repair this automatically with the right command, but running it against the wrong table or without a backup first carries real risk if the corruption is more serious than a simple index issue.

Symptoms range from specific pages failing to load, to WordPress's own database error messages naming a table directly.

What's Included

• Identifying exactly which table(s) are corrupted and how serious the damage is
• Taking a backup before attempting any repair, given the small risk involved
• Running the appropriate repair process for the storage engine in use
• Verifying the site functions normally afterwards and spot-checking the affected content

What's NOT Included

• Recovering data that's unrecoverable due to severe corruption beyond what repair tools can fix (rare, but possible — you'd be told immediately if found)
• Diagnosing the original hardware or hosting fault that caused the corruption in the first place
• Ongoing database integrity monitoring (can be set up separately if this keeps recurring)

How It Works

1. Identify the specific corrupted table(s) from the error message or a CHECK TABLE scan across the database.
2. Take a full database backup before attempting any repair, given corruption repair isn't always fully reversible.
3. Run REPAIR TABLE (or the appropriate engine-specific recovery process for InnoDB) on the affected table(s).
4. Re-check the table(s) to confirm the repair actually resolved the corruption rather than just suppressing the error.
5. Spot-check the content and functionality that depends on the repaired table to confirm everything displays correctly.

In practice: you buy the service, send over whatever access or details the job needs, I investigate and do the work, and you confirm it's resolved before we call it done.

Frequently Asked Questions

What does "table is marked as crashed" mean in WordPress?

It means a specific MySQL/MariaDB table has become internally corrupted, usually due to an abrupt server restart or disk issue during a write, and needs a repair operation rather than a simple settings fix.

Is repairing a database table risky?

There's a small risk with severe corruption, which is why a full backup is taken first — for the vast majority of cases the standard repair process resolves it cleanly with no data loss.

Will repairing my database delete any content?

No, the goal is to restore the table to a consistent, readable state — content isn't deliberately removed, though in rare cases of severe corruption some data in the specific damaged rows may not be recoverable.

What causes WordPress database tables to become corrupted?

The most common causes are a server crashing or restarting mid-write, a failed or interrupted database import, or in rarer cases underlying disk hardware issues.

How is this different from a general database cleanup?

Cleanup removes unnecessary bloat (old revisions, spam, expired transients) from otherwise healthy tables; repair fixes tables that have become structurally damaged and are causing actual errors.