local installation recovery after system crash

[numnah13]

Hey there,
I can't make my site work again after unexpected system crash. I had WP site (with Avada theme) on localhost xampp. No database exported. What I do have is the whole folders structure from the previous installation that worked fine.
However when I paste the content of mysql/data and my previous wp installation from htdocs into my new xampp installation, msql module crashes. Any idea what I can do with it?
Thanks

2017-08-12 19:27:17 107c 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-08-12 19:27:17 4220 [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-08-12 19:27:17 4220 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-08-12 19:27:17 4220 [Note] InnoDB: The InnoDB memory heap is disabled
2017-08-12 19:27:17 4220 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-08-12 19:27:17 4220 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-08-12 19:27:17 4220 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-08-12 19:27:17 4220 [Note] InnoDB: Using generic crc32 instructions
2017-08-12 19:27:17 4220 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-08-12 19:27:17 4220 [Note] InnoDB: Completed initialization of buffer pool
2017-08-12 19:27:17 4220 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2017-08-12 19:27:17 4220 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2017-08-12 19:27:17 4220 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2017-08-12 19:27:17 4220 [ERROR] InnoDB: Cannot create C:\xampp\mysql\data\ib_logfile1
2017-08-12 19:27:17 4220 [ERROR] Plugin 'InnoDB' init function returned error.
2017-08-12 19:27:17 4220 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-08-12 19:27:17 4220 [Note] Plugin 'FEEDBACK' is disabled.
2017-08-12 19:27:17 4220 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-08-12 19:27:17 4220 [ERROR] Aborting

[numnah13]

Anybody?
Is this too messed up to fix or too obvious to even bother?

[efremmc2]

After doing your migration, please change your mysql configuration file (my.cnf or my.ini), located in %systemdrive%\xampp\mysql\bin\my.ini for Windows. The same change is also available for Linux. Open the my.ini file, search for 'innodb', place a “#” in front of the line that reads, innodb_additional_mem_pol_size, add the following line:

innodb_use_sys_malloc=1

save the file and recycle the database server.

Additionally, when doing a migration, there are several factors that should be taken into consideration. First, review new features and any readme documentation on what changes were made. This is very important from release levels as some system variables are deprecated. Second, record system configuration settings between the old and new system. There are several ways to review the new system before migration, review the default system settings such as my.ini and several *.ini files located in the mysql directory. The file my,ini is usually in a subfolder/directory under bin\my.ini. They normally include several configuration models for optimization of generic workloads for sizing such as 'my-huge.ini', 'my-small.ini', and related.

[efremmc2]

Anybody?
Is this too messed up to fix or too obvious to even bother?

See below, just join the forums.

[numnah13]

I'll give it a try.
Thanks a lot!

[numnah13]

I commented out that line and added "innodb_use_sys_malloc=1" line in my.ini (don't have my.cnf) but the problem remains
I am a total noob so may not quite get what you're saying, but when installed exact same version of xampp, there was the same problem.

[efremmc2]

Okay, save the current my.ini file into another user directory. There are several configurations available in the root directory for my-small.ini or my-huge.ini. copy one of these as the my.ini and restart the service. Please report back the log as shown in your first posting.

[numnah13]

I replaced content of my.ini with a content from my-huge.ini.
MySQL still shuts down and I can't access logs, because now it says that mysql_error.log does not exist and asks if I want to create one.