addons: MariaDB is not starting after update to 2.7.0

Describe the issue you are experiencing

[00:31:12] INFO: Starting MariaDB
2024-04-16  0:31:12 0 [Note] Starting MariaDB 10.11.6-MariaDB source revision fecd78b83785d5ae96f2c6ff340375be803cd299 as process 13206
2024-04-16  0:31:13 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
2024-04-16  0:31:13 0 [Note] InnoDB: Number of transaction pools: 1
2024-04-16  0:31:13 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-04-16  0:31:13 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2024-04-16  0:31:13 0 [Note] InnoDB: Using Linux native AIO
2024-04-16  0:31:13 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-04-16  0:31:13 0 [Note] InnoDB: Completed initialization of buffer pool
2024-04-16  0:31:13 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-04-16  0:31:13 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.6.8. You must start up and shut down MariaDB 10.7 or earlier.
2024-04-16  0:31:13 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2024-04-16  0:31:13 0 [Note] InnoDB: Starting shutdown...
2024-04-16  0:31:14 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2024-04-16  0:31:14 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-04-16  0:31:14 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2024-04-16  0:31:14 0 [ERROR] Aborting
[00:31:14] INFO: Service mariadb exited with code 1 (by signal 0)

what should i do ?

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

MariaDB

What is the version of the add-on?

2.7.0

Steps to reproduce the issue

1.update from 2.6.1 to 2.7.0

System Health information

System Information

version core-2024.4.3
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.12.2
os_name Linux
os_version 6.6.25-haos
arch x86_64
timezone Europe/Rome
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 4885
Installed Version 1.34.0
Stage running
Available Repositories 1402
Downloaded Repositories 17
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 12.2
update_channel stable
supervisor_version supervisor-2024.04.0
agent_version 1.6.0
docker_version 25.0.5
disk_total 30.8 GB
disk_used 7.4 GB
healthy true
supported true
board ova
supervisor_api ok
version_api ok
installed_addons File editor (5.8.0), Terminal & SSH (9.13.0), Mosquitto broker (6.4.0), Zigbee2MQTT (1.36.1-1), MariaDB (2.7.0), Samba share (12.3.1), Ring-MQTT with Video Streaming (5.6.3), Studio Code Server (5.15.0), Node-RED (17.0.11)
Dashboards
dashboards 2
resources 8
views 9
mode storage
Sonoff
version 3.6.0 (8dd8af9)
cloud_online 1 / 2
local_online 1 / 1

Anything in the Supervisor logs that might be useful for us?

