mysql突然挂掉，一直启动不了，那位大神路过帮忙看看呗！！

急，有哪位mysql大神给解答一下，万分感激；

数据库突然关闭，然后就启动不了了，报错如下：

200728 10:38:32 mysqld_safe Starting mysqld daemon with databases from /www/server/data
2020-07-28 10:38:33 22496615563072 [Warning] option 'max_allowed_packet': unsigned value 107374182400 adjusted to 1073741824
2020-07-28 10:38:33 22496615563072 [Note] /www/server/mysql/bin/mysqld (mysqld 10.1.43-MariaDB) starting as process 29031 ...
2020-07-28 10:38:33 22496615563072 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2020-07-28 10:38:33 22496615563072 [Note] InnoDB: The InnoDB memory heap is disabled
2020-07-28 10:38:33 22496615563072 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-07-28 10:38:33 22496615563072 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-07-28 10:38:33 22496615563072 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-07-28 10:38:33 22496615563072 [Note] InnoDB: Using SSE crc32 instructions
2020-07-28 10:38:33 22496615563072 [Note] InnoDB: Initializing buffer pool, size = 4.0G
2020-07-28 10:38:33 22496615563072 [Note] InnoDB: Completed initialization of buffer pool
2020-07-28 10:38:33 22496615563072 [Note] InnoDB: Highest supported file format is Barracuda.
2020-07-28 10:38:33 22496615563072 [Note] InnoDB: Starting crash recovery from checkpoint LSN=24922590007
2020-07-28 10:38:33 22496615563072 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2020-07-28 10:38:34 22496615563072 [ERROR] InnoDB: Tried to read 65536 bytes at offset 272377856. Was only able to read 2048.
FAILInnoDB: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 46813952
2020-07-28 10:38:34 22496615563072 [Note] InnoDB: Starting final batch to recover 50159 pages from redo log
InnoDB: Last MySQL binlog file position 0 535724381, file name ./mysql-bin.000021
2020-07-28 10:38:35 22496615563072 [ERROR] InnoDB: Table wangcai/cmf_sign in the InnoDB data dictionary has tablespace id 202, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2020-07-28 10:38:35 22496615563072 [Note] InnoDB: 128 rollback segment(s) are active.
2020-07-28 10:38:35 22489036293888 [Note] InnoDB: Starting in background the rollback of recovered transactions
2020-07-28 10:38:35 22496615563072 [Note] InnoDB: Waiting for purge to start
2020-07-28 10:38:35 147423050700 InnoDB: Error: Write to file /www/server/data/ib_logfile1 failed at offset 272379392.
InnoDB: 1024 bytes should have been written, only 512 were written.
InnoDB: Operating system error number 5.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2020-07-28 10:38:35 147423050700  InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
 InnoDB: Operation os_file_write_func to file /home/annyudie/deb/bt-mariadb101/bt-mariadb101-10.1.43/storage/xtradb/os/os0file.cc and at line 5292
2020-07-28 10:38:35 22489036293888 [ERROR] InnoDB: File /www/server/data/ib_logfile1: 'os_file_write_func' returned OS error 205. Cannot continue operation
200728 10:38:35 [ERROR] mysqld got signal 6 ;
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.43-MariaDB
key_buffer_size=1073741824
read_buffer_size=4194304
max_used_connections=0
max_threads=602
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5992644 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...
stack_bottom = 0x0 thread_stack 0x80000
2020-07-28 10:38:35 22496615563072 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.45-86.1 started; log sequence number 24968401385
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x29)[0x5567c3dfc169]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x52b)[0x5567c39deb7b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x128a0)[0x1475e56d08a0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x1475e4be4f47]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x1475e4be68b1]
/www/server/mysql/bin/mysqld(+0x8050b1)[0x5567c3c6e0b1]
/www/server/mysql/bin/mysqld(+0x807ac3)[0x5567c3c70ac3]
/www/server/mysql/bin/mysqld(+0x922053)[0x5567c3d8b053]
/www/server/mysql/bin/mysqld(+0x7e6d3a)[0x5567c3c4fd3a]
/www/server/mysql/bin/mysqld(+0x7e7470)[0x5567c3c50470]
/www/server/mysql/bin/mysqld(+0x891477)[0x5567c3cfa477]
/www/server/mysql/bin/mysqld(+0x891df1)[0x5567c3cfadf1]
/www/server/mysql/bin/mysqld(+0x88692f)[0x5567c3cef92f]
/www/server/mysql/bin/mysqld(+0x88875d)[0x5567c3cf175d]
/www/server/mysql/bin/mysqld(+0x888cc9)[0x5567c3cf1cc9]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db)[0x1475e56c56db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x1475e4cc7a3f]
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.
200728 10:38:36 mysqld_safe mysqld from pid file /www/server/data/ubuntu.pid ended