Após a duplicação da unidade com falha, o mysql e o mariadb se recusam a executar

Question

Eu tinha um disco rígido que estava falhando e clonei o disco para manter meu servidor em execução. Eu notei que o mysql não rodava e tentei limpar o mysql, tentei instalar o mariadb, tentei limpá-lo e reinstalá-lo várias vezes. Parece que o mysql / mariadb está instalado bem, mas agora continuo recebendo esta falha:

Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.
invoke-rc.d: initscript mysql, action "start" failed.
● mariadb.service - MariaDB 10.2.14 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/mariadb.service.d
           └─migrated-from-my.cnf-settings.conf
   Active: failed (Result: exit-code) since Fri 2018-04-13 09:12:43 MDT; 10ms ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 22033 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
  Process: 21876 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR='/usr/bin/galera_recovery'; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
  Process: 21870 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 21865 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
 Main PID: 22033 (code=exited, status=1/FAILURE)
   Status: "MariaDB server is down"

Apr 13 09:12:41 SSDUbuntuServer mysqld[22033]: 2018-04-13  9:12:41 140424825977024 [Note] Plugin 'FEEDBACK' is disabled.
Apr 13 09:12:41 SSDUbuntuServer mysqld[22033]: 2018-04-13  9:12:41 140424825977024 [ERROR] mysqld: File '/var/log/mysql/mariadb-bin.000008' not found (Errcode: 2 "No ...directory")
Apr 13 09:12:41 SSDUbuntuServer mysqld[22033]: 2018-04-13  9:12:41 140424825977024 [ERROR] Failed to open log (file '/var/log/mysql/mariadb-bin.000008', errno 2)
Apr 13 09:12:41 SSDUbuntuServer mysqld[22033]: 2018-04-13  9:12:41 140424825977024 [ERROR] Could not open log file
Apr 13 09:12:41 SSDUbuntuServer mysqld[22033]: 2018-04-13  9:12:41 140424825977024 [ERROR] Can't init tc log
Apr 13 09:12:41 SSDUbuntuServer mysqld[22033]: 2018-04-13  9:12:41 140424825977024 [ERROR] Aborting
Apr 13 09:12:43 SSDUbuntuServer systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Apr 13 09:12:43 SSDUbuntuServer systemd[1]: Failed to start MariaDB 10.2.14 database server.
Apr 13 09:12:43 SSDUbuntuServer systemd[1]: mariadb.service: Unit entered failed state.
Apr 13 09:12:43 SSDUbuntuServer systemd[1]: mariadb.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package mariadb-server-10.2 (--configure):
 subprocess installed post-installation script returned error exit status 1

Adoraria colocar meu banco de dados em funcionamento novamente, mas não consigo descobrir por que ele não será iniciado. Eu purgou e reinstalei o mysql e o maria várias vezes, e ambos deram o mesmo erro.

Obrigado!

editar

Depois de dar acesso de gravação aos diretórios de log acima, recebo

Apr 13 11:06:02 SSDUbuntuServer mysqld[8060]: 2018-04-13 11:06:02 140331412616960 [Note] InnoDB: FTS optimize thread exiting.
Apr 13 11:06:02 SSDUbuntuServer mysqld[8060]: 2018-04-13 11:06:02 140332290479872 [Note] Event Scheduler: Purging the queue. 0 events
Apr 13 11:06:02 SSDUbuntuServer mysqld[8060]: 2018-04-13 11:06:02 140332290479872 [Note] InnoDB: Starting shutdown...
Apr 13 11:06:02 SSDUbuntuServer mysqld[8060]: 2018-04-13 11:06:02 140331370653440 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
Apr 13 11:06:02 SSDUbuntuServer mysqld[8060]: 2018-04-13 11:06:02 140331370653440 [Note] InnoDB: Buffer pool(s) dump completed at 180413 11:06:02
Apr 13 11:06:03 SSDUbuntuServer mysqld[8060]: 2018-04-13 11:06:03 140332290479872 [Note] InnoDB: Shutdown completed; log sequence number 1620101
Apr 13 11:06:03 SSDUbuntuServer mysqld[8060]: 2018-04-13 11:06:03 140332290479872 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"

    

Answer 1

Após mais pesquisas, descobri que /etc/mysql/debian-start estava faltando e causando as falhas. Eu criei o arquivo e preenchai seu conteúdo com esta versão do mariadb e tudo funcionou.

    

Answer 2

Como foi a configuração de suas unidades antes da clonagem? as linhas

Apr 13 09:12:41 SSDUbuntuServer mysqld[22033]: 2018-04-13  9:12:41 140424825977024 [Note] Plugin 'FEEDBACK' is disabled.
Apr 13 09:12:41 SSDUbuntuServer mysqld[22033]: 2018-04-13  9:12:41 140424825977024 [ERROR] mysqld: File '/var/log/mysql/mariadb-bin.000008' not found (Errcode: 2 "No ...directory")
Apr 13 09:12:41 SSDUbuntuServer mysqld[22033]: 2018-04-13  9:12:41 140424825977024 [ERROR] Failed to open log (file '/var/log/mysql/mariadb-bin.000008', errno 2)
Apr 13 09:12:41 SSDUbuntuServer mysqld[22033]: 2018-04-13  9:12:41 140424825977024 [ERROR] Could not open log file
Apr 13 09:12:41 SSDUbuntuServer mysqld[22033]: 2018-04-13  9:12:41 140424825977024 [ERROR] Can't init tc log

Indica que o processo não está localizando o diretório log ou não tem permissões para acessar o que já está lá. Tente listar o diretório /var/log/mysql/ primeiro para ver se há algo lá.