Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

recently my PC powered off abruptly for no apparent reason, leaving my Windows 7 installation severly damaged. I can still log onto the machine, but tons of Windows system files have been corrupted and I have no other choice than performing a repair install of Windows.

At the same time, my MySQL 5.5.31 instance running on this system has been damaged. I am not sure if it's just the MySQL installation that got damaged, or the data itself. What I can say is that while the serve was certainly running during the shutdown, it did not perform any tasks at that time.

What happens now is that when I try to run mysqldump from MySQL Workbench, it aborts after a couple of tables saying that it has lost the connection to the server.

Most tables are InnoDB, a few MyISAM.

How can I repair the installation and recover my data? Should I uninstall and re-install?

Appreciate your help.

EDIT: These are the two errors I get from the error event log in MySQL Workbench: "InnoDB: Page checksum 3072680322, prior-to-4.0.14-form checksum 1925954319 InnoDB: stored checksum 24388168, prior-to-4.0.14-form stored checksum 1077079361 InnoDB: Page lsn 3225980244 611338381, low 4 bytes of lsn at page end 2304517124 InnoDB: Page number (if stored to page already) 2370756659, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 4293596229"

"InnoDB: Assertion failure in thread 3988 in file page0page.ic line 745 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: InnoDB: about forcing recovery."

share|improve this question

migrated from May 6 '13 at 12:54

This question came from our site for professional and enthusiast programmers.

How big is the dump file going to be? How long has it run before timing out? MySQL workbench has a DBMS keep alive time interval of 600 seconds by default. – apesa May 5 '13 at 14:02
I think the total dump file size would be around 10 GB (in fact I always dump each table individually rather than having one big file). It runs about 30 seconds before timing out, in any case far earlier than 600s (=10 minutes). – Steve06 May 5 '13 at 14:11
You have no errors in MySQL Workbench? If not I might reinstall MySQL at the same version level first and then try to execute a dumpfile as you have before. In Windows I think you should just be able to rerun Install and have it take you to a Install / Remove / Repair option. – apesa May 5 '13 at 15:09
I have added the two errors from the error event log inMySQL Workbench above. – Steve06 May 6 '13 at 3:22
Based on your error you do not have a connection problem, you have a corruption problem. You should follow the innodb_force_recovery option. Look here – apesa May 6 '13 at 13:48

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.