Bug #85339 Mysqld server not starting in win10
Submitted: 7 Mar 2017 8:49 Modified: 7 Mar 2017 12:49
Reporter: Filippo Berardo Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:5.7 OS:Windows (installed on macbook)
Assigned to: CPU Architecture:Any
Tags: innoDb problems, server not starting

[7 Mar 2017 8:49] Filippo Berardo
Description:
I installed the mysql installer and then i tried with mYsql zip file but i had the same problem. When the installer try to start the service it fails because of some problems with innodb tables. I tried to change th parameter : innodb_flush_method=normal

and deleting log files and something happnes when starting server but it doesn't start.
 here the log file :
2017-03-07T08:48:36.217396Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-03-07T08:48:36.217396Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2017-03-07T08:48:36.217396Z 0 [Note] C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe (mysqld 5.7.17-log) starting as process 1152 ...
2017-03-07T08:48:36.233022Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-03-07T08:48:36.233022Z 0 [Note] InnoDB: Uses event mutexes
2017-03-07T08:48:36.233022Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-03-07T08:48:36.233022Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-03-07T08:48:36.233022Z 0 [Note] InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB
2017-03-07T08:48:36.233022Z 0 [Note] InnoDB: Number of pools: 1
2017-03-07T08:48:36.233022Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2017-03-07T08:48:36.233022Z 0 [Note] InnoDB: Initializing buffer pool, total size = 8M, instances = 1, chunk size = 8M
2017-03-07T08:48:36.233022Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-03-07T08:48:36.264351Z 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2017-03-07T08:48:36.266359Z 0 [Note] InnoDB: Setting file '.\ibdata1' size to 12 MB. Physically writing the file full; Please wait ...
2017-03-07T08:48:36.286158Z 0 [Note] InnoDB: File '.\ibdata1' size is now 12 MB.
2017-03-07T08:48:36.317353Z 0 [Note] InnoDB: Setting log file .\ib_logfile101 size to 48 MB
2017-03-07T08:48:36.448779Z 0 [Note] InnoDB: Setting log file .\ib_logfile1 size to 48 MB
2017-03-07T08:48:36.617671Z 0 [ERROR] InnoDB: Operating system error number 87 in a file operation.
2017-03-07T08:48:36.633287Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2017-03-07T08:48:36.633287Z 0 [ERROR] InnoDB: File .\ib_logfile101: 'aio write' returned OS error 187. Cannot continue operation
2017-03-07T08:48:36.648968Z 0 [ERROR] InnoDB: Cannot continue operation.

How to repeat:
INstall mysql 5.7 in a macbook with win 10 installed with bootcamp.
[7 Mar 2017 12:49] Chiranjeevi Battula
Hello Filippo Berardo,

Thank you for the bug report.
This is most likely duplicate of Bug #85020, please see Bug #85020.

Thanks,
Chiranjeevi.