- Remove innodb_force_recovery from the config - Downgrade back to 10.4.11 - start mariadb service - set global innodb_fast_shutdown = 0 - stop mariadb service - upgrade to the version you want to run - start mariadb servce
and it will work. There can be changes to the innodb redo log on-disk format, which is why you can only upgrade after an extra-clean shutdown. On Tue, 17 Feb 2026 at 16:59, Andrew Weaver via discuss <[email protected]> wrote: > > Hello, > > I am trying to migrate some databases from version 10.4.11 to 10.5.29 > > So on the source server I simply: > > 1) shut down the mariadb service on the source, copied/zipped the data > directory, transferred the data directory to the new server. > > 2) chown -R mysql:mysql /var/lib/mysql;systemctl start mariadb > > In the log it says this: > > 2026-02-17 9:48:32 0 [ERROR] InnoDB: corrupted TRX_ID 62f900540078f866 > 2026-02-17 9:48:32 0 [Note] InnoDB: Retry with innodb_force_recovery=5 > 2026-02-17 9:48:32 0 [ERROR] InnoDB: Plugin initialization aborted with > error Data structure corruption > 2026-02-17 9:48:32 0 [Note] InnoDB: Starting shutdown... > 2026-02-17 9:48:32 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE > ENGINE failed. > 2026-02-17 9:48:32 0 [Note] Plugin 'FEEDBACK' is disabled. > 2026-02-17 9:48:32 0 [ERROR] Unknown/unsupported storage engine: InnoDB > > I put this: innodb_force_recovery=5 into /etc/my.cnf.d/mariadb-server.cnf and > restarted the server (per the log above) > > and then after trying to restart mariadb the log now says this: > > 2026-02-17 9:51:50 0 [ERROR] InnoDB: Upgrade after a crash is not supported. > The redo log was created with MariaDB 10.4.11. You must start up and shut > down MariaDB 10.4 or earlier on the data directory. > 2026-02-17 9:51:50 0 [ERROR] InnoDB: Plugin initialization aborted with > error Generic error > 2026-02-17 9:51:50 0 [Note] InnoDB: Starting shutdown... > 2026-02-17 9:51:50 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE > ENGINE failed. > 2026-02-17 9:51:50 0 [Note] Plugin 'FEEDBACK' is disabled. > 2026-02-17 9:51:50 0 [ERROR] Unknown/unsupported storage engine: InnoDB > 2026-02-17 9:51:50 0 [ERROR] Aborting > > This seems to be a loop that I cannot get out of no matter how hard I try. > > The source server didn't crash prior to me copying the data from it so I am > unsure as to why it's saying "Upgrade after a crash is not supported". > > The source server is running and is replicating to several replicants. > > thanks, > > -Drew > > > > > > _______________________________________________ > discuss mailing list -- [email protected] > To unsubscribe send an email to [email protected] -- Gordan Bobic Database Specialist, Shattered Silicon Ltd. https://shatteredsilicon.net Follow us: LinkedIn: https://www.linkedin.com/company/shatteredsilicon X: https://x.com/ssiliconbg _______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
