On Tue, 17 Feb 2026 at 17:56, Andrew Weaver <[email protected]> wrote: > > Alright so I was able to get a little further (thank you so much): > > Server version: 10.4.11-MariaDB MariaDB Server > ... > MariaDB [(none)]> set global innodb_fast_shutdown = 0; > Query OK, 0 rows affected (0.000 sec) > MariaDB [(none)]> quit > Bye > [yum.repos.d]# systemctl stop mariadb > > I then uninstalled 10.4.11, put the repos back to the default and installed > 10.5.29-3 from RHEL9 distribution. > > When I started mariadb it says this: > > 2026-02-17 10:48:42 0 [ERROR] InnoDB: corrupted TRX_ID 62f900540078f866 > 2026-02-17 10:48:42 0 [Note] InnoDB: Retry with innodb_force_recovery=5 > 2026-02-17 10:48:42 0 [ERROR] InnoDB: Plugin initialization aborted with > error Data structure corruption > 2026-02-17 10:48:42 0 [Note] InnoDB: Starting shutdown... > 2026-02-17 10:48:42 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE > ENGINE failed. > 2026-02-17 10:48:42 0 [Note] Plugin 'FEEDBACK' is disabled. > 2026-02-17 10:48:42 0 [ERROR] Unknown/unsupported storage engine: InnoDB > > Anything else needed to check in 10.4.11 land prior to upgrading?
So you got it working with 10.4, without force-recovery, did a full clean shutdown, and 10.5 still choked on the redo log?? The only thing I can think of is that you started 10.4 with force-recovery still on so it came up read-only and did nothing on shutdown to purge the redo log. Anything interesting in the log during 10.4 startup? -- 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]
