Also:
Just for "fun" I upgraded to 10.4.34 from 10.4.11 which was the final
version of 10.4 just to see what would happen:
Feb 17 11:36:24 localhost systemd[1]: Starting MariaDB 10.4.34 database
server...
Feb 17 11:36:24 localhost mysqld[991572]: 2026-02-17 11:36:24 0 [Note]
Starting MariaDB 10.4.34-MariaDB source revision
16394f1aa1b4097f897b8ab01ea2064726cca059 as process 991572
Feb 17 11:36:24 localhost mysqld[991572]: 2026-02-17 11:36:24 0 [Note]
InnoDB: Using Linux native AIO
Feb 17 11:36:24 localhost mysqld[991572]: 2026-02-17 11:36:24 0 [Note]
InnoDB: Mutexes and rw_locks use GCC atomic builtins
Feb 17 11:36:24 localhost mysqld[991572]: 2026-02-17 11:36:24 0 [Note]
InnoDB: Uses event mutexes
Feb 17 11:36:24 localhost mysqld[991572]: 2026-02-17 11:36:24 0 [Note]
InnoDB: Compressed tables use zlib 1.2.11
Feb 17 11:36:24 localhost mysqld[991572]: 2026-02-17 11:36:24 0 [Note]
InnoDB: Number of pools: 1
Feb 17 11:36:24 localhost mysqld[991572]: 2026-02-17 11:36:24 0 [Note]
InnoDB: Using SSE2 crc32 instructions
Feb 17 11:36:24 localhost mysqld[991572]: 2026-02-17 11:36:24 0 [Note]
InnoDB: Initializing buffer pool, total size = 128M, instances = 1,
chunk size = 128M
Feb 17 11:36:24 localhost mysqld[991572]: 2026-02-17 11:36:24 0 [Note]
InnoDB: Completed initialization of buffer pool
Feb 17 11:36:24 localhost mysqld[991572]: 2026-02-17 11:36:24 0 [Note]
InnoDB: If the mysqld execution user is authorized, page cleaner thread
priority can be changed. See the man page of setpriority().
Feb 17 11:36:24 localhost mysqld[991572]: 2026-02-17 11:36:24 0 [ERROR]
InnoDB: corrupted TRX_NO 62f900540078f867
I cannot for the life of me figure out why every other version aside for
10.4.11 thinks there is corruption in this database.
thank you,
-Drew
On 2026-02-17 11:32, Andrew Weaver via discuss wrote:
Hi,
The configuration file location between 10.4 and 10.5 differs and I
didn't edit the default repo configuration file while using 10.4.11 so
I don't believe that I had force-recovery enabled still while in
10.4.11.
Does it matter that the source operating system is 64 bit Windows for
these files that I gathered using mariabackup?
Does windows use a different replay log format or something?
Here is the entire log entry while 10.4.11 was running:
Feb 17 10:58:08 localhost systemd[1]: Starting MariaDB 10.4.11 database
server...
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
/usr/sbin/mysqld (mysqld 10.4.11-MariaDB) starting as process 990898
...
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: Using Linux native AIO
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: Mutexes and rw_locks use GCC atomic builtins
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: Uses event mutexes
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: Compressed tables use zlib 1.2.11
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: Number of pools: 1
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: Using SSE2 crc32 instructions
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: Initializing buffer pool, total size = 128M, instances = 1,
chunk size = 128M
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: Completed initialization of buffer pool
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: If the mysqld execution user is authorized, page cleaner thread
priority can be changed. See the man page of setpriority().
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: 128 out of 128 rollback segments are active.
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: Creating shared tablespace for temporary tables
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the
file full; Please wait ...
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: File './ibtmp1' size is now 12 MB.
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: 10.4.11 started; log sequence number 587827221; transaction id
7131731845703072051
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
Plugin 'FEEDBACK' is disabled.
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
Server socket created on IP: '::'.
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
Reading of all Master_info entries succeeded
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
Added new Master_info '' to hash table
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
/usr/sbin/mysqld: ready for connections.
Feb 17 10:58:08 localhost mysqld[990898]: Version: '10.4.11-MariaDB'
socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
Feb 17 10:58:08 localhost systemd[1]: Started MariaDB 10.4.11 database
server.
Feb 17 10:58:08 localhost mysqld[990898]: 2026-02-17 10:58:08 0 [Note]
InnoDB: Buffer pool(s) load completed at 260217 10:58:08
On 2026-02-17 11:23, Gordan Bobic via discuss wrote:
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?
_______________________________________________
discuss mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
discuss mailing list -- [email protected]
To unsubscribe send an email to [email protected]
