MySQL Recovery

When mysqld Refuses to Start, You Still Have the Files on Disk

Server dead after a crash or power cut? Point this Windows tool at your data directory, scan .ibd/.frm/.MYD/.MYI, preview tables, and export clean SQL you can import elsewhere. Trial first.

Download free trialBuy a license
MySQL Recovery — screenshot.

You do not need a running MySQL service. The app reads the on-disk fragments, rebuilds what it can, and hands you an import-ready script—handy after host migrations, bad restores, or half-finished backups.

Built for “we cannot open the database” moments

Typical use: copy the data directory off the broken machine, run the scan on a working Windows PC, inspect previews, then load the SQL into a fresh instance. You stay in control of where files go; nothing is written back into the originals.

How to use it

1

Gather the database files

Copy the folder that holds your .ibd, .frm, .MYD, and .MYI files (or the whole data directory) to a drive with free space. Keep a second copy untouched while you work.

2

Scan and review previews

Add the paths in the app, run the recovery pass, and open the table browser to confirm row counts and sample cells look sane before you export.

3

Export SQL and import cleanly

Save the generated script, create an empty database on a healthy server, import with mysql client or your admin tool, then run your normal integrity checks.

Benefits

Rescue after crashes and bad shutdowns

Power loss, forced kills, and disk hiccups often leave MyISAM tables marked crashed or InnoDB pages inconsistent. A file-level pass can surface data mysqld will not mount.

Download free trialBuy a license

Preview instead of blind restores

Skim tables and cell samples in the UI so you know the salvage is worth importing before you touch production.

Download free trialBuy a license

Keep originals read-only

The tool is meant to read your damaged files and write results elsewhere—your source folder stays unchanged while you iterate.

Download free trialBuy a license

Why people use it

Works without a live server

If the service will not start or the instance is gone, you can still work from cold storage as long as the files are readable.

InnoDB and MyISAM in one workflow

Mixed deployments are common; you do not need separate one-off utilities for each engine when both show up in the same backup tree.

Edit before you commit

The output is plain SQL. Trim bad rows, split large dumps, or tweak DDL in a text editor if your DBA wants a manual pass.

Common MySQL corruption error codes

Error codeOfficial MySQL message templatePrimary cause
1016Can't open file: '[table_name].MYI' (errno: 2)Missing or physically damaged database or table files on disk.
1030Got error [X] from storage engineGeneric wrapper for internal InnoDB or MyISAM failures.
1033Incorrect information in file: './[db]/[table].frm'Corrupted table definition or a damaged .frm metadata file.
1064You have an error in your SQL syntax near '...'Sometimes metadata damage surfaces as bogus syntax when the server misreads structures.
1146Table '[db].[table]' doesn't existMissing .frm files or a mismatch between the data dictionary and files on disk.
1194Table '[table]' is marked as crashed and should be repairedSevere MyISAM corruption, often after a write interrupted mid-flight.
1412Table definition has changed, please retry transaction.frm file out of sync with the InnoDB data dictionary.
145Table '...' was not closed properly; it is marked as crashedUnclean shutdown or kill while the table was open.
126Index file is crashed; try to repair it.MYI index corruption; the engine cannot map rows reliably.
2013Lost connection to MySQL server during queryServer-side crash (for example segfault) while reading damaged pages.
Log onlyInnoDB: Checksum mismatch in page [X]Bit rot, bad sectors, or hardware errors making pages unreadable.

FAQ

Usually yes. The app targets the raw files. Copy the tree to a Windows box with enough free space, point the scanner at it, and work from previews. Keep an untouched duplicate until you are happy with the export.
MySQL from legacy 5.x builds through current 8.x/9.x lines, plus MariaDB 10.x/11.x-style layouts we see in the field. InnoDB and MyISAM are both in scope; mixed folders are normal.
REPAIR needs a cooperative server and intact enough files to open the table. When mysqld dies mid-repair or will not boot, file-level recovery is the next step. Treat this as a deeper pass over bytes, not a SQL-only fix.
The export aims to rebuild structure and data together—keys, types, views, and triggers when the fragments allow. Severely truncated files may yield partial tables; the preview shows what survived before you commit disk space to a full dump.
No. Open files read-only, emit SQL to a path you choose. If something looks wrong, delete the export and rescan with different options without touching the source media.
Runtime scales with total file size and fragmentation. Small instances finish quickly; multi-hundred-gigabyte trees need patience and fast disks. Use the trial to time a representative folder before you plan a maintenance window.
You can run full scans and inspect previews. Paid activation removes export limits (such as row caps per table in the demo). If previews are empty, buying will not magically invent data—send a sample set to support if you are unsure.

System Requirements

MySQL Recovery

Languages

Version

1.5

File Size

6.1 Mb

Last updated on

February 22, 2026

Buy now
$39.99Download
  • Windows 11/10/8.1/8/7 (32/64 bit)
  • Intel i3, AMD Ryzen 5 or above
  • 4 GB of RAM or above
  • NVIDIA® GeForce® series 8 and 8M, Intel® HD Graphics 2000, Quadro FX 4800, Quadro FX 5600, AMD Radeon™ R600, Mobility Radeon™ HD 4330, Mobility FirePro™ series, Radeon™ R5 M230 or higher graphics card with up-to-date drivers
  • 1280 × 768 screen resolution, 32-bit color
  • 1 GB of free hard disk space or above

GRT requirements trial note