Fix MySQL on WHM / cPanel Server

I am having issues restarting the MySQL on a server. This is what panel wrote me below. I need the mysql fixed and need to be able to use InnoDB. 150310 16:46:18 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 371445860714 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1 row operations to undo InnoDB: Trx id counter is A793C00 150310 16:46:19 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Starting in background the rollback of uncommitted transactions 150310 16:46:19 InnoDB: Rolling back trx with id A793A4B, 1 rows to undo 150310 16:46:19 InnoDB: Waiting for the background threads to start 150310 16:46:19 InnoDB: Assertion failure in thread 47920511842624 in file [login to view URL] line 83 InnoDB: Failing assertion: [login to view URL] == FIL_NULL || [login to view URL] >= FIL_PAGE_DATA InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. 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: [login to view URL] InnoDB: about forcing recovery. 21:46:19 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. key_buffer_size=8388608 read_buffer_size=131072 max_used_connections=0 max_threads=125 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 281667 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 terribly wrong... stack_bottom = 0 thread_stack 0x3e800 /usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7e4ae5] /usr/sbin/mysqld(handle_fatal_signal+0x3e1)[0x69afe1] /lib64/libpthread.so.0[0x3a3080eca0] /lib64/libc.so.6(gsignal+0x35)[0x3a3002ffc5] /lib64/libc.so.6(abort+0x110)[0x3a30031a70] /usr/sbin/mysqld[0x8f73b0] /usr/sbin/mysqld[0x874ca0] /usr/sbin/mysqld[0x88aa43] /usr/sbin/mysqld[0x8856bd] /usr/sbin/mysqld[0x87c37e] /usr/sbin/mysqld[0x93cec3] /usr/sbin/mysqld[0x93d01b] /usr/sbin/mysqld[0x87e8c9] /usr/sbin/mysqld[0x87eef9] /lib64/libpthread.so.0[0x3a3080683d] /lib64/libc.so.6(clone+0x6d)[0x3a300d4fcd] The manual page at [login to view URL] contains information that should help you find out what is causing the crash. 150310 16:46:19 mysqld_safe mysqld from pid file /var/lib/mysql/[login to view URL] ended At this point to get your system online we can either set MySQL to start without InnoDB or you may try working with a MySQL Database Administrator to recover InnoDB on the system or restore any backups of databases you have to get it back up and running. If you'd like me to try to get MySQL online sans InnoDB just let me know.