MariaDB Errors When Restarting

Recently moved servers, the previous server had MariaDB 10.1 installed while the new server had 10.2. Everything was okay until I restored a backup from the old server, and I got errors which I tried to fix, but I believe I have just made things worse. Now the problem is that we have gone live and I cannot restart MySQL because of the following errors (see attached file). I contacted my hosting company and they have suggested that save my databases, and uninstall MariaDB and reinstall it again, as they believe that this will fix the issue. However, I am unsure how to do this or will I just make things worse :( Any help would be appreciated, cheers. 2018-05-26 5:04:43 139904388753600 [ERROR] mysqld: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds 2018-05-26 5:05:14 139904388753600 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/var/lib/mysql/aria_log_control' 2018-05-26 5:05:14 139904388753600 [ERROR] Plugin 'Aria' init function returned error. 2018-05-26 5:05:14 139904388753600 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. 2018-05-26 5:05:14 139904388753600 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-05-26 5:05:14 139904388753600 [Note] InnoDB: Uses event mutexes 2018-05-26 5:05:14 139904388753600 [Note] InnoDB: Compressed tables use zlib 1.2.7 2018-05-26 5:05:14 139904388753600 [Note] InnoDB: Using Linux native AIO 2018-05-26 5:05:14 139904388753600 [Note] InnoDB: Number of pools: 1 2018-05-26 5:05:14 139904388753600 [Note] InnoDB: Using generic crc32 instructions 2018-05-26 5:05:15 139904388753600 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2018-05-26 5:05:15 139904388753600 [Note] InnoDB: Completed initialization of buffer pool 2018-05-26 5:05:15 139903830591232 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-05-26 5:05:15 139904388753600 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 2018-05-26 5:05:15 139904388753600 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2018-05-26 5:05:15 139904388753600 [Note] InnoDB: Retrying to lock the first data file 2018-05-26 5:05:16 139904388753600 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 - Snipped - 2018-05-26 5:06:52 139904388753600 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2018-05-26 5:06:53 139904388753600 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 2018-05-26 5:06:53 139904388753600 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2018-05-26 5:06:54 139904388753600 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 2018-05-26 5:06:54 139904388753600 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2018-05-26 5:06:55 139904388753600 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 2018-05-26 5:06:55 139904388753600 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2018-05-26 5:06:55 139904388753600 [Note] InnoDB: Unable to open the first data file 2018-05-26 5:06:55 139904388753600 [ERROR] InnoDB: Operating system error number 11 in a file operation. 2018-05-26 5:06:55 139904388753600 [ERROR] InnoDB: Error number 11 means 'Resource temporarily unavailable' 2018-05-26 5:06:55 139904388753600 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2018-05-26 5:06:55 139904388753600 [ERROR] InnoDB: Cannot open datafile './ibdata1' 2018-05-26 5:06:55 139904388753600 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data! 2018-05-26 5:06:55 139904388753600 [ERROR] InnoDB: Plugin initialization aborted with error Cannot open a file 2018-05-26 5:06:55 139904388753600 [Note] InnoDB: Starting shutdown... 2018-05-26 5:06:55 139904388753600 [ERROR] Plugin 'InnoDB' init function returned error. 2018-05-26 5:06:55 139904388753600 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2018-05-26 5:06:55 139904388753600 [Note] Plugin 'FEEDBACK' is disabled. 2018-05-26 5:06:55 139904388753600 [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as mysqld was configured with --with-aria-tmp-tables 2018-05-26 5:06:55 139904388753600 [ERROR] Aborting