2024-04-15 21:26:24.079 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2024-04-15 21:56:24.573 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2024-04-15 22:19:08.481 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
2024-04-15 22:19:08.482 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
2024-04-15 22:19:08.482 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
2024-04-15 22:19:08.543 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
2024-04-15 22:19:08.544 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
2024-04-15 22:19:08.545 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
2024-04-15 22:19:08.545 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
2024-04-15 22:19:08.546 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor
2024-04-15 22:19:08.563 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
2024-04-15 22:19:08.563 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
2024-04-15 22:19:08.564 INFO (MainThread) [supervisor.resolution.check] System checks complete
2024-04-15 22:19:08.564 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2024-04-15 22:19:09.018 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2024-04-15 22:19:09.018 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
2024-04-15 22:19:09.019 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
2024-04-15 22:23:28.968 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
2024-04-15 22:24:46.515 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/tsightler/ring-mqtt-ha-addon repository
2024-04-15 22:24:46.523 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
2024-04-15 22:24:46.531 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/zigbee2mqtt/hassio-zigbee2mqtt repository
2024-04-15 22:24:46.549 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repository
2024-04-15 22:24:46.567 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
2024-04-15 22:24:50.607 INFO (MainThread) [supervisor.store] Loading add-ons from store: 81 all - 0 new - 0 remove
2024-04-15 22:24:50.608 INFO (MainThread) [supervisor.store] Loading add-ons from store: 81 all - 0 new - 0 remove
2024-04-15 22:26:25.054 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2024-04-15 22:56:25.599 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2024-04-15 23:19:09.061 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
2024-04-15 23:19:09.061 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
2024-04-15 23:19:09.061 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
2024-04-15 23:19:09.171 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
2024-04-15 23:19:09.173 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
2024-04-15 23:19:09.194 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
2024-04-15 23:19:09.214 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
2024-04-15 23:19:09.214 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor
2024-04-15 23:19:09.231 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
2024-04-15 23:19:09.232 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
2024-04-15 23:19:09.233 INFO (MainThread) [supervisor.resolution.check] System checks complete
2024-04-15 23:19:09.233 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2024-04-15 23:19:09.598 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2024-04-15 23:19:09.598 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
2024-04-15 23:19:09.599 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
2024-04-15 23:26:26.187 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2024-04-15 23:30:55.827 INFO (MainThread) [supervisor.host.info] Updating local host information
2024-04-15 23:30:57.086 INFO (MainThread) [supervisor.host.services] Updating service information
2024-04-15 23:30:57.100 INFO (MainThread) [supervisor.host.network] Updating local network information
2024-04-15 23:30:57.443 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
2024-04-15 23:30:57.459 INFO (MainThread) [supervisor.host.manager] Host information reload completed
2024-04-15 23:56:26.658 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2024-04-16 00:02:20.672 INFO (MainThread) [supervisor.backups.manager] Backup 7aa30de8 starting stage addon_repositories
2024-04-16 00:02:20.673 INFO (MainThread) [supervisor.backups.manager] Backup 7aa30de8 starting stage docker_config
2024-04-16 00:02:20.673 INFO (MainThread) [supervisor.backups.manager] Creating new partial backup with slug 7aa30de8
2024-04-16 00:02:20.688 INFO (MainThread) [supervisor.backups.manager] Backup 7aa30de8 starting stage addons
2024-04-16 00:02:27.107 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_mariadb
2024-04-16 00:02:44.512 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_mariadb
2024-04-16 00:02:47.314 INFO (MainThread) [supervisor.backups.manager] Backup 7aa30de8 starting stage finishing_file
2024-04-16 00:02:47.325 INFO (MainThread) [supervisor.backups.manager] Creating partial backup with slug 7aa30de8 completed
2024-04-16 00:02:47.330 INFO (MainThread) [supervisor.docker.addon] Updating image homeassistant/amd64-addon-mariadb:2.6.1 to homeassistant/amd64-addon-mariadb:2.7.0
2024-04-16 00:02:47.330 INFO (MainThread) [supervisor.docker.interface] Downloading docker image homeassistant/amd64-addon-mariadb with tag 2.7.0.
2024-04-16 00:03:21.486 INFO (SyncWorker_2) [supervisor.docker.manager] Stopping addon_core_mariadb application
2024-04-16 00:03:51.108 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning addon_core_mariadb application
2024-04-16 00:03:52.072 INFO (MainThread) [supervisor.addons.addon] Add-on 'core_mariadb' successfully updated
2024-04-16 00:03:53.461 INFO (SyncWorker_0) [supervisor.docker.manager] Cleanup images: ['homeassistant/amd64-addon-mariadb:2.6.1']
2024-04-16 00:04:05.052 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-mariadb with version 2.7.0
2024-04-16 00:04:05.102 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/tsightler/ring-mqtt-ha-addon repository
2024-04-16 00:04:05.162 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
2024-04-16 00:04:05.210 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/zigbee2mqtt/hassio-zigbee2mqtt repository
2024-04-16 00:04:05.263 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repository
2024-04-16 00:04:05.271 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
2024-04-16 00:04:05.440 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
2024-04-16 00:04:28.748 INFO (MainThread) [supervisor.store] Loading add-ons from store: 81 all - 0 new - 0 remove
2024-04-16 00:04:28.749 INFO (MainThread) [supervisor.store] Loading add-ons from store: 81 all - 0 new - 0 remove
2024-04-16 00:10:50.989 INFO (SyncWorker_3) [supervisor.docker.manager] Restarting homeassistant
2024-04-16 00:13:21.818 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2024-04-16 00:14:35.939 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2024-04-16 00:14:37.075 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to NOT_RUNNING
2024-04-16 00:14:37.466 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2024-04-16 00:16:14.236 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to RUNNING
2024-04-16 00:16:14.236 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
2024-04-16 00:19:09.623 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
2024-04-16 00:19:09.623 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
2024-04-16 00:19:09.623 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
2024-04-16 00:19:09.683 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
2024-04-16 00:19:09.685 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
2024-04-16 00:19:09.686 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
2024-04-16 00:19:09.686 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
2024-04-16 00:19:09.687 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor
2024-04-16 00:19:09.711 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
2024-04-16 00:19:09.711 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
2024-04-16 00:19:09.712 INFO (MainThread) [supervisor.resolution.check] System checks complete
2024-04-16 00:19:09.712 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2024-04-16 00:19:10.040 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2024-04-16 00:19:10.042 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
2024-04-16 00:19:10.042 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
2024-04-16 00:23:29.551 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
2024-04-16 00:26:27.127 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2024-04-16 00:27:28.022 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from core_ssh
2024-04-16 00:27:28.029 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from core_ssh
2024-04-16 00:27:28.035 INFO (MainThread) [supervisor.api.middleware.security] /host/info access from core_ssh
2024-04-16 00:27:28.042 INFO (MainThread) [supervisor.api.middleware.security] /core/info access from core_ssh

