Cannot connect with MYSQL after update

[Lonestar jack]

Somehow a new MYSQL version (MYSQL57) appeared and I cannot make the connection through XAMPP now. What do I do so I do not lose my data?
I can't make there through PHPMYADMIN either. I do not understand the recommended recovery instructions at the bottom.


12:49:01 PM [mysql] Error: MySQL shutdown unexpectedly.
12:49:01 PM [mysql] This may be due to a blocked port, missing dependencies,
12:49:01 PM [mysql] improper privileges, a crash, or a shutdown by another method.
12:49:01 PM [mysql] Press the Logs button to view error logs and check
12:49:01 PM [mysql] the Windows Event Viewer for more clues
12:49:01 PM [mysql] If you need more help, copy and post this
12:49:01 PM [mysql] entire log window on the forums

2017-07-04 12:48:58 c94 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2017-07-04 12:48:58 3220 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-07-04 12:48:58 3220 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-07-04 12:48:58 3220 [Note] InnoDB: The InnoDB memory heap is disabled
2017-07-04 12:48:58 3220 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-07-04 12:48:58 3220 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-07-04 12:48:58 3220 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-07-04 12:48:58 3220 [Note] InnoDB: Using generic crc32 instructions
2017-07-04 12:48:58 3220 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-07-04 12:48:58 3220 [Note] InnoDB: Completed initialization of buffer pool
2017-07-04 12:48:58 3220 [Note] InnoDB: Highest supported file format is Barracuda.
2017-07-04 12:48:59 3220 [Note] InnoDB: 128 rollback segment(s) are active.
2017-07-04 12:48:59 3220 [Note] InnoDB: Waiting for purge to start
2017-07-04 12:48:59 3220 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.32-79.0 started; log sequence number 5023208
2017-07-04 12:48:59 12620 [Note] InnoDB: Dumping buffer pool(s) not yet started
Cannot find checkpoint record at LSN (1,0x3137)

2017-07-04 12:48:59 3220 [ERROR] mysqld.exe: Aria recovery failed. Please run aria_chk -r on all Aria tables and delete all aria_log.######## files
2017-07-04 12:48:59 3220 [ERROR] Plugin 'Aria' init function returned error.
2017-07-04 12:48:59 3220 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2017-07-04 12:48:59 3220 [Note] Plugin 'FEEDBACK' is disabled.
2017-07-04 12:48:59 3220 [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as mysqld was configured with --with-aria-tmp-tables
2017-07-04 12:48:59 3220 [ERROR] Aborting

[Nobbie]

Somehow a new MYSQL version (MYSQL57) appeared

What do you mean by that??

I do not understand the recommended recovery instructions at the bottom.

What exactly do you not understand? This is the recommendation:

Code: Select all

Please run aria_chk -r on all Aria tables and delete all aria_log.######## files

Obviously there as a "aria_chk.exe" within the MySQL (MariaDB) installation, call it in a terminal with option -r on all tables (i think you will find the tables in the database folder). If in doubt, i would simply enter "aria_chk -r" in a terminal and wait for a message. You have to append the tables of your installation. And "delete all aria_log.#######" means exactly what it says. This can be done as well in a terminal, or simply in the windows explorer. You know how to delete files?!

Thats all.