Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

innodb_force_recovery is an emergency startup and data-extraction switch, not an InnoDB repair command. Set it only after normal crash recovery and a verified backup path have failed or are unavailable. Start at level 1 on a separate copy of the data directory, increase one level at a time only when startup still fails, and use the resulting read-only session to dump whatever data remains readable. Then remove the setting, rebuild a clean MySQL instance, and validate the restored data before production use.

Levels 4 through 6 can permanently damage InnoDB files. Never experiment with those values on the only copy of a production data directory. If an uncorrupted backup and binary logs exist, restoring the backup and applying the logs is the safer, consistency-preserving recovery method.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What innodb_force_recovery does

During a normal restart, InnoDB performs crash recovery: it scans redo information, rolls back incomplete transactions, merges change-buffer entries, purges old versions, and starts background threads. A damaged page, broken undo record, failed disk, or runaway rollback can prevent that process from completing.

innodb_force_recovery suppresses selected recovery and background operations so the server may start long enough for you to read and export data. A value greater than zero disables normal writes. The option does not repair pages, reconstruct missing records, or make an inconsistent transaction state safe for continued application use.

#1 Best Overall
Sale
Compressed Air Duster,130000RPM Super Power Cordless Air Duster,Rechargeable Brushless Blower,3 Gear Adjustable Blower with LED Light,Dust Remover for Computer/House/Outdoor/Car
  • Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
  • With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
  • Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
  • Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
  • Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.

The intended endpoint is a logical dump followed by a rebuild or restore into a clean instance. Treat the original files as evidence to preserve, not as a server you plan to return to service.

Choose the safest recovery route first

Forced recovery is a salvage path. Before using it, determine whether ordinary crash recovery or backup-based recovery can solve the incident without exposing the data files to additional risk.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Option Transaction consistency Risk to original files Potential data recovered Binary logs required Can the original instance return to service?
Normal restart and InnoDB crash recovery Preserves InnoDB’s designed recovery process when storage is intact Normal operational risk Usually the complete database if the failure was transient No Yes, after root cause and integrity checks are resolved
Backup restore plus point-in-time recovery Best available consistency when the base backup is valid and logs are complete Operate on a restored copy; original files remain untouched Backup contents plus transactions represented in binary logs Yes, for changes after the backup No; use the restored instance instead
innodb_force_recovery and logical dump May be incomplete or inconsistent, especially at levels 3, 5, and 6 Levels 4 and higher can permanently corrupt data files Only rows, pages, and tables that can still be read No, but logs may be needed to fill gaps No; rebuild from the dump and retire the affected files

MySQL’s recovery guidance says that confirmed corruption or disk failure should be recovered from an uncorrupted backup, followed by binary-log application with mysqlbinlog and mysql. Use forced recovery when no usable clean path exists, when a backup is too old and you need additional salvage, or when you must extract data before rebuilding.

Preserve the evidence before changing anything

  1. Stop application writes. Remove the server from the application’s pool, stop replication jobs that write to it, and prevent automated restart loops. Record the time of the failure.
  2. Capture diagnostic state. Save the MySQL error log, the exact MySQL version, operating-system and storage details, configured data directory, enabled storage engines, disk-space status, and the output of any failed restart. Preserve the original timestamps.
  3. Inventory recovery materials. Locate the newest full or physical backup, incremental backups, binary logs, backup verification reports, and documented encryption keys or credentials. Do not assume that a file named “backup” is restorable until it has been tested.
  4. Make a filesystem-level copy or snapshot. Stop MySQL cleanly if it is still running, or use a storage snapshot designed for a stopped or crash-consistent database. Copy the entire data directory, including InnoDB system files, redo logs, undo files, table files, and metadata. Keep the original read-only and work on the copy.
  5. Record the copy’s identity. Note its location, creation time, storage checksum process, and who is authorized to modify it. Make additional copies before attempting levels 4, 5, or 6.

