The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-16. For the latest, interactive version please visit https://mariadb.com/kb/.

InnoDB: Upgrade after a crash is not supported…

Upgrade MariaDB 10.4.24 to 10.11.2, XAMPP, Windows 10 Old MariaDB is in directory oldmysql First Second: Maria DB respectively MySQL is starting in XAMPP Control Panel. Second Second: MySQL Shutdown Unexpectedly mysql_error.log: ] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.8. You must start up and shut down MariaDB 10.4 or earlier.

redo log = file ib_logfile0 10.4.8 is mentioned in file ib_logfile0. (Why not 10.4.24? Anyway!) a) If I change the name of ib_logfile0 or I move file ib_logfile0 to another directory: Message: ib_logfile0 was not found b) If ib_logfile0 is empty: Message: ib_logfile0 is too small c) When I changed in file „ib_logfile0“ 10.4.8 to 10.11.2: Message: No valid checkpoint was found or Invalid log header checksum

d) Execution of mariadb-upgrade-service did not prevent message: InnoDB: Upgrade after a crash is not supported…

You must start up and shut down MariaDB 10.4 or earlier. When I turn off the PC, Maria DB is shutted down?

What I have to do that MariaDB does not refer in a second step to 10.4.8?

Answer Answered by Daniel Black in this comment.

Follow the instructions of "You must start up and shut down MariaDB 10.4 or earlier".

So uninstall 10.11.2. Install any 10.4 version. Start up 10.4. Shutdown (cleanly).

And then upgrade to 10.11.2.

Stop playing with ib_logfile0. Leave it alone or you'll loose data.

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.