Anything in the add-on logs that might be useful for us?

2024-04-16  0:35:39 0 [Note] InnoDB: Completed initialization of buffer pool
2024-04-16  0:35:39 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-04-16  0:35:39 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.6.8. You must start up and shut down MariaDB 10.7 or earlier.
2024-04-16  0:35:39 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2024-04-16  0:35:39 0 [Note] InnoDB: Starting shutdown...
2024-04-16  0:35:39 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2024-04-16  0:35:39 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-04-16  0:35:39 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2024-04-16  0:35:39 0 [ERROR] Aborting
[00:35:39] INFO: Service mariadb exited with code 1 (by signal 0)
[00:35:40] INFO: Starting MariaDB
2024-04-16  0:35:40 0 [Note] Starting MariaDB 10.11.6-MariaDB source revision fecd78b83785d5ae96f2c6ff340375be803cd299 as process 15698
2024-04-16  0:35:41 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
2024-04-16  0:35:41 0 [Note] InnoDB: Number of transaction pools: 1
2024-04-16  0:35:41 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-04-16  0:35:41 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2024-04-16  0:35:41 0 [Note] InnoDB: Using Linux native AIO
2024-04-16  0:35:41 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-04-16  0:35:41 0 [Note] InnoDB: Completed initialization of buffer pool
2024-04-16  0:35:41 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-04-16  0:35:41 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.6.8. You must start up and shut down MariaDB 10.7 or earlier.
2024-04-16  0:35:41 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2024-04-16  0:35:41 0 [Note] InnoDB: Starting shutdown...
2024-04-16  0:35:41 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2024-04-16  0:35:41 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-04-16  0:35:41 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2024-04-16  0:35:41 0 [ERROR] Aborting
[00:35:41] INFO: Service mariadb exited with code 1 (by signal 0)
[00:35:43] INFO: Starting MariaDB
2024-04-16  0:35:43 0 [Note] Starting MariaDB 10.11.6-MariaDB source revision fecd78b83785d5ae96f2c6ff340375be803cd299 as process 15719
2024-04-16  0:35:43 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
2024-04-16  0:35:43 0 [Note] InnoDB: Number of transaction pools: 1
2024-04-16  0:35:43 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-04-16  0:35:43 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2024-04-16  0:35:43 0 [Note] InnoDB: Using Linux native AIO
2024-04-16  0:35:43 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-04-16  0:35:43 0 [Note] InnoDB: Completed initialization of buffer pool
2024-04-16  0:35:43 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-04-16  0:35:43 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.6.8. You must start up and shut down MariaDB 10.7 or earlier.
2024-04-16  0:35:43 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2024-04-16  0:35:43 0 [Note] InnoDB: Starting shutdown...
2024-04-16  0:35:43 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2024-04-16  0:35:43 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-04-16  0:35:43 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2024-04-16  0:35:43 0 [ERROR] Aborting
[00:35:44] INFO: Service mariadb exited with code 1 (by signal 0)
[00:35:45] INFO: Starting MariaDB
2024-04-16  0:35:45 0 [Note] Starting MariaDB 10.11.6-MariaDB source revision fecd78b83785d5ae96f2c6ff340375be803cd299 as process 15740
2024-04-16  0:35:45 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
2024-04-16  0:35:45 0 [Note] InnoDB: Number of transaction pools: 1
2024-04-16  0:35:45 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-04-16  0:35:45 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2024-04-16  0:35:45 0 [Note] InnoDB: Using Linux native AIO
2024-04-16  0:35:45 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-04-16  0:35:45 0 [Note] InnoDB: Completed initialization of buffer pool
2024-04-16  0:35:45 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-04-16  0:35:45 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.6.8. You must start up and shut down MariaDB 10.7 or earlier.
2024-04-16  0:35:45 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2024-04-16  0:35:45 0 [Note] InnoDB: Starting shutdown...
2024-04-16  0:35:45 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2024-04-16  0:35:45 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-04-16  0:35:45 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2024-04-16  0:35:45 0 [ERROR] Aborting
[00:35:46] INFO: Service mariadb exited with code 1 (by signal 0)
[00:35:47] INFO: Starting MariaDB
2024-04-16  0:35:47 0 [Note] Starting MariaDB 10.11.6-MariaDB source revision fecd78b83785d5ae96f2c6ff340375be803cd299 as process 15763
2024-04-16  0:35:47 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
2024-04-16  0:35:47 0 [Note] InnoDB: Number of transaction pools: 1
2024-04-16  0:35:47 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-04-16  0:35:47 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2024-04-16  0:35:47 0 [Note] InnoDB: Using Linux native AIO
2024-04-16  0:35:47 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-04-16  0:35:47 0 [Note] InnoDB: Completed initialization of buffer pool
2024-04-16  0:35:47 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-04-16  0:35:47 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.6.8. You must start up and shut down MariaDB 10.7 or earlier.
2024-04-16  0:35:47 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2024-04-16  0:35:47 0 [Note] InnoDB: Starting shutdown...
2024-04-16  0:35:48 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2024-04-16  0:35:48 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-04-16  0:35:48 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2024-04-16  0:35:48 0 [ERROR] Aborting
[00:35:48] INFO: Service mariadb exited with code 1 (by signal 0)
[00:35:49] INFO: Starting MariaDB
2024-04-16  0:35:49 0 [Note] Starting MariaDB 10.11.6-MariaDB source revision fecd78b83785d5ae96f2c6ff340375be803cd299 as process 15784
2024-04-16  0:35:50 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
2024-04-16  0:35:50 0 [Note] InnoDB: Number of transaction pools: 1
2024-04-16  0:35:50 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-04-16  0:35:50 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2024-04-16  0:35:50 0 [Note] InnoDB: Using Linux native AIO
2024-04-16  0:35:50 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-04-16  0:35:50 0 [Note] InnoDB: Completed initialization of buffer pool
2024-04-16  0:35:50 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-04-16  0:35:50 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.6.8. You must start up and shut down MariaDB 10.7 or earlier.
2024-04-16  0:35:50 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2024-04-16  0:35:50 0 [Note] InnoDB: Starting shutdown...
2024-04-16  0:35:50 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2024-04-16  0:35:50 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-04-16  0:35:51 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2024-04-16  0:35:51 0 [ERROR] Aborting
[00:35:52] INFO: Service mariadb exited with code 1 (by signal 0)

