New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Unless you have your ib logfiles, you're basically fucked.
i still have those ib_logfile0, ib_logfile1, and ibdata1.
https://docs.oracle.com/cd/E17952_01/mysql-5.0-en/innodb-backup.html
systemctl restart mariadb.service
Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.
Nov 09 14:44:49 namhuy mysqld[18126]: 2017-11-09 14:44:49 140360283191552 [ERROR] Plugin 'InnoDB' init function returned error.
Nov 09 14:44:49 namhuy mysqld[18126]: 2017-11-09 14:44:49 140360283191552 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Nov 09 14:44:49 namhuy mysqld[18126]: 2017-11-09 14:44:49 140360283191552 [Note] Plugin 'FEEDBACK' is disabled.
Nov 09 14:44:49 namhuy mysqld[18126]: 2017-11-09 14:44:49 140360283191552 [ERROR] Unknown/unsupported storage engine: InnoDB
Nov 09 14:44:49 namhuy mysqld[18126]: 2017-11-09 14:44:49 140360283191552 [ERROR] Aborting
Nov 09 14:44:54 namhuy mysqld[18126]: Error in my_thread_global_end(): 1 threads didn't exit
Nov 09 14:44:54 namhuy systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Nov 09 14:44:54 namhuy systemd[1]: Failed to start MariaDB database server.
Nov 09 14:44:54 namhuy systemd[1]: Unit mariadb.service entered failed state.
Nov 09 14:44:54 namhuy systemd[1]: mariadb.service failed.
perhaps you need to set proper ownership on the files?
[ERROR] Unknown/unsupported storage engine: InnoDB
Not that i have the slightest clue but i'd read that as innodb support being disabled?
set error_logs and tune a little more specifically. You may have to move your ib_* files out of the way and manually build/rebuild stuff.
this is what i need help on. i don't know how.
I've only had to deal with that twice, but they were MyISAM based, so it was significantly easier. Move the ib_logfiles out of the way after turning MySQL off, and set "innodb_force_recovery=9" in your my.cnf, and restart the service. Then dig deeper.