Ошибка запуска mysqld.exe

[cousinr]

Здравствуйте, пожалуйста помогите, комп вырубился во время работы, а после загрузки сайт не работает, в базу не войти ни под root без пароля, ни под mysql.. Как я уже понял, это из-за не коректного завершения работы. Но как исправить пока не понял, куда зайти, где что изменить и прописать, подскажите пожалуйсоа детально. MySQL-5.7-x64. Прошел по ссылке https://dev.mysql.com/doc/refman/5.7/en ... overy.html, но не понял где это и как... Резервная копия ibdata1 делалась почти месяц, а за это время было проделано огромнейшее количество работы и я не разбираюсь особо в БД и пхп ((

2020-03-22T16:09:03.408327Z 0 [Note] d:\onedrive\ospanel\modules\database\MySQL-5.7-x64\bin\mysqld.exe (mysqld 5.7.25) starting as process 11696 ...
2020-03-22T16:09:03.419328Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2020-03-22T16:09:03.420328Z 0 [Note] InnoDB: Uses event mutexes
2020-03-22T16:09:03.420328Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2020-03-22T16:09:03.420328Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-03-22T16:09:03.421328Z 0 [Note] InnoDB: Number of pools: 1
2020-03-22T16:09:03.422328Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2020-03-22T16:09:03.427328Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2020-03-22T16:09:03.449330Z 0 [Note] InnoDB: Completed initialization of buffer pool
2020-03-22T16:09:04.112367Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2020-03-22T16:09:04.422385Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 3594231057
2020-03-22T16:09:04.422385Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 3594231066
2020-03-22T16:09:04.422385Z 0 [Note] InnoDB: Database was not shutdown normally!
2020-03-22T16:09:04.422385Z 0 [Note] InnoDB: Starting crash recovery.
2020-03-22T16:09:07.869582Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=295] log sequence number 3594231266 is in the future! Current system log sequence number 3594231075.
2020-03-22T16:09:07.869582Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/ ... overy.html for information about forcing recovery.
2020-03-22T16:09:07.962588Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=192] log sequence number 3594231584 is in the future! Current system log sequence number 3594231075.
2020-03-22T16:09:07.962588Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/ ... overy.html for information about forcing recovery.
2020-03-22T16:09:08.050593Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=407] log sequence number 3594231584 is in the future! Current system log sequence number 3594231075.
2020-03-22T16:09:08.050593Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/ ... overy.html for information about forcing recovery.
2020-03-22T16:09:08.061593Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=193] log sequence number 3594231853 is in the future! Current system log sequence number 3594231075.
2020-03-22T16:09:08.062593Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/ ... overy.html for information about forcing recovery.
2020-03-22T16:09:08.128597Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=194] log sequence number 3594232149 is in the future! Current system log sequence number 3594231075.
2020-03-22T16:09:08.128597Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/ ... overy.html for information about forcing recovery.
2020-03-22T16:09:08.205602Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=480] log sequence number 3594232300 is in the future! Current system log sequence number 3594231075.
2020-03-22T16:09:08.205602Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/ ... overy.html for information about forcing recovery.
2020-03-22T16:09:08.260605Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=195] log sequence number 3594284806 is in the future! Current system log sequence number 3594231075.
2020-03-22T16:09:08.260605Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/ ... overy.html for information about forcing recovery.
2020-03-22T16:09:08.272605Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=405] log sequence number 3594284806 is in the future! Current system log sequence number 3594231075.
2020-03-22T16:09:08.272605Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/ ... overy.html for information about forcing recovery.
2020-03-22T16:09:08.353610Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=301] log sequence number 3594285162 is in the future! Current system log sequence number 3594231075.
2020-03-22T16:09:08.353610Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/ ... overy.html for information about forcing recovery.
2020-03-22T16:09:15.136998Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2020-03-22T16:09:15.136998Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-03-22T16:09:15.137998Z 0 [Note] InnoDB: Setting file 'd:\onedrive\ospanel\userdata\MySQL-5.7-x64\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-03-22T16:09:15.260005Z 0 [Note] InnoDB: File 'd:\onedrive\ospanel\userdata\MySQL-5.7-x64\ibtmp1' size is now 12 MB.
2020-03-22T16:09:15.265005Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2020-03-22T16:09:15.265005Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2020-03-22T16:09:15.266005Z 0 [Note] InnoDB: Waiting for purge to start
2020-03-22 19:09:15 0x26f8 InnoDB: Assertion failure in thread 9976 in file fut0lst.ic line 85
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/ ... overy.html
InnoDB: about forcing recovery.
16:09:15 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=0
max_threads=64
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 295692 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x17c41e70
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...
2020-03-22T16:09:15.324009Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 11839ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
2020-03-22T16:09:15.355010Z 0 [Note] InnoDB: 5.7.25 started; log sequence number 3594231066
2020-03-22T16:09:15.356011Z 0 [Note] Plugin 'FEDERATED' is disabled.
2020-03-22T16:09:15.370011Z 0 [Note] InnoDB: Loading buffer pool(s) from d:\onedrive\ospanel\userdata\MySQL-5.7-x64\ib_buffer_pool
2020-03-22T16:09:15.438015Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2020-03-22T16:09:15.441015Z 0 [Note] - '127.0.0.1' resolves to '127.0.0.1';
2020-03-22T16:09:15.441015Z 0 [Note] Server socket created on IP: '127.0.0.1'.
13fa63402 mysqld.exe!my_errno()
7fee7a5ec9d MSVCR120.dll!raise()
7fee7a64874 MSVCR120.dll!abort()
13fb7fa04 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
13fb27aec mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
13fb26d44 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
13fb262fc mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
13fb25c42 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
13fac2fde mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
13fac727c mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
778959cd kernel32.dll!BaseThreadInitThunk()
77aca561 ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0):
Connection ID (thread ID): 0
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2020-03-22T16:09:47.398843Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 31069ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)