Additional information

No response

About this issue

  • Original URL
  • State: closed
  • Created 3 months ago
  • Reactions: 4
  • Comments: 57 (25 by maintainers)

Commits related to this issue

Most upvoted comments

I hope this is not considered spam, but I just have to say it: Although the situation is at least inconvenient, the mechanisms of Home Assistant enable us to recover rather easily and with minimal data loss for most installations, that face(d) this issue. But what I want to point out in particular, is the tremendous support of one individual here: @agners, thanks a ton! ❤️ It is people like him going out of their way to help and guide, which strengthens my belief and commitment to the open source community. Cheers mate!

Can you restore 2.6.1 again, then try the following command to stop the add-on before updating in the Advanced SSH & Web Terminal (from the community store)

docker stop --time 300 addon_core_mariadb

yes, it works, it took 42 seconds image

maybe it should be added in the supervisor that it has to wait that time only when updating. I imagine that it cannot be set as a default for things such as that the system must be able to shut down in an emergency situation such as when the power goes out and you are on UPS.

but I don’t know how it works, I just wanted to say my opinion and thank you so much for your help

Even if it works, errors have come up repeatedly, I don’t know if it helps:

2024-04-22 20:29:55 4 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-22 20:29:55 4 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
[20:29:55] INFO: MariaDB started
[20:29:56] INFO: Check data integrity and fix corruptions
[20:29:59] INFO: Ensuring internal database upgrades are performed
2024-04-22 20:29:55 4 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-22 20:29:55 4 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).

