PS If the answer is yes, you can disable InnoDB using the skip-innodb directive in the configuration file my.ini (my.cnf for UNIX). The server after editing my.ini will need to reload.
If not try to fix your server any application recovery for MySQL. I would advise to use a proven application and preferably paid. (I know from experience that as a greater chance of recovery) I can recommend you the following application: http://www.mysql.recoverytoolbox.com/
If you do not have the ability or desire to use any software I found for you a link to another forum, which describes a very similar to your problem: http://www.filerepairforum.com/forum/mic...
I hope you will find the solution to your problem.
I use a dedicated server, freebsd
Sometimes (in different ways) mysql can fall in a day, and maybe a month.
and after the fall of the usual inclusion it is not included, is only activated after the removal of the file with the name "ibdata1" in the folder "/ var / db / mysql".
Included not the course and after the team Mysql start.
After turning on the check table, very often some little broken (Do not know what exactly), but what that little problem, I have them and restores all normal, although work without repairing.
May know by anyone causes such falls? MySQL-client version: 5.0.67
