2

I am unable to find MariaDB version 10.4.13 using brew. After reinstalling by uninstalling and installing (critical mistake) Homebrew upgraded my version to 10.5.5

Now I am getting the following error:

020-08-14 20:33:07 0 [Note] InnoDB: Uses event mutexes

2020-08-14 20:33:07 0 [Note] InnoDB: Compressed tables use zlib 1.2.11

2020-08-14 20:33:07 0 [Note] InnoDB: Number of pools: 1

2020-08-14 20:33:07 0 [Note] InnoDB: Using SSE4.2 crc32 instructions

2020-08-14 20:33:07 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728

2020-08-14 20:33:07 0 [Note] InnoDB: Completed initialization of buffer pool

2020-08-14 20:33:07 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.13.

2020-08-14 20:33:07 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error

2020-08-14 20:33:07 0 [Note] InnoDB: Starting shutdown...

2020-08-14 20:33:07 0 [ERROR] Plugin 'InnoDB' init function returned error.

2020-08-14 20:33:07 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2020-08-14 20:33:07 0 [Note] Plugin 'FEEDBACK' is disabled.

2020-08-14 20:33:07 0 [ERROR] Unknown/unsupported storage engine: InnoDB

2020-08-14 20:33:07 0 [ERROR] Aborting

Any help would be greatly appreciated. I have still have my datadir somewhere outside of the /var/log/mysql.

Obi-Wan-Clemobi
  • 145
  • 1
  • 13

1 Answers1

5

The only way I found round this was to backup my /var/lib/mysql and /var/lib/mariadb directories by renaming them, then creating them as empty directories. I'm aware this isn't an option for many, if you're still in development and working on seed data this should work for you.

There has been some talk about just removing log files from these directories and thus preserving data though I haven't tried this.

Log files reportedly removed that fixed this issue:

/var/lib/mysqld/ib_logfile0
/var/lib/mysql/ib_logfile1
/var/lib/mysql/aria_log_control

referenced from https://github.com/laradock/laradock/issues/93

spike 王建
  • 1,556
  • 5
  • 14
  • Thanks Spikie. Unfortunately the damage has already been done and that's not an option for me, but I appreciate your time. – Obi-Wan-Clemobi Aug 17 '20 at 15:36
  • 1
    Thanks — this worked for me. Not sure what happened but possibly the redo logs were damaged after an upgrade to 10.5.5 or incompatible. After deleting the redo logs, mariadb started successfully. This was on my development environment, so it wasn't a problem. So far it looks like it has recovered perfectly fine. – Erfan Aug 26 '20 at 03:32
  • I ended up resorting to Time Machine to restore my previous installation. Since this solution worked for you, I'll accept the answer. – Obi-Wan-Clemobi Aug 28 '20 at 16:13
  • 2
    The directory with the lof-iles on macos Big Sur/mariadb when installed using homebrew are located here: `/usr/local/var/mysql` – Roland Nov 30 '20 at 14:47
  • 1
    +1 for just deleting log files - for me using mariadb on MacOS Big Sur, just deleting /usr/local/var/mysql/ib_logfile* fixed the problem for me. – jackocnr Jan 04 '21 at 17:23