Unknown storage engine 'InnoDB' error: Corrupt

morteza3245

Well-Known Member
Sep 16, 2013
154
1
68
cPanel Access Level
Root Administrator
hello
when i repair a database, i receive this error: Unknown storage engine 'InnoDB' error: Corrupt
screenshot: image.prntscr.com/image/6sF0b0RLSoSsLZ2pUjY5og.png

then, i trying fix using this tutorial: InnoDB Corruption Repair Guide

and i trying run this command:
Code:
CREATE TABLE mod_joomlabridge_clients_recovered LIKE mod_joomlabridge_clients;
it show me this error: ERROR 1286 (42000): Unknown storage engine 'InnoDB'
screenshot: image.prntscr.com/image/-6l0EJN1QRS6tlQj3UP1Bw.png

what should i do?
i loss my data? or it is just file system of databases?

please help me.

thanks.
 
Last edited by a moderator:

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,904
2,218
463
Hello,

Do you notice any output to the MySQL error log on this system (/var/lib/mysql/$hostnam.err) when restarting MySQL?

Thank you.
 

morteza3245

Well-Known Member
Sep 16, 2013
154
1
68
cPanel Access Level
Root Administrator
this is the result:

Code:
2017-09-21 23:07:41 28052 [Note] /usr/sbin/mysqld: Normal shutdown

2017-09-21 23:07:41 28052 [Note] Giving 1 client threads a chance to die gracefully
2017-09-21 23:07:41 28052 [Note] Event Scheduler: Purging the queue. 0 events
2017-09-21 23:07:41 28052 [Note] Shutting down slave threads
2017-09-21 23:07:43 28052 [Note] Forcefully disconnecting 0 remaining clients
2017-09-21 23:07:43 28052 [Note] Binlog end
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'partition'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_METRICS'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_CMPMEM'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_CMP'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_LOCKS'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'INNODB_TRX'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'BLACKHOLE'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'ARCHIVE'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'MRG_MYISAM'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'MyISAM'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'MEMORY'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'CSV'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'sha256_password'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'mysql_old_password'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'mysql_native_password'
2017-09-21 23:07:43 28052 [Note] Shutting down plugin 'binlog'
2017-09-21 23:07:43 28052 [Note] /usr/sbin/mysqld: Shutdown complete

170921 23:07:43 mysqld_safe mysqld from pid file /var/lib/mysql/host.domain.com.pid ended
170921 23:07:44 mysqld_safe Logging to '/var/lib/mysql/host.domain.com.err'.
170921 23:07:44 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
170921 23:07:44 mysqld_safe Logging to '/var/lib/mysql/host.domain.com.err'.
170921 23:07:44 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2017-09-21 23:07:44 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-09-21 23:07:44 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2017-09-21 23:07:44 0 [Note] /usr/sbin/mysqld (mysqld 5.6.37) starting as process 23063 ...
2017-09-21 23:07:44 23063 [Note] Plugin 'FEDERATED' is disabled.
2017-09-21 23:07:44 23063 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-09-21 23:07:44 23063 [Note] InnoDB: The InnoDB memory heap is disabled
2017-09-21 23:07:44 23063 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-09-21 23:07:44 23063 [Note] InnoDB: Memory barrier is not used
2017-09-21 23:07:44 23063 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-09-21 23:07:44 23063 [Note] InnoDB: Using Linux native AIO
2017-09-21 23:07:44 23063 [Note] InnoDB: Using CPU crc32 instructions
2017-09-21 23:07:44 23063 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-09-21 23:07:44 23063 [Note] InnoDB: Completed initialization of buffer pool
2017-09-21 23:07:44 23063 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 0 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-$
2017-09-21 23:07:44 23063 [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_f$
2017-09-21 23:07:44 23063 [ERROR] Plugin 'InnoDB' init function returned error.
2017-09-21 23:07:44 23063 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-09-21 23:07:44 23063 [Note] Server hostname (bind-address): '*'; port: 3306
2017-09-21 23:07:44 23063 [Note] IPv6 is available.
2017-09-21 23:07:44 23063 [Note]   - '::' resolves to '::';
2017-09-21 23:07:44 23063 [Note] Server socket created on IP: '::'.
2017-09-21 23:07:44 23063 [Note] Event Scheduler: Loaded 0 events
2017-09-21 23:07:44 23063 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.37'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)
 

morteza3245

Well-Known Member
Sep 16, 2013
154
1
68
cPanel Access Level
Root Administrator
and in phpmyadmin i see below error also:
image.prntscr.com/image/6B5YOdelRJOPRmaGYNE4RQ.png

and a curropted table is this permission and space, its okay?: below screenshot:
image.prntscr.com/image/rLxDLXHFRTOmFYkWJC07uw.png

my my.conf config is below:

Code:
[mysqld]
default-storage-engine=MyISAM
innodb_force_recovery=1
innodb_file_per_table=1
performance-schema=0
max_allowed_packet=268435456
local-infile=0
#skip-innodb
default_storage_engine=MYISAM
default_tmp_storage_engine=MYISAM
innodb_force_recovery = 1
 
Last edited by a moderator:

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,904
2,218
463
Hello,

You are still using InnoDB recovery entries in your /etc/my.cnf file:

innodb_force_recovery=1
You will need to remove that entry and restart MySQL if you'd like InnoDB to function. However, note that it's possible InnoDB is still corrupted. If the guide linked in your original post doesn't help with the repair, then it's sometimes useful to consult with a qualified system administrator for further assistance as InnoDB corruption is outside our scope of support. We provide a list of system administration services at:

System Administration Services | cPanel Forums

Thank you.