Mariadb not starting and I don't know why.. was working fine before

Help! (Home for newbies)
1
SYSTEM INFORMATION
OS type and version Ubuntu 24.04.3 LTS
Virtualmin version 7.50.0 GPL

|Webmin version|[2.520]

mariadbd[3832143]: 2025-12-02 20:19:29 0 [Note] InnoDB: Set innodb_force_recovery=1 to ignore corrupted pages.
mariadbd[3832143]: 2025-12-02 20:19:29 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
mariadbd[3832143]: 2025-12-02 20:19:29 0 [Note] InnoDB: Starting shutdown…
mariadbd[3832143]: 2025-12-02 20:19:29 0 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
mariadbd[3832143]: 2025-12-02 20:19:29 0 [Note] Plugin ‘FEEDBACK’ is disabled.
mariadbd[3832143]: 2025-12-02 20:19:29 0 [ERROR] Unknown/unsupported storage engine: InnoDB
mariadbd[3832143]: 2025-12-02 20:19:29 0 [ERROR] Aborting
systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: mariadb.service: Failed with result ‘exit-code’.
systemd[1]: Failed to start mariadb.service - MariaDB 10.11.13 database server.

[Note] InnoDB: Compressed tables use zlib 1.3
[Note] InnoDB: Number of transaction pools: 1
[Note] InnoDB: Using crc32 + pclmulqdq instructions
[Note] InnoDB: Using liburing
[Note] InnoDB: innodb_buffer_pool_size_max=128m, innodb_buffer_pool_size=128m
[Note] InnoDB: Initialized memory pressure event listener
[Note] InnoDB: Completed initialization of buffer pool
[Note] InnoDB: File system buffers for log disabled (block size=4096 bytes)
[Note] InnoDB: Starting crash recovery from checkpoint LSN=11710916772
[Note] InnoDB: End of log at LSN=11718798760
[Note] InnoDB: 3 transaction(s) which must be rolled back or cleaned up in total 3 row operations to undo
[Note] InnoDB: Trx id counter is 15004637
[Note] InnoDB: To recover: 379 pages
[ERROR] InnoDB: Not applying DELETE_ROW_FORMAT_DYNAMIC due to corruption on [page id: space=97, page number=174]
[ERROR] InnoDB: Set innodb_force_recovery=1 to ignore corruption.
[Note] InnoDB: Set innodb_force_recovery=1 to ignore corrupted pages.
[ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
[Note] InnoDB: Starting shutdown…
[ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
[Note] Plugin ‘FEEDBACK’ is disabled.
[ERROR] Unknown/unsupported storage engine: InnoDB
[ERROR] Aborting

Anything I can do reset it? or restore it? is plenty of disk space, and memory.. not sure what happened here.

2

seems like I had one virtual server that was left on a default plan with 2gb limit (hate that default plan limit clearly forgot to remove it) and the whole db got broken because of it?

2025-11-29 21:43:49 575613 [ERROR] mariadbd: Disk got full writing ‘information_schema.(temporary)’ (Errcode: 28 “No space left on device”)

:sad_but_relieved_face:

is there someway I can restore things in /var/lib/mysql removing anything?

3

It means one or more of your database files corrupt in some way (maybe a failing disk, maybe system was shutdown improperly, maybe something else).

You’ll want to try recovery. So, backup your system, specifically the Mariadb data files somewhere in /var/lib.

Then start Mariadb in recovery mode with the option it suggested you use (innodb_force_recovery=1) configured in your my.cnf or wherever your [mysqld] configuration section it.

If you’re able to get it to start, I probably recommend you dump your databases, delete the old databases, reinitialize and then restore the databases you dumped. That gets you do a known good state.

Note that we’re not the right people to tell you what to do about Mariadb problems. We didn’t write and don’t maintain Mariadb. We are not experts. I use it a little more often than you do and for probably a lot longer of a time, but I’m not an expert! Check in with the Mariadb documentation and forums!

4

well I mean its default script install of virtual min on ubuntu 24lts.. where would that file be

5

Oh, if you know which database is corrupt, you can focus on only that one. If you have a recent Virtualmin backup of that Virtual Server from before the corruption, you should already have a dump of the database, which means you can just blow away the problem database, restart Mariadb, and restore the database.

6

We use system packages. All files are where your OS puts them. I’m not sitting in front of an Ubuntu system at the moment, but you should just be able to poke around in /etc to find it.

You can even search with grep -R mysqld /etc

7

simple as removing the virtual server profile folder that is used in /var/lib/mysql ?

I don’t have any backup on the default installed db, only setup this server fresh a month ago

8

If you don’t have anything worth backing up, then you don’t care about restoring it, so you can just delete it and recreate.

9

when you say delete it?

what part can I delete to just have it start up with fresh tables?

10

I have the databases backed up..

question is how can I keep the config settings, but just recreate all the initial files in /var/lib/mysql

/var/lib/mysql/ib_logfile0 is corrupted but deleting it doesn’t work with starting mariadb without it

[ERROR] InnoDB: ib_logfile0 is empty, and LSN is unknown.
[ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
[Note] InnoDB: Starting shutdown…
[ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
[Note] Plugin ‘FEEDBACK’ is disabled.
[ERROR] Unknown/unsupported storage engine: InnoDB
[ERROR] Aborting

11

basically how can I reinstall mariadb as if I had run the virtual min install script, without breaking any of the virtualmin setup, where I can set a new root password for mariadb, and going to …10000/mysql/start.cgi?xnavigation=1 works