{"id":2909,"date":"2018-09-11T12:25:09","date_gmt":"2018-09-11T12:25:09","guid":{"rendered":"https:\/\/iserversupport.com\/?p=2909"},"modified":"2022-03-09T09:35:04","modified_gmt":"2022-03-09T09:35:04","slug":"recover-crashed-innodb-tables-on-mysql-database-server","status":"publish","type":"post","link":"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/","title":{"rendered":"Recover crashed Innodb tables on MySQL database server."},"content":{"rendered":"<h1>Recover Crashed innodb tables<\/h1>\n<p>&nbsp;<\/p>\n<p><span style=\"color: #ff0000;\"><strong>Lost valuable database ? Hire us we will recover it for you<\/strong><\/span> <a href=\"https:\/\/iserversupport.com\/proactive-server-management\/\">Server Management plan<\/a><\/p>\n<p>Recover crashed Innodb tables process will help you to recover any critical tables during innodb crash. One of the dangerous issue you will face on a MySQL server is innodb crash, no matter how important the data is and what tweaks you have on the database server crash can happen sometimes. So you need to\u00a0Recover crashed Innodb tables if you don&#8217;t have a recent backup. It can happen on cPanel server, Plesk server, Directadmin server, Percona server, Madiarb server.<\/p>\n<div id=\"attachment_2918\" style=\"width: 1020px\" class=\"wp-caption alignnone\"><img decoding=\"async\" aria-describedby=\"caption-attachment-2918\" class=\"size-full wp-image-2918\" src=\"https:\/\/iserversupport.com\/wp-content\/uploads\/2018\/09\/Screen-Shot-2018-09-11-at-4.51.20-PM.png\" alt=\"mysql crashed innodb recovery process\" width=\"1010\" height=\"392\" srcset=\"https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/Screen-Shot-2018-09-11-at-4.51.20-PM-200x78.png 200w, https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/Screen-Shot-2018-09-11-at-4.51.20-PM-300x116.png 300w, https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/Screen-Shot-2018-09-11-at-4.51.20-PM-400x155.png 400w, https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/Screen-Shot-2018-09-11-at-4.51.20-PM-600x233.png 600w, https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/Screen-Shot-2018-09-11-at-4.51.20-PM-768x298.png 768w, https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/Screen-Shot-2018-09-11-at-4.51.20-PM-800x310.png 800w, https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/Screen-Shot-2018-09-11-at-4.51.20-PM.png 1010w\" sizes=\"(max-width: 1010px) 100vw, 1010px\" \/><p id=\"caption-attachment-2918\" class=\"wp-caption-text\">mysql crashed innodb recovery process<\/p><\/div>\n<h2>How\u00a0Innodb crash can happen ?<\/h2>\n<ul>\n<li>Innodb table can crash if there is powerlose for your dedicated server.<\/li>\n<li>Force shutdown of MySQL service can end up in Innodb crash.<\/li>\n<li>Space issue on the serve can case Innodb crash, if the server space is 100% filled and mysql not able to write on the disk.<\/li>\n<li>High load on the server can cause Innodb crash.<\/li>\n<li>High I\/O wait on the disk can also cause MySQL innodb crash.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h3>How to determine if innodb is crashed.?<\/h3>\n<p>You can determine this by checking MySQL logs, On most of the server location of the Log is\u00a0\/var\/lib\/mysql\/server.hostname.com.err sometimes it can also found under \/var\/lib\/mysql\/mysql.log this can be changed under \/etc\/my.cnf file.<\/p>\n<p>You can see logs like below if the table is Innodb table is crashed. refer <a href=\"https:\/\/dev.mysql.com\/doc\/refman\/5.5\/en\/innodb-recovery.html\">InnoDB recovery<\/a><\/p>\n<pre>The manual page at http:\/\/dev.mysql.com\/doc\/mysql\/en\/crashing.html contains\r\ninformation that should help you find out what is causing the crash.\r\n180406 13:45:02 [Note] Plugin 'FEDERATED' is disabled.\r\n180406 13:45:02 InnoDB: The InnoDB memory heap is disabled\r\n180406 13:45:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins\r\n180406 13:45:02 InnoDB: Compressed tables use zlib 1.2.3\r\n180406 13:45:02 InnoDB: Using Linux native AIO\r\n180406 13:45:02 InnoDB: Initializing buffer pool, size = 128.0M\r\n180406 13:45:02 InnoDB: Completed initialization of buffer pool\r\n180406 13:45:02 InnoDB: highest supported file format is Barracuda.\r\nInnoDB: Log scan progressed past the checkpoint lsn 16040747881\r\n180406 13:45:02 InnoDB: Database was not shut down normally!\r\nInnoDB: Starting crash recovery.\r\nInnoDB: Reading tablespace information from the .ibd files...\r\nInnoDB: Restoring possible half-written data pages from the doublewrite\r\nInnoDB: buffer...\r\nInnoDB: Doing recovery: scanned up to log sequence number 16040751132\r\n180406 13:45:02 InnoDB: Starting an apply batch of log records to the database...\r\nInnoDB: 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\r\nInnoDB: Apply batch completed\r\n180406 13:45:03 InnoDB: Waiting for the background threads to start\r\n180406 13:45:04 InnoDB: 5.5.58 started; log sequence number 16040751132<\/pre>\n<p>&nbsp;<\/p>\n<pre>Version: '5.5.58-cll' socket: '\/var\/lib\/mysql\/mysql.sock' port: 3306 MySQL Community Server (GPL)\r\n180406 13:48:06 InnoDB: Assertion failure in thread 140428055471872 in file fut0lst.ic line 83\r\nInnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset &gt;= FIL_PAGE_DATA\r\nInnoDB: We intentionally generate a memory trap.\r\nInnoDB: Submit a detailed bug report to http:\/\/bugs.mysql.com.\r\nInnoDB: If you get repeated assertion failures or crashes, even\r\nInnoDB: immediately after the mysqld startup, there may be\r\nInnoDB: corruption in the InnoDB tablespace. Please refer to\r\nInnoDB: http:\/\/dev.mysql.com\/doc\/refman\/5.5\/en\/forcing-innodb-recovery.html\r\nInnoDB: about forcing recovery.\r\n18:48:06 UTC - mysqld got signal 6 ;\r\nThis could be because you hit a bug. It is also possible that this binary\r\nor one of the libraries it was linked against is corrupt, improperly built,\r\nor misconfigured. This error can also be caused by malfunctioning hardware.\r\nWe will try our best to scrape up some info that will hopefully help\r\ndiagnose the problem, but since we have already crashed,\r\nsomething is definitely wrong and this may fail.<\/pre>\n<p>&nbsp;<\/p>\n<p>Mostly you will face the issue on cPanel MySQL server 5.X<\/p>\n<h3>Recover crashed Innodb tables on MySQL<\/h3>\n<p>First think you need to do to recover the database is to stop mysql using<\/p>\n<pre>\/etc\/init.d\/mysql stop<\/pre>\n<p>And make sure there are no running process of MySql you can check this using the command<\/p>\n<pre>ps -aux | grep mysql<\/pre>\n<p>If there are any running process kill the process id using the command kill -9 pid and take backup of Crashed MySQL database. If it is a cPanel server first make sure to disable MySQL monitoring from\u00a0 cPanel\/WHM\u00a0Home \u00bbService Configuration \u00bbService Manager to avoid automatic restart.<\/p>\n<p>Backup \/var\/lib\/mysql using below command<\/p>\n<pre>cp -rf \/var\/lib\/mysql\u00a0\u00a0\/var\/lib\/mysql_backup_data<\/pre>\n<p>It is important to take backup of the data folder because if something fail during recovery you can restore\u00a0\/var\/lib\/mysql\u00a0 and start the process again.<\/p>\n<p>Once this is the done next step is to start the actual recovery process. You can do this by adding the parameter\u00a0innodb_force_recovery, the value of the parameter is from 1 to 6, if you can recover the database using\u00a0innodb_force_recovery value 1 you don&#8217;t lose any data and the condition of data will be very good. In any minor crash you can recover it using the value\u00a0innodb_force_recovery = 1. If the intensity of the crash is high you might have to increase the valye up to 6 and the possibility of datalose is high.<\/p>\n<p>So now we will try <a href=\"https:\/\/dev.mysql.com\/doc\/refman\/8.0\/en\/forcing-innodb-recovery.html\">Forcing InnoDB Recovery<\/a> first step is to add<\/p>\n<pre>innodb_force_recovery = 1<\/pre>\n<p>In the file<\/p>\n<pre>\/etc\/my.cnf<\/pre>\n<p>And try to start MySql using the following command<\/p>\n<pre>\/etc\/init.d\/mysql start<\/pre>\n<p>If the issue is fixed MySQL will start with the message &#8220;Starting successful&#8221; or else you will get some error message like below.<\/p>\n<pre>Starting MySQL.\/usr\/bin\/mysqld_safe: line 182: 2208 Killed nohup \/usr\/sbin\/mysqld --basedir=\/usr --datadir=\/var\/lib\/mysql --plugin-dir=\/usr\/lib64\/mysql\/plugin --user=mysql --log-error=dasc-server.hosting.com.err --open-files-limit=10000 --pid-file=\/var\/lib\/mysql\/dasc-server.hosting.com.pid &lt; \/dev\/null &gt; \/dev\/null 2&gt;&amp;1\r\nERROR! The server quit without updating PID file (\/var\/lib\/mysql\/dasc-server.server.com.pid).<\/pre>\n<p>In that case try below value until MySQL starts<\/p>\n<pre>innodb_force_recovery = 2<\/pre>\n<pre>innodb_force_recovery = 3<\/pre>\n<pre>innodb_force_recovery = 4<\/pre>\n<pre>innodb_force_recovery = 5<\/pre>\n<pre>innodb_force_recovery = 6<\/pre>\n<p>Sometimes MySQL wont start even with the value 6 so you need to check the log file again which is under \/var\/lib\/mysql\/server.server.com.err<\/p>\n<p>You might notice the error.<\/p>\n<pre>InnoDB: Waiting for the background threads to start<\/pre>\n<p>This can be fixed by adding the line<\/p>\n<pre>innodb_purge_threads=0<\/pre>\n<p>With the\u00a0innodb_force_recovery 6 value.<\/p>\n<p>So once MySQL is started in recovery mode we need to take backup of all the crashed databases and restore it with new\u00a0ibdata1, ib_logfile0, ib_logfile1 files.<\/p>\n<p>Next step is to create the database list into a file which can be done using the command.<\/p>\n<pre class=\"p1\">\u00a0mysql -e 'show databases;' |\u00a0grep -v information_schema | grep -v Database\u00a0 &gt;\u00a0\/home\/mysql_innodb_recovery\/database_list.txt<\/pre>\n<p>Once this is done take backup of each Individual databases including the database called &#8220;mysql&#8221; which is very important. You can take backup using below command.<\/p>\n<pre class=\"p1\">for db in 'cat \/home\/mysql_innodb_recovery\/database_list.txt'; do mysqldump $i &gt; \/home\/mysql_innodb_recovery\/database_backup\/$db.sql;done<\/pre>\n<p>Now we need to drop current databases to make sure that they are removed from MySQL and innodb which can be done using the command. Make sure to remove the database name &#8220;mysql&#8221; from the file\u00a0\/home\/mysql_innodb_recovery\/database_list.txt before doing this.<\/p>\n<pre>for db in 'cat \/home\/mysql_innodb_recovery\/database_list.txt'; do mysqladmin drop $db;done<\/pre>\n<p>Some database won&#8217;t get dropped which can be directly removed using the rm -rf command<\/p>\n<pre>cd \/var\/lib\/mysql\r\n\r\nrm -rf database_name<\/pre>\n<p>Now move ib files to a new location and we force MySQL to create a new ibdata files.<\/p>\n<pre>mv \/var\/lib\/mysql\/ibdata1\u00a0\/home\/mysql_innodb_recovery\/\r\n\r\nmv \/var\/lib\/mysql\/ib_logfile0\u00a0\/home\/mysql_innodb_recovery\/\r\n\r\nmv \/var\/lib\/mysql\/ib_logfile1\u00a0\/home\/mysql_innodb_recovery\/<\/pre>\n<p>Remove below values from \/etc\/my.cnf and start mysql<\/p>\n<pre>innodb_force_recovery = 1\r\ninnodb_purge_threads = 0<\/pre>\n<p>Start MySQL<\/p>\n<pre>\/etc\/init.d\/mysql start<\/pre>\n<p>Once the MySQL service is started create all the database with the similar command we have used to drop database.<\/p>\n<pre>for db in 'cat \/home\/mysql_innodb_recovery\/database_list.txt'; do mysqladmin create $db;done<\/pre>\n<p>Now we will restore the backups we have taken.<\/p>\n<pre>for db in 'cat \/home\/mysql_innodb_recovery\/database_list.txt'; do mysqldump $db &lt; \/home\/mysql_innodb_recovery\/database_backup\/$db.sql;done<\/pre>\n<p>Here we have completed the Innodb table repair process. Have a look at the log file\u00a0\/var\/lib\/mysql\/server.server.com.err and make sure the repair process is successful.<\/p>\n<p>Repair crashed innodb tables.<\/p>\n<p>Sometimes tables will be marked as crashed this can be fixed quickly using the below command.<\/p>\n<pre>mysqlcheck -r -A<\/pre>\n<p>or<\/p>\n<pre>mysqlcheck --repair --all-databases<\/pre>\n<p>The above command will repair all the databases on the server. If there is only one database marked as crashed this can be fixed by running the command<\/p>\n<p>mysqlcheck &#8211;repair DATABASE_NAME<\/p>\n<p>Once everything is recovered you can test if the MySQL is up by simply running the command mysql from console.<\/p>\n<div id=\"attachment_2917\" style=\"width: 626px\" class=\"wp-caption alignnone\"><img decoding=\"async\" aria-describedby=\"caption-attachment-2917\" class=\"size-full wp-image-2917\" src=\"https:\/\/iserversupport.com\/wp-content\/uploads\/2018\/09\/Screen-Shot-2018-09-11-at-4.48.22-PM.png\" alt=\"Recover crashed Innodb tables\" width=\"616\" height=\"226\" srcset=\"https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/Screen-Shot-2018-09-11-at-4.48.22-PM-200x73.png 200w, https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/Screen-Shot-2018-09-11-at-4.48.22-PM-300x110.png 300w, https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/Screen-Shot-2018-09-11-at-4.48.22-PM-400x147.png 400w, https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/Screen-Shot-2018-09-11-at-4.48.22-PM-600x220.png 600w, https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/Screen-Shot-2018-09-11-at-4.48.22-PM.png 616w\" sizes=\"(max-width: 616px) 100vw, 616px\" \/><p id=\"caption-attachment-2917\" class=\"wp-caption-text\">Recovered crashed innodb mysql service<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Recover Crashed innodb tables &nbsp; Lost valuable database ? Hire us we will recover it for you Server Management plan Recover crashed Innodb tables process will help you to recover [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":21955,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v22.6 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Recover crashed Innodb tables on MySQL database server.<\/title>\n<meta name=\"description\" content=\"Recover crashed Innodb tables and databased without any data lose. The process include repairing databases recover as much data as possible from the crash\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Recover crashed Innodb tables on MySQL database server.\" \/>\n<meta property=\"og:description\" content=\"Recover crashed Innodb tables and databased without any data lose. The process include repairing databases recover as much data as possible from the crash\" \/>\n<meta property=\"og:url\" content=\"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/\" \/>\n<meta property=\"og:site_name\" content=\"Server Management Company - Outsourced Webhosting Service\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/facebook.com\/iserversupport\" \/>\n<meta property=\"article:published_time\" content=\"2018-09-11T12:25:09+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-03-09T09:35:04+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/mysql-19-1174939-e1605888188793.png\" \/>\n\t<meta property=\"og:image:width\" content=\"225\" \/>\n\t<meta property=\"og:image:height\" content=\"225\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"iServerSupport\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@iserversupport\" \/>\n<meta name=\"twitter:site\" content=\"@iserversupport\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"iServerSupport\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/\"},\"author\":{\"name\":\"iServerSupport\",\"@id\":\"https:\/\/iserversupport.com\/blog\/#\/schema\/person\/414757a5feb39cada3a64aece076ce39\"},\"headline\":\"Recover crashed Innodb tables on MySQL database server.\",\"datePublished\":\"2018-09-11T12:25:09+00:00\",\"dateModified\":\"2022-03-09T09:35:04+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/\"},\"wordCount\":904,\"commentCount\":1,\"publisher\":{\"@id\":\"https:\/\/iserversupport.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/mysql-19-1174939-e1605888188793.png\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/\",\"url\":\"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/\",\"name\":\"Recover crashed Innodb tables on MySQL database server.\",\"isPartOf\":{\"@id\":\"https:\/\/iserversupport.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/mysql-19-1174939-e1605888188793.png\",\"datePublished\":\"2018-09-11T12:25:09+00:00\",\"dateModified\":\"2022-03-09T09:35:04+00:00\",\"description\":\"Recover crashed Innodb tables and databased without any data lose. The process include repairing databases recover as much data as possible from the crash\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/#primaryimage\",\"url\":\"https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/mysql-19-1174939-e1605888188793.png\",\"contentUrl\":\"https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/mysql-19-1174939-e1605888188793.png\",\"width\":225,\"height\":225,\"caption\":\"Sever Management Services\"},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/iserversupport.com\/blog\/#website\",\"url\":\"https:\/\/iserversupport.com\/blog\/\",\"name\":\"Server Management Company - Outsourced Webhosting Service\",\"description\":\"Complete server management service\",\"publisher\":{\"@id\":\"https:\/\/iserversupport.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/iserversupport.com\/blog\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/iserversupport.com\/blog\/#organization\",\"name\":\"iServerSupport\",\"url\":\"https:\/\/iserversupport.com\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/iserversupport.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/iserversupport.com\/wp-content\/uploads\/2020\/09\/I-SERVER-SUPPORT-07-1-e1606382474222.png\",\"contentUrl\":\"https:\/\/iserversupport.com\/wp-content\/uploads\/2020\/09\/I-SERVER-SUPPORT-07-1-e1606382474222.png\",\"width\":20,\"height\":19,\"caption\":\"iServerSupport\"},\"image\":{\"@id\":\"https:\/\/iserversupport.com\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/facebook.com\/iserversupport\",\"https:\/\/x.com\/iserversupport\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/iserversupport.com\/blog\/#\/schema\/person\/414757a5feb39cada3a64aece076ce39\",\"name\":\"iServerSupport\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/iserversupport.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/ab568d65092a1e7994bb3aa6f4a4a1ba?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/ab568d65092a1e7994bb3aa6f4a4a1ba?s=96&d=mm&r=g\",\"caption\":\"iServerSupport\"},\"sameAs\":[\"https:\/\/iserversupport.com\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Recover crashed Innodb tables on MySQL database server.","description":"Recover crashed Innodb tables and databased without any data lose. The process include repairing databases recover as much data as possible from the crash","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/","og_locale":"en_US","og_type":"article","og_title":"Recover crashed Innodb tables on MySQL database server.","og_description":"Recover crashed Innodb tables and databased without any data lose. The process include repairing databases recover as much data as possible from the crash","og_url":"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/","og_site_name":"Server Management Company - Outsourced Webhosting Service","article_publisher":"https:\/\/facebook.com\/iserversupport","article_published_time":"2018-09-11T12:25:09+00:00","article_modified_time":"2022-03-09T09:35:04+00:00","og_image":[{"width":225,"height":225,"url":"https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/mysql-19-1174939-e1605888188793.png","type":"image\/png"}],"author":"iServerSupport","twitter_card":"summary_large_image","twitter_creator":"@iserversupport","twitter_site":"@iserversupport","twitter_misc":{"Written by":"iServerSupport","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/#article","isPartOf":{"@id":"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/"},"author":{"name":"iServerSupport","@id":"https:\/\/iserversupport.com\/blog\/#\/schema\/person\/414757a5feb39cada3a64aece076ce39"},"headline":"Recover crashed Innodb tables on MySQL database server.","datePublished":"2018-09-11T12:25:09+00:00","dateModified":"2022-03-09T09:35:04+00:00","mainEntityOfPage":{"@id":"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/"},"wordCount":904,"commentCount":1,"publisher":{"@id":"https:\/\/iserversupport.com\/blog\/#organization"},"image":{"@id":"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/#primaryimage"},"thumbnailUrl":"https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/mysql-19-1174939-e1605888188793.png","inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/","url":"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/","name":"Recover crashed Innodb tables on MySQL database server.","isPartOf":{"@id":"https:\/\/iserversupport.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/#primaryimage"},"image":{"@id":"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/#primaryimage"},"thumbnailUrl":"https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/mysql-19-1174939-e1605888188793.png","datePublished":"2018-09-11T12:25:09+00:00","dateModified":"2022-03-09T09:35:04+00:00","description":"Recover crashed Innodb tables and databased without any data lose. The process include repairing databases recover as much data as possible from the crash","inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/iserversupport.com\/blog\/recover-crashed-innodb-tables-on-mysql-database-server\/#primaryimage","url":"https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/mysql-19-1174939-e1605888188793.png","contentUrl":"https:\/\/iserversupport.com\/blog\/wp-content\/uploads\/2018\/09\/mysql-19-1174939-e1605888188793.png","width":225,"height":225,"caption":"Sever Management Services"},{"@type":"WebSite","@id":"https:\/\/iserversupport.com\/blog\/#website","url":"https:\/\/iserversupport.com\/blog\/","name":"Server Management Company - Outsourced Webhosting Service","description":"Complete server management service","publisher":{"@id":"https:\/\/iserversupport.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/iserversupport.com\/blog\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/iserversupport.com\/blog\/#organization","name":"iServerSupport","url":"https:\/\/iserversupport.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/iserversupport.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/iserversupport.com\/wp-content\/uploads\/2020\/09\/I-SERVER-SUPPORT-07-1-e1606382474222.png","contentUrl":"https:\/\/iserversupport.com\/wp-content\/uploads\/2020\/09\/I-SERVER-SUPPORT-07-1-e1606382474222.png","width":20,"height":19,"caption":"iServerSupport"},"image":{"@id":"https:\/\/iserversupport.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/facebook.com\/iserversupport","https:\/\/x.com\/iserversupport"]},{"@type":"Person","@id":"https:\/\/iserversupport.com\/blog\/#\/schema\/person\/414757a5feb39cada3a64aece076ce39","name":"iServerSupport","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/iserversupport.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/ab568d65092a1e7994bb3aa6f4a4a1ba?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ab568d65092a1e7994bb3aa6f4a4a1ba?s=96&d=mm&r=g","caption":"iServerSupport"},"sameAs":["https:\/\/iserversupport.com"]}]}},"_links":{"self":[{"href":"https:\/\/iserversupport.com\/blog\/wp-json\/wp\/v2\/posts\/2909"}],"collection":[{"href":"https:\/\/iserversupport.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/iserversupport.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/iserversupport.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/iserversupport.com\/blog\/wp-json\/wp\/v2\/comments?post=2909"}],"version-history":[{"count":0,"href":"https:\/\/iserversupport.com\/blog\/wp-json\/wp\/v2\/posts\/2909\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/iserversupport.com\/blog\/wp-json\/wp\/v2\/media\/21955"}],"wp:attachment":[{"href":"https:\/\/iserversupport.com\/blog\/wp-json\/wp\/v2\/media?parent=2909"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/iserversupport.com\/blog\/wp-json\/wp\/v2\/categories?post=2909"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/iserversupport.com\/blog\/wp-json\/wp\/v2\/tags?post=2909"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}