20th December 2016, 12:07
The only error message I see here that indicates what is going on that the MySQL Server is not running or cannot be connected to. (it doesn't matter if mariadb or mysql)
The problem is that we don't know why that happens as there is nothing in the logs about it.
What you could try to test is moving the database files somewhere else (rename it) and start with a fresh new one. If that works then we know that there is something wrong with the database itself.
If the fsck (yes that can run for several hours depending on the size of the db) fails on that database it is so corrupt that it cannot be restored or repaired.
The problem is that we don't know why that happens as there is nothing in the logs about it.
What you could try to test is moving the database files somewhere else (rename it) and start with a fresh new one. If that works then we know that there is something wrong with the database itself.
If the fsck (yes that can run for several hours depending on the size of the db) fails on that database it is so corrupt that it cannot be restored or repaired.