MySQL explicitly limits nonzero forced-recovery values to emergency situations where the goal is to start InnoDB and dump tables. Values of 4 or greater can permanently corrupt data files, so testing those levels on a separate copy is mandatory.

Understand every recovery level

Higher values include the behavior of lower values. Increase only one step at a time, and stop as soon as the server starts and you can extract the data you need.

Level Internal behavior When it is useful Risk and limitations
0 Normal InnoDB startup and recovery Use after the underlying problem is resolved or on a clean rebuilt instance Normal behavior; it is not forced recovery
1 (SRV_FORCE_IGNORE_CORRUPT) Allows startup despite detected corrupt pages and attempts to skip corrupt index records or pages during reads First emergency attempt and the preferred starting point for dumping Some rows or pages may remain unreadable
2 (SRV_FORCE_NO_BACKGROUND) Stops the InnoDB master and purge threads When background cleanup or purge activity causes the server to exit Background cleanup is disabled; do not treat the instance as healthy
3 (SRV_FORCE_NO_TRX_UNDO) Skips transaction rollback after crash recovery When startup is blocked by runaway or damaged undo processing Incomplete transactions can remain unresolved, so logical consistency is uncertain
4 (SRV_FORCE_NO_IBUF_MERGE) Disables insert-buffer merges and statistics calculation; the server is read-only Last-resort extraction after testing on a disposable copy Can permanently corrupt data files; secondary indexes may need rebuilding
5 (SRV_FORCE_NO_UNDO_LOG_SCAN) Skips the undo-log scan and treats incomplete transactions as committed; the server is read-only Extreme extraction only when lower values cannot start the copy Can permanently corrupt files and transaction consistency
6 (SRV_FORCE_NO_LOG_REDO) Skips redo roll-forward; the server is read-only Drastic final extraction attempt on a preserved copy Pages can be obsolete, and additional B-tree or structural corruption may result

Levels 1 through 3 are still emergency modes. Although the most explicit permanent-corruption warning applies to 4 and above, none of the nonzero levels is suitable for normal application traffic.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Step-by-step recovery procedure

1. Isolate the server and prepare a working copy

Stop normal traffic and complete the preservation steps before editing configuration. If the host is managed by a service supervisor, disable automatic restart temporarily so repeated failed starts do not alter logs or files. Keep the original data directory offline. Perform every subsequent start against the filesystem copy or storage snapshot.

Rank #2
EVEO® Screen Cleaner Spray Kit (Streak-Free) TV Screen Cleaner for Smart TV, Lcd, LEd, Oled | Computer Screen Cleaner Spray and Wipe Microfiber Cloth - TV, Monitor, Laptop, iPad, Car - 6.7oz 1 Pack
  • Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
  • Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
  • Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
  • Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
  • Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth

2. Set level 1 in the MySQL option file

Edit the option file used by the server and add the setting under the [mysqld] section:

[mysqld]
innodb_force_recovery = 1

Do not add the option only to a client section, and do not assume that changing a command-line client option changes the server. Confirm which option file and data directory the service actually uses.

3. Restart once and read the error log

Start the copied instance and inspect the error log immediately. A successful start is not proof that the database is sound; it only means that this level suppressed enough work to let InnoDB open. Look for messages identifying corrupt tables, pages, indexes, undo records, redo processing, or tables that fail during dictionary initialization.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

If startup still fails, stop the copied instance, change the value to 2, and repeat. Continue through level 3 only when necessary. Never jump directly to 6 simply because a lower level has not yet been tried.

4. Confirm that the instance is read-only for recovery purposes

Any value greater than zero blocks writes. Levels 4 through 6 are explicitly read-only. Do not run application migrations, ALTER TABLE, repairs, deletes, updates, or maintenance jobs. Disable scheduled tasks that could connect and issue writes. Use the server only for simple reads and extraction.

5. Dump databases and tables as soon as they are readable

