我不知道细节，我只是运行一些程序当我在新服务器上重新运行时移动服务器时，mysqld停止工作
日志
2019-10-04 11:12:22 b18 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.
2019-10-04 11:12:22 2840 [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.
2019-10-04 11:12:22 2840 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-10-04 11:12:22 2840 [Note] InnoDB: The InnoDB memory heap is disabled
2019-10-04 11:12:22 2840 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-10-04 11:12:22 2840 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-10-04 11:12:22 2840 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-10-04 11:12:22 2840 [Note] InnoDB: Using generic crc32 instructions
2019-10-04 11:12:22 2840 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2019-10-04 11:12:22 2840 [Note] InnoDB: Completed initialization of buffer pool
2019-10-04 11:12:22 2840 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-04 11:12:22 2840 [Note] InnoDB: The log sequence number 177026532 in ibdata file do not match the log sequence number 21817052062 in the ib_logfiles!
2019-10-04 11:12:22 2840 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2019-10-04 11:12:22 2840 [Note] InnoDB: Creating tablespace and datafile system tables.
2019-10-04 11:12:22 2840 [Note] InnoDB: Tablespace and datafile system tables created.
2019-10-04 11:12:22 2840 [Warning] InnoDB: Resizing redo log from 2*1536 to 2*320 pages, LSN=21817055855
2019-10-04 11:12:22 2840 [Warning] InnoDB: Starting to delete and rewrite log files.
2019-10-04 11:12:22 2840 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2019-10-04 11:12:22 2840 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2019-10-04 11:12:22 2840 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2019-10-04 11:12:23 2840 [Warning] InnoDB: New log files created, LSN=21817056268
2019-10-04 11:12:23 2840 [Note] InnoDB: 128 rollback segment(s) are active.
2019-10-04 11:12:23 2840 [Note] InnoDB: Waiting for purge to start
2019-10-04 11:12:23 2840 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.39-83.1 started; log sequence number 21817052062
2019-10-04 11:12:23 2848 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-10-04 11:12:23 2840 [Note] Plugin 'FEEDBACK' is disabled.
2019-10-04 11:12:23 2840 [Note] Server socket created on IP: '::'.
2019-10-04 11:12:23 2840 [ERROR] mysqld.exe: Table '.\mysql\user' is marked as crashed and should be repaired
2019-10-04 11:12:23 2840 [Warning] Checking table: '.\mysql\user'
2019-10-04 11:12:23 2840 [ERROR] mysql.user: 2 clients are using or haven't closed the table properly
2019-10-04 11:12:23 2840 [ERROR] Missing system table mysql.roles_mapping; please run mysql_upgrade to create it
2019-10-04 11:12:23 2840 [ERROR] Incorrect definition of table mysql.event: expected column 'sql_mode' at position 14 to have type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVALID_DATES','ERROR_FOR_DIVISION_BY_ZERO','TRADITIONAL','NO_AUTO_CREATE_USER','HIGH_NOT_PRECEDENCE','NO_ENGINE_SUBSTITUTION','PAD_CHAR_TO_FULL_LENGTH'), found type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','NOT_USED','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_A
2019-10-04 11:12:23 2840 [ERROR] mysqld.exe: Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
2019-10-04 11:12:23 3808 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
2019-10-04 11:12:23 2840 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.36-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2019-10-04 11:12:28 4240 [ERROR] Incorrect definition of table mysql.proc: expected column 'sql_mode' at position 14 to have type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVA
2019-10-04 11:12:28 1090 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2019-10-04 11:15:05 d10 InnoDB: Assertion failure in thread 3344 in file trx0purge.cc line 682
InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
191004 11:15:05 [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 https://mariadb.com/kb/en/reporting-bugs
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.1.36-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=15
max_threads=1001
thread_count=15
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787136 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()
mysqld.exe!strxnmov()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlInitializeExceptionChain()
ntdll.dll!RtlInitializeExceptionChain()
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.
2019-10-04 11:16:35 b54 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.
2019-10-04 11:16:35 2900 [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.
2019-10-04 11:16:35 2900 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-10-04 11:16:35 2900 [Note] InnoDB: The InnoDB memory heap is disabled
2019-10-04 11:16:35 2900 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-10-04 11:16:35 2900 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-10-04 11:16:35 2900 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-10-04 11:16:35 2900 [Note] InnoDB: Using generic crc32 instructions
2019-10-04 11:16:35 2900 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2019-10-04 11:16:35 2900 [Note] InnoDB: Completed initialization of buffer pool
2019-10-04 11:16:35 2900 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-04 11:16:35 2900 [Note] InnoDB: Starting crash recovery from checkpoint LSN=21817056642
2019-10-04 11:16:35 2900 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2019-10-04 11:16:35 2900 [Note] InnoDB: Starting final batch to recover 2 pages from redo log
2019-10-04 11:16:36 2900 [Note] InnoDB: 128 rollback segment(s) are active.
2019-10-04 11:16:36 2900 [Note] InnoDB: Waiting for purge to start
2019-10-04 11:16:36 17c8 InnoDB: Assertion failure in thread 6088 in file trx0purge.cc line 682
InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
191004 11:16:36 [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 https://mariadb.com/kb/en/reporting-bugs
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.1.36-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787136 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...
2019-10-04 11:16:36 2900 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.39-83.1 started; log sequence number 21817060575
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlInitializeExceptionChain()
ntdll.dll!RtlInitializeExceptionChain()
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.
2019-10-04 11:16:36 3992 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-10-04 11:16:36 2900 [Note] Plugin 'FEEDBACK' is disabled.
2019-10-04 11:16:36 2900 [Note] Server socket created on IP: '::'.
2019-10-04 11:16:38 2900 [ERROR] Missing system table mysql.roles_mapping; please run mysql_upgrade to create it
2019-10-04 11:16:38 2900 [ERROR] Incorrect definition of table mysql.event: expected column 'sql_mode' at position 14 to have type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVALID_DATES','ERROR_FOR_DIVISION_BY_ZERO','TRADITIONAL','NO_AUTO_CREATE_USER','HIGH_NOT_PRECEDENCE','NO_ENGINE_SUBSTITUTION','PAD_CHAR_TO_FULL_LENGTH'), found type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','NOT_USED','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_A
2019-10-04 11:16:38 2900 [ERROR] mysqld.exe: Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
2019-10-04 11:16:38 5660 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
2019-10-04 11:16:38 2900 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.36-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
下面是我尝试过的配置sqlinnodb_force_recovery = 4mysqld可以运行，但是我尝试编辑数据，它告诉我[只读
# Example MySQL config file for small systems.
#
# This is for a system with little memory (<= 64M) where MySQL is only used
# from time to time and it's important that the mysqld daemon
# doesn't use much resources.
#
# You can copy this file to
# C:/xampp/mysql/bin/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is C:/xampp/mysql/data) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.
# The following options will be passed to all MySQL clients
[client]
# password = your_password
port = 3306
socket = "C:/xampp/mysql/mysql.sock"
# Here follows entries for some specific programs
# The MySQL server
[mysqld]
port= 3306
socket = "C:/xampp/mysql/mysql.sock"
basedir = "C:/xampp/mysql"
tmpdir = "C:/xampp/tmp"
datadir = "C:/xampp/mysql/data"
pid_file = "mysql.pid"
# enable-named-pipe
key_buffer = 16M
max_allowed_packet = 1M
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
log_error = "mysql_error.log"
# Change here for bind listening
# bind-address="127.0.0.1"
# bind-address = ::1 # for ipv6
# Where do all the plugins live
plugin_dir = "C:/xampp/mysql/lib/plugin/"
# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
# commented in by lampp security
#skip-networking
#skip-federated
# Replication Master Server (default)
# binary logging is required for replication
# log-bin deactivated by default since XAMPP 1.4.11
#log-bin=mysql-bin
# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1
# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
# where you replace <host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin
# Point the following paths to different dedicated disks
#tmpdir = "C:/xampp/tmp"
#log-update = /path-to-dedicated-directory/hostname
# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000
# Comment the following if you are using InnoDB tables
#skip-innodb
innodb_data_home_dir = "C:/xampp/mysql/data"
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = "C:/xampp/mysql/data"
#innodb_log_arch_dir = "C:/xampp/mysql/data"
## You can set .._buffer_pool_size up to 50 - 80 %
## of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 16M
innodb_additional_mem_pool_size = 2M
## Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50
## UTF 8 Settings
#init-connect=\'SET NAMES utf8\'
#collation_server=utf8_unicode_ci
#character_set_server=utf8
#skip-character-set-client-handshake
#character_sets-dir="C:/xampp/mysql/share/charsets"
[mysqldump]
quick
max_allowed_packet = 16M
[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates
[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M
[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M
[mysqlhotcopy]
interactive-timeout
如何解决？我不知道这个错误谢谢你的帮助我
维修表TABLE_NAME;该表的存储引擎不支持维修
我尝试通过ALTER TABLE table_name ENGINE = MyISAM更改引擎。这是行不通的，我只能以只读方式使用innodb_force_recovery = 4
我尝试删除所有数据并将新数据放入数据库我这样做ALTER TABLE table_name ENGINE = MyISAM;好的，我可以在表问题中将引擎从innodb更改为MyISAM我运行程序几乎就可以了
mysqld已停止工作我认为是新错误因为我尝试了innodb_force_recovery = 4但这次我不能启动mysql像以前一样，我尝试myisam-recover-options = BACKUP，FORCE或myisam-recover = BACKUP，FORCE但我无法启动mysql
更新新内容：
我正在使用innodb_force_recovery = 5，我可以再次启动mysql。但是我在同一张表中遇到了问题
同一表中，我将Engine更改为MyISAM，这告诉我表'Same Table'在引擎中不存在