InnoDB: Operating system error number 87 in a file operation error

[mastermind]

Posting this in case anyone else runs into this head scracher.

@admins I was not sure which forum to post this in so if this is the wrong place please move.

Ran in to this error when I attempted to launch the MySQL server (MySQL.bat) in the _Server folder.
Long story short it is a know issue with MySQL 5 pertaining to the drive storage type.

I want to use a small mini PC as a blank slate for testing SQL patches in a pure, freshly downloaded repack.
This is the one I am using.
Nexbox T9
Intel 64-bit Cherry-Trail x5-Z8300 @ 1.84GHz Turbo
Intel HD Graphics
4GB DDR3 RAM
64GB eMMC with expandable MicroSD card storage
1 USB 3.0 port, 3 USB 2.0 ports, 1 USB OTG
RJ45 Ethernet
HDMI Port
2.4GHz WiFi with 802.11b/g/n support
Bluetooth 4.0
3.5mm Headphone/Microphone combo jack

When you run the MySQL.bat you are greeted with the following.

_____________________Emucoach 4.3.4 Blizzlike Repack______________________
___________________________http://emucoach.com____________________________
______________________________MySQL 5.5.9_________________________________

MySQL is currently running. Please only close this window for shutdown.
Please disregard any InoDB messages that are prompted. They have no use.
After your server is shut off, press CTRL C to shut down this service.
170626 20:12:23 [Note] Plugin 'FEDERATED' is disabled.
170626 20:12:23 InnoDB: The InnoDB memory heap is disabled
170626 20:12:23 InnoDB: Mutexes and rw_locks use Windows interlocked functions
170626 20:12:23 InnoDB: Compressed tables use zlib 1.2.3
170626 20:12:23 InnoDB: Initializing buffer pool, size = 128.0M
170626 20:12:23 InnoDB: Completed initialization of buffer pool
[B]170626 20:12:23 InnoDB: highest supported file format is Barracuda.
170626 20:12:23  InnoDB: Operating system error number 87 in a file operation.[/B]
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File name .\ib_logfile0
InnoDB: File operation call: 'aio read'.
InnoDB: Cannot continue operation.

MySQL could not be started.
Press any key to continue . . .

After a few adjectives that should not be repeated in polite company, I start troubleshooting.

The solution....

Open the MySQL config file (_Server\mysql\bin\my.cnf)
Add the highlighted line below.
Save the file and execute MySQL.bat and it should start properly.

[client]
password	= ascent
port		= 3306
socket		= /tmp/mysql.sock

[mysqld]
[B]innodb_flush_method=normal[/B]
basedir="../_Server/mysql"
datadir="../_Server/mysql/data"
port		= 3306
...
...
...

Just to test the limits of this Nexbox mini PC I have had five people connected to this little thing and surprisingly there was no notable lag.

Not that I would use this as a dedicated game server

 

[eyerobot]

Good fix. I ran into this when i was trying to transfer my characters from 7.0 to 7.0 2. It wouldn't run as one large query, but insisted on being set to run individual queries only. It did work, But i really don't see why it worked.

 

[Sikuri]

Hi, I know this is old...
But I need help with 483, file in operation.
It's exactly the same error as above, just different code.

I have applied this fix, but SQL still crashes after 15 minutes.
Can someone assist me?

 

[mastermind]

Error 483 is a general hardware failure. Make sure the disk teh database it on does not have any issues.
I guess the best advice I can give is to run a chkdsk /F or chkdsk /R command on the drive and see if there are any issues.

If the drive supports SMART (pretty much all do these days) you can typically get a free diag download from the drive manufacture.
Run the manufactures diagnostic and see if it reports anything.

Just keep in mind some of thore manufacture diags have a option to zero out the driver. Do not select those as it will blank the drive. The basic SMART tests should be enough to tell you if the drive is in good shape.

Good luck.