WampServer

Hi guys,

I need help with WampServer.

Currently running windows 10 on macbook pro touch bar 2018 using bootcamp.
Wampserver 3.1.0
Mysql 5.7.19
mariaDB 10.2.8

Apache is running fine with no problems.

However MySQL keep getting this error

2018-09-02T07:41:30.788331Z 0 [ERROR] InnoDB: Header page consists of zero bytes in datafile: .\ibdata1, Space ID:0, Flags: 0. Please refer to [dev.mysql.com] for how to resolve the issue.
2018-09-02T07:41:30.788331Z 0 [ERROR] InnoDB: Corrupted page [page id: space=0, page number=0] of datafile '.\ibdata1' could not be found in the doublewrite buffer.
2018-09-02T07:41:30.803954Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
2018-09-02T07:41:31.130596Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2018-09-02T07:41:31.130596Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-09-02T07:41:31.130596Z 0 [ERROR] Failed to initialize plugins.
2018-09-02T07:41:31.130596Z 0 [ERROR] Aborting

Have tried adding the flush on my.ini, deleting data files etc doesn't work.

this is the log for innob


2018-09-02 15:41:30 12548 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-09-02 15:41:30 12548 [Note] InnoDB: Uses event mutexes
2018-09-02 15:41:30 12548 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-09-02 15:41:30 12548 [Note] InnoDB: Number of pools: 1
2018-09-02 15:41:30 12548 [Note] InnoDB: Using generic crc32 instructions
2018-09-02 15:41:30 12548 [Note] InnoDB: Initializing buffer pool, total size = 32M, instances = 1, chunk size = 32M
2018-09-02 15:41:30 12548 [Note] InnoDB: Completed initialization of buffer pool
2018-09-02 15:41:30 12548 [Note] InnoDB: Highest supported file format is Barracuda.
2018-09-02 15:41:30 12548 [Warning] InnoDB: Retry attempts for reading partial data failed.
2018-09-02 15:41:30 12548 [ERROR] InnoDB: Tried to read 512 bytes at offset 0, but was only able to read 0
2018-09-02 15:41:30 12548 [ERROR] InnoDB: File (unknown): 'read' returned OS error 0. Cannot continue operation
180902 15:41:30 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see [mariadb.com]

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.2.8-MariaDB
key_buffer_size=67108864
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 70631 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_parameter_handler()[my_init.c:259]
mysqld.exe!raise()[signal.cpp:516]
mysqld.exe!abort()[abort.cpp:71]
mysqld.exe!os_file_handle_error_cond_exit()[os0file.cc:5207]
mysqld.exe!os_file_read_page()[os0file.cc:5089]
mysqld.exe!os_file_read_func()[os0file.cc:5429]
mysqld.exe!fil_io()[fil0fil.cc:5398]
mysqld.exe!log_group_header_read()[log0log.cc:1564]
mysqld.exe!recv_find_max_checkpoint()[log0recv.cc:949]
mysqld.exe!recv_recovery_from_checkpoint_start()[log0recv.cc:3151]
mysqld.exe!innobase_start_or_create_for_mysql()[srv0start.cc:2219]
mysqld.exe!innobase_init()[ha_innodb.cc:4428]
mysqld.exe!ha_initialize_handlerton()[handler.cc:512]
mysqld.exe!plugin_initialize()[sql_plugin.cc:1413]
mysqld.exe!plugin_init()[sql_plugin.cc:1694]
mysqld.exe!init_server_components()[mysqld.cc:5256]
mysqld.exe!win_main()[mysqld.cc:5848]
mysqld.exe!mysql_service()[mysqld.cc:6107]
mysqld.exe!thread_start<void (__cdecl*)(void * __ptr64)>()[thread.cpp:115]
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
The manual page at [dev.mysql.com] contains
information that should help you find out what is causing the crash.

Have also tried follow troubleshooting steps listed but still not working.
Hope someone can assist!
Thanks in advance!



Edited 1 time(s). Last edit at 09/02/2018 09:48AM by kimchi94.

Hi,

> running windows 10 on macbook pro touch bar 2018 using bootcamp.

First : Wampserver does not work on a FAT32 or exFAT drive. It only works on NTFS disk.
Second : MySQL does not work on a 4KN (4096 native formated drive)

Open a command windows as an administrator (The word Administrator must be in the title bar) and in this command windows, type:

fsutil fsinfo ntfsinfo c:

Note : If the drive letter on which Wampserver is installed is not c:, modify the command accordingly

Put the result here.

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

C:\Windows\system32>fsutil fsinfo ntfsinfo c:
NTFS Volume Serial Number : 0x34f5ee1202469ff7
NTFS Version : 3.1
LFS Version : 2.0
Number Sectors : 0x00000000017713ff
Total Clusters : 0x00000000017713ff
Free Clusters : 0x0000000000dd546c
Total Reserved : 0x0000000000001b13
Bytes Per Sector : 4096
Bytes Per Physical Sector : 4096
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 4096
Clusters Per FileRecord Segment : 1
Mft Valid Data Length : 0x000000002f000000
Mft Start Lcn : 0x0000000000000004
Mft2 Start Lcn : 0x0000000000bb89ff
Mft Zone Start : 0x00000000007ba0e0
Mft Zone End : 0x00000000007bfe20
Max Device Trim Extent Count : 256
Max Device Trim Byte Count : 0xffffffff
Max Volume Trim Extent Count : 62
Max Volume Trim Byte Count : 0x40000000
Resource Manager Identifier : 86753D6D-A3B7-11E8-A3FC-D2960C16B347

UPDATE
I have included this following on my.ini of MYSQL:
innodb_flush_method=normal

And this on my.ini of MariaDB:
innodb_force_recovery = 6

with this 2 my Wamp is green. However i don't think this is a permanent solution.

Hi,

Bytes Per Sector  :                4096
Bytes Per Physical Sector :        4096

This is a factory formatted 4K Native type disc. (4KN)
MySQL does not work on this type of disk, only on 512 Native (512N - Bytes per sector 512, Bytes Per Physical Sector 512) or 512 Extended (512E - Bytes per sector 512, Bytes Per Physical Sector 4096).
Microsoft has made the necessary corrections for MySQL Server, but MySQL has still not done anything to make it work, even on recent versions.

In some very limited cases, MariaDB (which comes from MySQL) can run on a 4KN disk, but for you, this is not the case.
The only solution is to install Wampserver on a 512N or 512E disk. There is no other.

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

I have changed the my.ini for mariaDB to these:

innodb_buffer_pool_size = 256M
innodb_log_file_size = 256M
innodb_thread_concurrency = 16
innodb_flush_log_at_trx_commit = 2
innodb_flush_method = normal

and removed the flush 6.

Also maintained the flush normal for mysql. and it works! isit okay?

Hi,

> Also maintained the flush normal for mysql. and it works! isit okay?
If MariaDB works with these parameters, good for you.
You can disable MySQL :
Right-Click Wampmanager tray icon -> Wamp Settings -> Allow MySQL to uncheck it

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons