Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

so my Mysql server has been working just fine, but suddenly out of the blue now whenever I try to load it up it returns this error:

110827 18:42:06 [Note] Plugin 'FEDERATED' is disabled.
110827 18:42:06  InnoDB: Started; log sequence number 0 42897533
110827 18:42:06 [Note] Recovering after a crash using mysql-bin
110827 18:42:06 [Note] Starting crash recovery...
110827 18:42:06 [Note] Crash recovery finished.
110827 18:42:06 [Note] Event Scheduler: Loaded 0 events
110827 18:42:06 [Note] wampmysqld: ready for connections.
Version: '5.1.36-community-log'  socket: ''  port: 3306  MySQL Community Server (GPL)
110827 18:42:15  InnoDB: Operating system error number 995 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
InnoDB: File name .\ibdata1
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.

anyone knows why this is happening and how to fix it? I'm using wampserver 2.0

share|improve this question

closed as off-topic by Tom O'Connor Aug 14 '13 at 21:04

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions must be relevant to professional system administration. Server Fault is a site dedicated to professionals; novice questions are off-topic. Please see the Help Center for more information on topicality. The best advice we can give you is to hire a professional to help you out." – Tom O'Connor
If this question can be reworded to fit the rules in the help center, please edit the question.

Following the links provided in your question, I get to http://msdn.microsoft.com/en-us/library/ms681388.aspx, which describes Error 995 as:

The I/O operation has been aborted because of either a thread exit or an application request.

That sounds vaguely like MySQL actually asked to abort the operation, or else a thread died unceremoniously.

share|improve this answer

Here is an old MySQL bug report on error 995 in which a couple things are suggested:

  • Tune innodb_file_io_threads: "Number of file i/o threads in InnoDB. Normally, this should be 4, but on Windows disk i/o may benefit from a larger number. Numeric my.cnf parameter format. "
  • Depending on what version of MySQL you're running, a fix was put into 5.1.42. See if you can upgrade to that version if you're not running it.
  • Potentially an OS bug/failure. Try running the DB on a different machine.
share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.