MariaDB does not start after upgrading to version 2.7

I have HAOS installed in a RPI4 to the latest version of all components and now I upgraded from Mariadb version 2.6.1 to Mariadb version 2.7 and after restarting the database does not start giving these errors

2024-04-17 17:29:11 0 [Note] Starting MariaDB 10.11.6-MariaDB source revision fecd78b83785d5ae96f2c6ff340375be803cd299 as process 2847
2024-04-17 17:29:12 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
2024-04-17 17:29:12 0 [Note] InnoDB: Number of transaction pools: 1
2024-04-17 17:29:12 0 [Note] InnoDB: Using ARMv8 crc32 instructions
2024-04-17 17:29:12 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2024-04-17 17:29:12 0 [Note] InnoDB: Using Linux native AIO
2024-04-17 17:29:12 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-04-17 17:29:12 0 [Note] InnoDB: Completed initialization of buffer pool
2024-04-17 17:29:12 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-04-17 17:29:12 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.6.12. You must start up and shut down MariaDB 10.7 or earlier.
2024-04-17 17:29:12 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2024-04-17 17:29:12 0 [Note] InnoDB: Starting shutdown...

Has the same thing happened to anyone? Is there a solution without having to dump the backup prior to installing the upgrade?


1 Like

Same exact thing happened to me just now.
Will let you know if I figure out how to un-bjork

Same for me, too.

Rolling Back to previous version and restarting Home Assistant worked.

By rolling back do you mean restoring the backup made before the upgrade or is there an automatic way to revert to the previous version? So far I have not had to undo an upgrade of an addon and I would not like to lose the database by doing it wrong.

Yes, you’re right: I restored the backup that was made during the upgrade to version 2.7

The database ist stored at that time so your db ist reset to that point in time (which ist ok since mariadb was not working after the failed upgrade anyways).

There ist also a discussion on GitHub which helped me to finally Upgrade to 2.7:

In a nutshell: after going back to v2.6.1 stop the addon, start the upgrade to v2.7 manually and then start the addon again (and then maybe restart home assistant).

1 Like