Hi Andrew! If you have experience with podman (or docker), you can do your testing/repairs with containers which is probably easier than uninstall/reinstall MariaDB with dnf.
Examples (same with docker): | ❯ podman run -v data_dir:/mnt/datadir -it mariadb:10.4.11 bash | Resolving "mariadb" using unqualified-search registries (/etc/containers/registries.conf) | Trying to pull docker.io/library/mariadb:10.4.11... | Getting image source signatures | [..] | Writing manifest to image destination | root@0df6f4899745:/# mariadb | mariadb mariadb-fix-extensions mariadb-show | mariadb-access mariadb-hotcopy mariadb-slap | mariadb-admin mariadb-import mariadb-tzinfo-to-sql | mariadb-analyze mariadb-install-db mariadb-upgrade | mariadb-backup mariadb-optimize mariadb-waitpid | mariadb-binlog mariadb-plugin mariadbd | mariadb-check mariadb-repair mariadbd-multi | mariadb-convert-table-format mariadb-report mariadbd-safe | mariadb-dump mariadb-secure-installation mariadbd-safe-helper | mariadb-dumpslow mariadb-service-convert | mariadb-find-rows mariadb-setpermission | root@0df6f4899745:/# mariadbd ... | 2026-02-17 16:01:53 0 [Note] mariadbd (mysqld 10.4.11-MariaDB-1:10.4.11+maria~bionic) starting as process 6 ... | mariadbd: Please consult the Knowledge Base to find out how to run mysqld as root! | 2026-02-17 16:01:53 0 [ERROR] Aborting Cheers! Andrew Weaver via discuss <[email protected]>, 17/02/2026 – 10:32:28 (-0500): > I saw that article the problem I ran into with that was that the repo it > references doesn't exist. > > This https://mirror.mariadb.org/yum/10.4 > > and > > This https://mirror.rackspace.com/mariadb/yum/10.4 > > Are both 404s now. > > Is there a vault repo somewhere that I couldn't locate? > > > On 2026-02-17 10:27, Gordan Bobic wrote: > > > On Tue, 17 Feb 2026 at 17:21, Andrew Weaver via discuss > > <[email protected]> wrote: > > > > > Sorry to reply to myself like an insane person but I have also tried > > > generating the source data by using the mariabackup command and the > > > result of that was this: > > > > > > 2026-02-17 10:18:18 0 [ERROR] InnoDB: Upgrade after a crash is not > > > supported. The redo log was created with Backup 10.4.11-MariaDB. You > > > must start up and shut down MariaDB 10.4 or earlier on the data > > > directory. > > > > > > Do I need to somehow install 10.4.11 on AlmaLinux 9 just to startup > > > the database and stop it and then somehow upgrade back to 10.5? > > > > > > Would that actually work? > > > > Yes. See here: > > https://shatteredsilicon.net/mariadb-10-4-on-el9/ > > > > You will need to explicitly adjust for 10.4.11. > _______________________________________________ > discuss mailing list -- [email protected] > To unsubscribe send an email to [email protected] -- Faustin Lammler MariaDB Foundation GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79
signature.asc
Description: PGP signature
_______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
