2024-11-10 23:40:02 140452329683136 [ERROR] [FATAL] InnoDB: Trying to read page number 4294967295 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
241110 23:40:02 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
I don’t know what that error means, though (I’m not a Mariadb developer, and I’ve never seen this particular error).
I found this:
Note that in space 0 seems to be specific (there are lots of other reports of similar errors but in other space numbers…again, no idea what that means, but in space 0 seems like a different problem than in space 89 or whatever).
From what I can tell, what I said above remains true: It could be hardware failing, could be disk. You should do what I said above and check those things in addition (and maybe before) futzing around trying to fix the database. If you’re disk is failing or you’ve got bad memory or the kernel is crashing randomly, you probably won’t have much luck fixing software problems. Also make sure you’re not running out of disk space of have a full quota for a user with a database (if you’re using quotas and your database files are stored on a filesystem subject to quotas).