Just ran into this problem, updated from the command line, so no backup. Lost all my historical data from the past 2 years 😢

Ugh. Yeah unfortunately you can’t downgrade without having a backup.

What you could do in this case is take a backup of the upgraded/non-working state (as the data is still there, it is just the new version of MariaDB cannot recover it 😢 ), download that backup, open the tar (I think 7-Zip can do that on Windows) edit backup.json, specifically change the version field to 2.6.1 for core_mariadb. Recreate the tar, upload the backup and restore it. This then should install MariaDB 2.6.1 again which should be able to recover the issue. Then make sure it gracefully shuts down, and upgrade again.

Can someone provide the logs from the shutdown before the upgrade (see #3566 (comment)).

Just gave it a try on my test instance and do not see an issue for far on this machine (HAOS 12.2 on a Pi4) although there are some strange errors concerning incorrect definitions of table mqsql.column_stats.

Full upgrade log including stop, install, start:

s6-rc: info: service mariadb-lock-core: starting
[14:48:42] INFO: Start MariaDB client (to lock tables for backups)
s6-rc: info: service mariadb-lock-core successfully started
s6-rc: info: service mariadb-lock-post: starting
[14:48:42] INFO: MariaDB tables locked
s6-rc: info: service mariadb-lock-post successfully started
s6-rc: info: service mariadb-lock-post: stopping
[14:48:54] INFO: MariaDB tables unlocked
s6-rc: info: service mariadb-lock-post successfully stopped
s6-rc: info: service mariadb-lock-core: stopping
[14:48:54] INFO: MariaDB client (to lock tables for backups) stopped
s6-rc: info: service mariadb-lock-core successfully stopped
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service mariadb-post: stopping
[14:49:16] INFO: Deleting service information from Home Assistant

s6-rc: info: service mariadb-post successfully stopped
s6-rc: info: service mariadb-core: stopping
2024-04-16 14:49:16 0 [Note] mysqld (initiated by: unknown): Normal shutdown
2024-04-16 14:49:16 0 [Note] InnoDB: FTS optimize thread exiting.
2024-04-16 14:49:16 0 [Note] InnoDB: Starting shutdown...
2024-04-16 14:49:16 0 [Note] InnoDB: Dumping buffer pool(s) to /data/databases/ib_buffer_pool
2024-04-16 14:49:16 0 [Note] InnoDB: Restricted to 2028 pages due to innodb_buf_pool_dump_pct=25
2024-04-16 14:49:16 0 [Note] InnoDB: Buffer pool(s) dump completed at 240416 14:49:16
2024-04-16 14:49:16 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2024-04-16 14:49:16 0 [Note] InnoDB: Shutdown completed; log sequence number 129651300584; transaction id 27096757
2024-04-16 14:49:16 0 [Note] mysqld: Shutdown complete

[14:49:16] INFO: Service mariadb exited with code 0 (by signal 0)
s6-rc: info: service mariadb-core successfully stopped
s6-rc: info: service mariadb-pre: stopping
s6-rc: info: service mariadb-pre successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service mariadb-pre: starting
[14:49:23] INFO: Using existing mariadb
s6-rc: info: service mariadb-pre successfully started
s6-rc: info: service mariadb-core: starting
s6-rc: info: service mariadb-core successfully started
s6-rc: info: service mariadb-post: starting
[14:49:23] INFO: Starting MariaDB
2024-04-16 14:49:23 0 [Note] Starting MariaDB 10.11.6-MariaDB source revision fecd78b83785d5ae96f2c6ff340375be803cd299 as process 67
2024-04-16 14:49:23 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
2024-04-16 14:49:23 0 [Note] InnoDB: Number of transaction pools: 1
2024-04-16 14:49:23 0 [Note] InnoDB: Using ARMv8 crc32 instructions
2024-04-16 14:49:23 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2024-04-16 14:49:23 0 [Note] InnoDB: Using Linux native AIO
2024-04-16 14:49:23 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-04-16 14:49:23 0 [Note] InnoDB: Completed initialization of buffer pool
2024-04-16 14:49:23 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-04-16 14:49:23 0 [Note] InnoDB: Upgrading redo log: 48.000MiB; LSN=129651300584
2024-04-16 14:49:23 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-04-16 14:49:24 0 [Note] InnoDB: 128 rollback segments are active.
2024-04-16 14:49:24 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2024-04-16 14:49:24 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2024-04-16 14:49:24 0 [Note] InnoDB: log sequence number 129651300584; transaction id 27096758
2024-04-16 14:49:24 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-04-16 14:49:24 0 [Note] InnoDB: Loading buffer pool(s) from /data/databases/ib_buffer_pool
2024-04-16 14:49:24 0 [Note] Server socket created on IP: '0.0.0.0'.
2024-04-16 14:49:24 0 [Note] Server socket created on IP: '::'.
2024-04-16 14:49:24 0 [Note] mysqld: ready for connections.
Version: '10.11.6-MariaDB'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Alpine Linux
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 0 [Note] InnoDB: Buffer pool(s) load completed at 240416 14:49:24
[14:49:24] INFO: MariaDB started
2024-04-16 14:49:24 5 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 5 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 5 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 5 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2024-04-16 14:49:24 5 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2024-04-16 14:49:24 5 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
[14:49:24] INFO: Check data integrity and fix corruptions
mysql.column_stats                                 OK
mysql.columns_priv                                 OK
mysql.db                                           OK
mysql.event                                        OK
mysql.func                                         OK
mysql.global_priv                                  OK
mysql.gtid_slave_pos                               OK
mysql.help_category                                OK
mysql.help_keyword                                 OK
mysql.help_relation                                OK
mysql.help_topic                                   OK
mysql.index_stats                                  OK
mysql.innodb_index_stats                           OK
mysql.innodb_table_stats                           OK
mysql.plugin                                       OK
mysql.proc                                         OK
mysql.procs_priv                                   OK
mysql.proxies_priv                                 OK
mysql.roles_mapping                                OK
mysql.servers                                      OK
mysql.table_stats                                  OK
mysql.tables_priv                                  OK
mysql.time_zone                                    OK
mysql.time_zone_leap_second                        OK
mysql.time_zone_name                               OK
mysql.time_zone_transition                         OK
mysql.time_zone_transition_type                    OK
mysql.transaction_registry                         OK
homeassistant.event_data                           OK
homeassistant.event_types                          OK
homeassistant.events                               OK
homeassistant.migration_changes                    OK
homeassistant.recorder_runs                        OK
homeassistant.schema_changes                       OK
homeassistant.state_attributes                     OK
homeassistant.states                               OK
homeassistant.states_meta                          OK
homeassistant.statistics                           OK
homeassistant.statistics_meta                      OK
homeassistant.statistics_runs                      OK
homeassistant.statistics_short_term                OK
nginxproxymanager.access_list                      OK
nginxproxymanager.access_list_auth                 OK
nginxproxymanager.access_list_client               OK
nginxproxymanager.audit_log                        OK
nginxproxymanager.auth                             OK
nginxproxymanager.certificate                      OK
nginxproxymanager.dead_host                        OK
nginxproxymanager.migrations                       OK
nginxproxymanager.migrations_lock                  OK
nginxproxymanager.proxy_host                       OK
nginxproxymanager.redirection_host                 OK
nginxproxymanager.setting                          OK
nginxproxymanager.stream                           OK
nginxproxymanager.user                             OK
nginxproxymanager.user_permission                  OK
phpmyadmin.pma__bookmark                           OK
phpmyadmin.pma__central_columns                    OK
phpmyadmin.pma__column_info                        OK
phpmyadmin.pma__designer_settings                  OK
phpmyadmin.pma__export_templates                   OK
phpmyadmin.pma__favorite                           OK
phpmyadmin.pma__history                            OK
phpmyadmin.pma__navigationhiding                   OK
phpmyadmin.pma__pdf_pages                          OK
phpmyadmin.pma__recent                             OK
phpmyadmin.pma__relation                           OK
phpmyadmin.pma__savedsearches                      OK
phpmyadmin.pma__table_coords                       OK
phpmyadmin.pma__table_info                         OK
phpmyadmin.pma__table_uiprefs                      OK
phpmyadmin.pma__tracking                           OK
phpmyadmin.pma__userconfig                         OK
phpmyadmin.pma__usergroups                         OK
phpmyadmin.pma__users                              OK
sys.sys_config                                     OK
[14:49:25] INFO: Ensuring internal database upgrades are performed
[14:49:30] INFO: Ensure databases exists
[14:49:30] INFO: Create database homeassistant
[14:49:30] INFO: Ensure users exists and are updated
[14:49:30] INFO: Update user hassio
[14:49:30] INFO: Init/Update rights
[14:49:30] INFO: Granting all privileges to hassio on homeassistant
[14:49:30] INFO: Sending service information to Home Assistant

s6-rc: info: service mariadb-post successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started

@guice what you can do (but it is a hack) just download the other version and tag it as the latest:

docker pull homeassistant/aarch64-addon-mariadb:2.6.1
docker tag homeassistant/aarch64-addon-mariadb:2.6.1 homeassistant/aarch64-addon-mariadb:2.7.1

Then restart the add-on via UI. Then try stopping it, and check for successful stop in the logs.

Don’t forget to restore the original container image after 2.6.1 startup/stop succeeded.

docker pull homeassistant/aarch64-addon-mariadb:2.6.1

Then restart the container. Note this is a hack, and only really works as long as there is no incompatible config change (which is the case between these two versions).

Even if it works, errors have come up repeatedly

If you restart the 2.7.1 version, these errors should disappear: during first startup after the upgrade, mariadb has issues with these statistics data (20:29:55 4 [ERROR]), but a few seconds later a script runs that updates these schema ([20:29:59] INFO: Ensuring internal database upgrades are performed).

Can you restore 2.6.1 again, then try the following command to stop the add-on before updating in the Advanced SSH & Web Terminal (from the community store)

docker stop --time 300 addon_core_mariadb

Thank you for this quick answer! I’ll try it!

@cortado your case looks a bit different:

2024-04-17 8:27:02 0 [ERROR] InnoDB: The Auto-extending data file './ibdata1' is of a different size 0 pages than specified by innodb_data_file_path

Maybe still try restore the old version and upgrade again, it might be shutdown related to. If the problem persists, please open a new issue.

After having the problem described here, I had success by restoring 2.6.1, stopping the add-on, doing the update to 2.7, and then starting the add-on.

For me, a graceful shutdown looks like this:

s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service mariadb-post: stopping
[09:29:05] INFO: Deleting service information from Home Assistant

s6-rc: info: service mariadb-post successfully stopped
s6-rc: info: service mariadb-core: stopping
2024-04-16  9:29:05 0 [Note] mysqld (initiated by: unknown): Normal shutdown
2024-04-16  9:29:05 0 [Note] InnoDB: FTS optimize thread exiting.
2024-04-16  9:29:05 0 [Note] InnoDB: Starting shutdown...
2024-04-16  9:29:05 0 [Note] InnoDB: Dumping buffer pool(s) to /data/databases/ib_buffer_pool
2024-04-16  9:29:05 0 [Note] InnoDB: Restricted to 2016 pages due to innodb_buf_pool_dump_pct=25
2024-04-16  9:29:05 0 [Note] InnoDB: Buffer pool(s) dump completed at 240416  9:29:05
2024-04-16  9:29:05 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2024-04-16  9:29:05 0 [Note] InnoDB: Shutdown completed; log sequence number 738796972612; transaction id 141268245
2024-04-16  9:29:05 0 [Note] mysqld: Shutdown complete
[09:29:06] INFO: Service mariadb exited with code 0 (by signal 0)
s6-rc: info: service mariadb-core successfully stopped
s6-rc: info: service mariadb-pre: stopping
s6-rc: info: service mariadb-pre successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

now I rolled back to 2.6.1 should I stop the MariaDB addon first and then do the update to 2.7.0 ?

Ok, reading this again, the problem seems to be the add-on shutdown before the upgrade was not graceful in your case:

2024-04-16 5:20:32 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.6.8. You must start up and shut down MariaDB 10.7 or earlier.

Maybe just downgrading and upgrading again helps?

If not (or in any case), you can use ha host logs to get the logs of previous add-on runs. It would be interesting to see the logs of the shutdown before the first (failed) startup attempt:

ha host logs --identifier addon_core_mariadb -n 10000