MariaDB 10.0.x Fail to Start
200601 12:48:16 [Note] InnoDB: Using mutexes to ref count buffer pool pages
200601 12:48:16 [Note] InnoDB: The InnoDB memory heap is disabled
200601 12:48:16 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
200601 12:48:16 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
200601 12:48:16 [Note] InnoDB: Compressed tables use zlib 1.2.3
200601 12:48:16 [Note] InnoDB: Using Linux native AIO
200601 12:48:16 [Note] InnoDB: Using CPU crc32 instructions
200601 12:48:16 [Note] InnoDB: Initializing buffer pool, size = 128.0M
200601 12:48:16 [Note] InnoDB: Completed initialization of buffer pool
200601 12:48:16 [Note] InnoDB: Highest supported file format is Barracuda.
200601 12:48:16 [Note] InnoDB: The log sequence numbers 1272857294665 and 1272857294665 in ibdata files do not match the log sequence number 1272857294860 in the ib_logfiles!
200601 12:48:19 [ERROR] InnoDB: Tried to read 16384 bytes at offset 0. Was only able to read 0.
2020-06-01 12:48:19 2ae72bf9bf00 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
200601 12:48:19 [ERROR] InnoDB: File (unknown): 'read' returned OS error 71. Cannot continue operation
Getting this error suddenly but we didn't made any changes on the Mysql conf file how to fix this
-
What is after: 200601 12:48:19 [ERROR] InnoDB: File (unknown): 'read' returned OS error 71. Cannot continue operation
I assume you're getting this from the error log? Ultimately though, this is something that you or your database administrator will need to fix, but we can certainly try advising you on how to correct this yourself with some guidance if you'd like. You may want to increment "innodb_force_recovery" from 1 to 2 (if you're unable to start MySQL) and so on in the server's MySQL configuration at /etc/my.cnf, restarting MySQL each step along the way in an effort to repair the corruption InnoDB is encountering when it starts up. If you are familiar with the Linux command line, the following guide is quite helpful and extremely detailed for database restoration and repairing InnoDB:0 -
What is after:
200601 12:48:19 [ERROR] InnoDB: File (unknown): 'read' returned OS error 71. Cannot continue operation
I assume you're getting this from the error log? Ultimately though, this is something that you or your database administrator will need to fix, but we can certainly try advising you on how to correct this yourself with some guidance if you'd like. You may want to increment "innodb_force_recovery" from 1 to 2 (if you're unable to start MySQL) and so on in the server's MySQL configuration at /etc/my.cnf, restarting MySQL each step along the way in an effort to repair the corruption InnoDB is encountering when it starts up. If you are familiar with the Linux command line, the following guide is quite helpful and extremely detailed for database restoration and repairing InnoDB:
I tried to start with Recovery mode 1 or 2 but still it was giving the same error.It was starting only in Mode 6 What is the solution ?0 -
I'd suggest reading through the guide provided or contacting a qualified system administrator as noted previously. 0 -
I'd suggest reading through the guide provided or contacting a qualified system administrator as noted previously.
I had read it,But could you please help me with command on how to reinstall the MariaDB ?0 -
I cannot do this for you. This isn't the recommended path either. You need to contact a system administrator. 0
Please sign in to leave a comment.
Comments
5 comments