Error establishing a database connection - lỗi mariadb không thể khởi động


(Minh Hưng) #1

Có pro nào biét fix lỗi này ko. mình hay bị . lâu lâu lại bị :frowning:

Error establishing a database connection

2020-03-16 17:04:46 7f2e65ed7700 InnoDB: Error: Write to file ./ib_logfile1 failed at offset 157994496.
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-03-16 17:04:46 7f2e65ed7700 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
200316 17:04:46 [ERROR] InnoDB: File ./ib_logfile1: ‘os_file_write_func’ returned OS error 105. Cannot continue operation
200316 17:04:47 mysqld_safe Number of processes running now: 0
200316 17:04:47 mysqld_safe mysqld restarted
200316 17:04:47 [Note] /usr/sbin/mysqld (mysqld 10.0.38-MariaDB) starting as process 10598 …
200316 17:04:47 [Note] InnoDB: Using mutexes to ref count buffer pool pages
200316 17:04:47 [Note] InnoDB: The InnoDB memory heap is disabled
200316 17:04:47 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
200316 17:04:47 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
200316 17:04:47 [Note] InnoDB: Compressed tables use zlib 1.2.7
200316 17:04:47 [Note] InnoDB: Using Linux native AIO
200316 17:04:47 [Note] InnoDB: Not using CPU crc32 instructions
200316 17:04:47 [Note] InnoDB: Initializing buffer pool, size = 1.0G
200316 17:04:47 [Note] InnoDB: Completed initialization of buffer pool
200316 17:04:47 [Note] InnoDB: Highest supported file format is Barracuda.
200316 17:04:47 [Note] InnoDB: Starting crash recovery from checkpoint LSN=113300724338
200316 17:05:00 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer…
200316 17:05:01 [ERROR] InnoDB: Tried to read 65536 bytes at offset 157976576. Was only able to read 18432.
2020-03-16 17:05:01 7f3e298ed8c0 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
200316 17:05:01 [ERROR] InnoDB: File (unknown): ‘read’ returned OS error 105. Cannot continue operation
200316 17:05:01 mysqld_safe mysqld from pid file /var/lib/mysql/minhhungtsbd.me.pid ended
200316 17:51:11 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200316 17:51:11 [Note] /usr/sbin/mysqld (mysqld 10.0.38-MariaDB) starting as process 2074 …
200316 17:51:11 [Note] InnoDB: Using mutexes to ref count buffer pool pages
200316 17:51:11 [Note] InnoDB: The InnoDB memory heap is disabled
200316 17:51:11 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
200316 17:51:11 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
200316 17:51:11 [Note] InnoDB: Compressed tables use zlib 1.2.7
200316 17:51:11 [Note] InnoDB: Using Linux native AIO
200316 17:51:11 [Note] InnoDB: Not using CPU crc32 instructions
200316 17:51:11 [Note] InnoDB: Initializing buffer pool, size = 1.0G
200316 17:51:11 [Note] InnoDB: Completed initialization of buffer pool
200316 17:51:11 [Note] InnoDB: Highest supported file format is Barracuda.
200316 17:51:11 [Note] InnoDB: Starting crash recovery from checkpoint LSN=113300724338
200316 17:51:15 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer…
200316 17:51:16 [ERROR] InnoDB: Tried to read 65536 bytes at offset 157976576. Was only able to read 18432.
2020-03-16 17:51:16 7f699a3bd8c0 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
200316 17:51:16 [ERROR] InnoDB: File (unknown): ‘read’ returned OS error 105. Cannot continue operation
200316 17:51:16 mysqld_safe mysqld from pid file /var/lib/mysql/minhhungtsbd.me.pid ended
200316 17:57:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200316 17:57:58 [Note] /usr/sbin/mysqld (mysqld 10.0.38-MariaDB) starting as process 2113 …
200316 17:57:58 [Note] InnoDB: Using mutexes to ref count buffer pool pages
200316 17:57:58 [Note] InnoDB: The InnoDB memory heap is disabled
200316 17:57:58 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
200316 17:57:58 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
200316 17:57:58 [Note] InnoDB: Compressed tables use zlib 1.2.7
200316 17:57:58 [Note] InnoDB: Using Linux native AIO
200316 17:57:58 [Note] InnoDB: Not using CPU crc32 instructions
200316 17:57:58 [Note] InnoDB: Initializing buffer pool, size = 1.0G
200316 17:57:58 [Note] InnoDB: Completed initialization of buffer pool
200316 17:57:58 [Note] InnoDB: Highest supported file format is Barracuda.
200316 17:57:58 [Note] InnoDB: Starting crash recovery from checkpoint LSN=113300724338
200316 17:58:00 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer…
200316 17:58:01 [ERROR] InnoDB: Tried to read 65536 bytes at offset 157976576. Was only able to read 18432.
2020-03-16 17:58:01 7fb9340018c0 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
200316 17:58:01 [ERROR] InnoDB: File (unknown): ‘read’ returned OS error 105. Cannot continue operation
200316 17:58:02 mysqld_safe mysqld from pid file /var/lib/mysql/minhhungtsbd.me.pid ended
200316 18:02:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200316 18:02:30 [Note] /usr/sbin/mysqld (mysqld 10.0.38-MariaDB) starting as process 3066 …
200316 18:02:30 [Note] InnoDB: Using mutexes to ref count buffer pool pages
200316 18:02:30 [Note] InnoDB: The InnoDB memory heap is disabled
200316 18:02:30 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
200316 18:02:30 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
200316 18:02:30 [Note] InnoDB: Compressed tables use zlib 1.2.7
200316 18:02:30 [Note] InnoDB: Using Linux native AIO
200316 18:02:30 [Note] InnoDB: Not using CPU crc32 instructions
200316 18:02:30 [Note] InnoDB: Initializing buffer pool, size = 1.0G
200316 18:02:30 [Note] InnoDB: Completed initialization of buffer pool
200316 18:02:30 [Note] InnoDB: Highest supported file format is Barracuda.
200316 18:02:30 [Note] InnoDB: Starting crash recovery from checkpoint LSN=113300724338
200316 18:02:35 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer…
200316 18:02:36 [ERROR] InnoDB: Tried to read 65536 bytes at offset 157976576. Was only able to read 18432.
2020-03-16 18:02:36 7fd8afbf98c0 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
200316 18:02:36 [ERROR] InnoDB: File (unknown): ‘read’ returned OS error 105. Cannot continue operation
200316 18:02:36 mysqld_safe mysqld from pid file /var/lib/mysql/minhhungtsbd.me.pid ended
200316 18:05:49 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200316 18:05:49 [Note] /usr/sbin/mysqld (mysqld 10.0.38-MariaDB) starting as process 3724 …
200316 18:05:49 [Note] InnoDB: Using mutexes to ref count buffer pool pages
200316 18:05:49 [Note] InnoDB: The InnoDB memory heap is disabled
200316 18:05:49 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
200316 18:05:49 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
200316 18:05:49 [Note] InnoDB: Compressed tables use zlib 1.2.7
200316 18:05:49 [Note] InnoDB: Using Linux native AIO
200316 18:05:49 [Note] InnoDB: Not using CPU crc32 instructions
200316 18:05:49 [Note] InnoDB: Initializing buffer pool, size = 1.0G
200316 18:05:49 [Note] InnoDB: Completed initialization of buffer pool
200316 18:05:49 [Note] InnoDB: Highest supported file format is Barracuda.
200316 18:05:49 [Note] InnoDB: Starting crash recovery from checkpoint LSN=113300724338
200316 18:05:51 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer…
200316 18:05:52 [ERROR] InnoDB: Tried to read 65536 bytes at offset 157976576. Was only able to read 18432.
2020-03-16 18:05:52 7efe1addf8c0 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
200316 18:05:52 [ERROR] InnoDB: File (unknown): ‘read’ returned OS error 105. Cannot continue operation
200316 18:05:52 mysqld_safe mysqld from pid file /var/lib/mysql/minhhungtsbd.me.pid ended
200316 18:06:21 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200316 18:06:21 [Note] /usr/sbin/mysqld (mysqld 10.0.38-MariaDB) starting as process 4355 …
200316 18:06:21 [Note] InnoDB: Using mutexes to ref count buffer pool pages
200316 18:06:21 [Note] InnoDB: The InnoDB memory heap is disabled
200316 18:06:21 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
200316 18:06:21 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
200316 18:06:21 [Note] InnoDB: Compressed tables use zlib 1.2.7
200316 18:06:21 [Note] InnoDB: Using Linux native AIO
200316 18:06:21 [Note] InnoDB: Not using CPU crc32 instructions
200316 18:06:21 [Note] InnoDB: Initializing buffer pool, size = 1.0G
200316 18:06:21 [Note] InnoDB: Completed initialization of buffer pool
200316 18:06:21 [Note] InnoDB: Highest supported file format is Barracuda.
200316 18:06:21 [Note] InnoDB: Starting crash recovery from checkpoint LSN=113300724338
200316 18:06:23 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer…
200316 18:06:24 [ERROR] InnoDB: Tried to read 65536 bytes at offset 157976576. Was only able to read 18432.
2020-03-16 18:06:24 7fe6a34bc8c0 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
200316 18:06:24 [ERROR] InnoDB: File (unknown): ‘read’ returned OS error 105. Cannot continue operation
200316 18:06:24 mysqld_safe mysqld from pid file /var/lib/mysql/minhhungtsbd.me.pid ended
200316 18:27:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200316 18:27:58 [Note] /usr/sbin/mysqld (mysqld 10.0.38-MariaDB) starting as process 2127 …
200316 18:27:58 [Note] InnoDB: Using mutexes to ref count buffer pool pages
200316 18:27:58 [Note] InnoDB: The InnoDB memory heap is disabled
200316 18:27:58 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
200316 18:27:58 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
200316 18:27:58 [Note] InnoDB: Compressed tables use zlib 1.2.7
200316 18:27:58 [Note] InnoDB: Using Linux native AIO
200316 18:27:58 [Note] InnoDB: Not using CPU crc32 instructions
200316 18:27:58 [Note] InnoDB: Initializing buffer pool, size = 1.0G
200316 18:27:58 [Note] InnoDB: Completed initialization of buffer pool
200316 18:27:58 [Note] InnoDB: Highest supported file format is Barracuda.
200316 18:27:58 [Note] InnoDB: Starting crash recovery from checkpoint LSN=113300724338
200316 18:28:00 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer…
200316 18:28:01 [ERROR] InnoDB: Tried to read 65536 bytes at offset 157976576. Was only able to read 18432.
2020-03-16 18:28:01 7f5b6590b8c0 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
200316 18:28:01 [ERROR] InnoDB: File (unknown): ‘read’ returned OS error 105. Cannot continue operation
200316 18:28:01 mysqld_safe mysqld from pid file /var/lib/mysql/minhhungtsbd.me.pid ended
200316 20:35:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200316 20:35:52 [Note] /usr/sbin/mysqld (mysqld 10.0.38-MariaDB) starting as process 2135 …
200316 20:35:52 [Note] InnoDB: Using mutexes to ref count buffer pool pages
200316 20:35:52 [Note] InnoDB: The InnoDB memory heap is disabled
200316 20:35:52 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
200316 20:35:52 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
200316 20:35:52 [Note] InnoDB: Compressed tables use zlib 1.2.7
200316 20:35:52 [Note] InnoDB: Using Linux native AIO
200316 20:35:53 [Note] InnoDB: Not using CPU crc32 instructions
200316 20:35:53 [Note] InnoDB: Initializing buffer pool, size = 1.0G
200316 20:35:53 [Note] InnoDB: Completed initialization of buffer pool
200316 20:35:53 [Note] InnoDB: Highest supported file format is Barracuda.
200316 20:35:53 [Note] InnoDB: Starting crash recovery from checkpoint LSN=113300724338
200316 20:35:59 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer…
200316 20:36:31 [Note] InnoDB: Read redo log up to LSN=113302821376
200316 20:36:32 [ERROR] InnoDB: Tried to read 65536 bytes at offset 157976576. Was only able to read 18432.
2020-03-16 20:36:32 7fe99750f8c0 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
200316 20:36:32 [ERROR] InnoDB: File (unknown): ‘read’ returned OS error 105. Cannot continue operation
200316 20:36:33 mysqld_safe mysqld from pid file /var/lib/mysql/minhhungtsbd.me.pid ended