Begin with the smallest useful logical export. A whole-server attempt can stop at the first damaged table, so save independent files for databases and, when necessary, individual tables.

mysqldump -u root -p --all-databases --routines --events --triggers > salvage.sql
mysqldump -u root -p --databases appdb > appdb.sql
mysqldump -u root -p appdb readable_table > readable_table.sql

Use an administrative account with permission to read the objects and to include required routines, events, and triggers. The commands above are examples; choose an account and database names that match the affected instance. Check the dump process exit status and inspect the resulting files. A file that was created successfully can still be incomplete if mysqldump reported errors.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Rank #3
Sale
BladeHawks RGB Gaming Mouse Pad Extra Large Extended 31.5x12 Inch-Black | LED mouse pad with 14 lighting modes, covers keyboard & mouse, anti-slip rubber base, waterproof surface, USB powered
  • 【Large size】:Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
  • 【LED backlight mouse pad】:Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
  • 【Anti-slip rubber base】:Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
  • 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
  • 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.

SELECT ... INTO OUTFILE is another extraction method when the server account has the required file privilege and the destination is writable by the server process. Write exports to storage outside the damaged data directory. Do not overwrite an earlier dump; retain each attempt with its recovery level and timestamp.

6. Isolate failures when a table-wide read stops

Try each table separately so one damaged object does not prevent salvage of the rest. If a table-wide scan fails, identify its primary key and read bounded ranges in smaller batches. Record the ranges that succeed and those that fail.

The MySQL manual notes that ORDER BY primary_key DESC may retrieve rows located after a corrupted region. This is a retrieval tactic, not a repair: verify the returned key ranges and expect gaps. At high recovery levels, only basic statements such as SELECT * FROM table_name may work; avoid assuming that joins, sorting, secondary-index access, or aggregate queries can safely traverse damaged structures.

For each table, preserve the schema definition separately from row data where possible. Save primary keys, unique keys, foreign keys, generated columns, triggers, and character-set settings so the clean rebuild can reproduce the intended structure even when some rows are missing.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

7. Escalate to levels 4 through 6 only on a disposable copy

If levels 1 through 3 cannot start the copied instance, create another copy or snapshot before trying level 4. Set the next value, restart, and inspect the log. Repeat one level at a time. At these levels, prioritize extraction speed over continued operation: dump every readable table immediately and preserve the output in separate storage.

Level 5 can treat incomplete transactions as committed, and level 6 skips redo roll-forward. Data extracted at either level must be treated as potentially inconsistent. Never promote that instance, its files, or its tablespaces to production.

8. Remove forced recovery after extraction

When the dump work is complete, stop the emergency instance and remove or comment out innodb_force_recovery from the option file. Do not simply set it to 0 and continue using the damaged data directory. Build or provision a clean MySQL instance with a supported configuration, recreate the schemas, and load the logical dump there.

Rank #4
Sale
Vaydeer Wrist Rest for Keyboard and Mouse, Computer Ergonomic Wrist Support Pad, Soft Memory Foam Arm Cushion for Desk, Palm Hand Office Laptop Typing
  • 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
  • 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
  • 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
  • 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
  • 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
mysql -u root -p < salvage.sql

Load database-by-database or table-by-table when the dump is partial. Resolve schema dependencies deliberately: create parent tables before child tables, then restore foreign keys and triggers after the row data has been loaded if necessary. Keep the damaged source disconnected until validation is complete.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Use backups and binary logs when they exist

A valid base backup is normally safer than trying to make a severely damaged instance readable. Restore the backup to separate hardware or storage, verify that it starts cleanly, and apply binary-log events generated after the backup with mysqlbinlog and mysql. Point-in-time recovery can reduce data loss while preserving transaction ordering better than a forced dump.

If the forced dump contains gaps, compare its tables and key ranges with the restored backup. Use the backup for missing objects whenever possible, then apply binary logs to bring the replacement forward. Do not merge files from a damaged data directory into a clean instance by hand; recover through logical export, supported backup tooling, or documented tablespace procedures appropriate to the exact failure.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

