Just tried this and received the following error?
Originally Posted by cPanelTristan
^[[A^[[AFailed to locate MySQL socket. Please check the mysql configuration.
-- Startup Output --
Starting MySQL... ERROR! The server quit without updating PID file (/var/lib/mysql/servername.pid).
131128 01:24:29 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
131128 1:24:29 [Note] libgovernor.so found
131128 1:24:29 [Note] All governors functions found too
131128 1:24:29 [ERROR] Governor not connected
131128 1:24:29 [Note] All governors lve functions found too
131128 1:24:29 [Note] Plugin 'FEDERATED' is disabled.
131128 1:24:29 InnoDB: The InnoDB memory heap is disabled
131128 1:24:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131128 1:24:29 InnoDB: Compressed tables use zlib 1.2.3
131128 1:24:29 InnoDB: Using Linux native AIO
131128 1:24:29 InnoDB: Initializing buffer pool, size = 128.0M
131128 1:24:29 InnoDB: Completed initialization of buffer pool
131128 1:24:29 InnoDB: highest supported file format is Barracuda.
131128 1:24:30 InnoDB: Waiting for the background threads to start
InnoDB: Error: trying to access page number 1551 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
131128 1:24:31 InnoDB: Assertion failure in thread 140042440066816 in file fil0fil.c line 4579
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to MySQL Bugs.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: MySQL :: MySQL 5.5 Reference Manual :: 18.104.22.168 Starting InnoDB on a Corrupted Database
InnoDB: about forcing recovery.
23:24:31 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338543 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
stack_bottom = 0 thread_stack 0x40000
The manual page at MySQL :: MySQL 5.6 Reference Manual :: C.5.4.2 What to Do If MySQL Keeps Crashing contains
information that should help you find out what is causing the crash.
131128 01:24:31 mysqld_safe mysqld from pid file /var/lib/mysql/servername.pid ended
-- End Startup Output --
I did create a new mount point and type mount -a.
Then copied the files and fixed permissions as they were on root:root after copying across from mysql.backup to new mysql folder.
Then tested and it kept failing. Tried renaming my.cnf to old and still the same aswell.