When redo recovery runs out of space

Some failures occur while InnoDB is trying to process redo information and cannot obtain enough space. MySQL troubleshooting guidance documents trying a forced-recovery restart beginning with SRV_FORCE_NO_IBUF_MERGE (level 4) and, if that does not work, SRV_FORCE_NO_LOG_REDO (level 6). Because both values can permanently damage files, apply this sequence only to a preserved copy and only when lower levels and a clean backup path have failed.

If the copied instance still cannot start at the documented emergency levels, stop escalating. Preserve the logs and files and recover from a valid backup, storage snapshot, or specialist incident response process rather than repeatedly starting the original directory.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Validate the rebuilt database before production

A successful dump and import establish only that some SQL could be read and loaded. Validation must show that the replacement contains the data and relationships the application expects.

  • Compare database, table, and row counts with the last known-good inventory and with backup records.
  • Compare minimum and maximum primary-key values and inspect for gaps in every table dumped in ranges.
  • Check duplicate and missing values for primary keys and unique keys.
  • Validate foreign-key relationships and application-level invariants, such as one order belonging to an existing customer or each ledger entry balancing according to the application’s rules.
  • Verify indexes, constraints, generated columns, triggers, routines, events, collations, and character sets.
  • Run representative read queries, reports, and critical application workflows against the replacement.
  • Review the import log for warnings, truncated values, rejected rows, disabled constraints, and tables that were skipped.
  • Create a new full backup of the clean instance, test restoring it, and document the recovery steps while the incident details are fresh.

Do not claim a universal recovery percentage or completion time. Results depend on which pages are damaged, the transaction state at failure, the quality of backups, and the binary logs available.

Best Value
Sale
Under Desk Cable Management Tray No Drill, Metal Mesh Cable Management Under Desk with Clamp Mount, 2 Hole Cable Tray with Wire Management and Cord Organizer for Home Office Standing Desk
  • 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
  • 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
  • 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
  • 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
  • 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.

Common mistakes and their consequences

Using the only production copy

Levels 4 and above may alter files irreversibly. Working on the only copy can turn a potentially recoverable incident into permanent loss. Always snapshot or copy first and preserve the original.

Starting at level 6

A high value suppresses more recovery work and can leave obsolete pages or unresolved transactions. Begin at 1 and increase one step at a time so you know the lowest level that permits extraction.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Assuming startup means repair

The server starting proves only that suppressed operations no longer block initialization. It does not prove that every table, index, transaction, or row is intact. Dump and rebuild instead of resuming application traffic.

Running writes during forced recovery

Nonzero values are emergency read modes. Application writes, schema changes, and maintenance tasks can fail or make the situation harder to interpret. Isolate the server and stop automated jobs.

Trusting one successful dump file

A whole-database dump can contain errors after a damaged table, and a partial table scan can hide missing key ranges. Check command exit status, error output, table coverage, and row/key ranges; retain separate exports for independently recovered objects.

Deleting the original files after import

Keep the original data directory and all logs until the replacement has passed application validation and at least one tested backup restore. The files may be needed to recover a missing range or explain an inconsistency.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Practical decision checklist

  • Can the server start normally? Resolve the underlying storage or configuration problem and use normal InnoDB recovery; do not enable forced recovery unnecessarily.
  • Is there a verified, uncorrupted backup? Prefer restore plus binary-log point-in-time recovery.
  • Is only extraction possible? Copy the data directory, start at level 1, and dump immediately.
  • Does startup fail? Increase one level at a time, documenting the error log after every restart.
  • Do levels 4–6 become necessary? Work from a new copy, expect permanent file damage, and treat all output as potentially inconsistent.
  • Is the dump complete? Reconcile tables, rows, primary-key ranges, constraints, and application checks before cutover.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.