Miko

That's the problem I'm currently facing. I cant find any documents relating to this error. Will give it a shot. Is there maybe a way i can force it into recovery mode. That is the other part I'm currently struggling with. or run the innodb_force_recovery = 4

Hello Everyone. I have a slight issues. Yesterday we had some very heavy rain and heavy lighting. (Lighting hit a Lamp pole on the streets and forced that voltage back into the grid) And our UPS batteries exploded and tripped the circuit breaker of mains power and the UPS circuit breaker. We where busy with a importing data into the docker container when this happed. Im trying to-do a data recovery because this is what the log files sales. 2023-01-20 23:09:04 0 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: ./ibdata1 2023-01-20 23:09:04 0 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: ./ibdata1 2023-01-20 23:09:04 0 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: ./ibdata1 2023-01-20 23:09:04 0 [ERROR] InnoDB: Page [page id: space=0, page number=370571] log sequence number 685813904476 is in the future! Current system log sequence number 432631856. 2023-01-20 23:09:04 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery. 2023-01-20 23:09:04 0 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: ./ibdata1 The ib_lofile0 might be corrput, is there a way to rebuild the ib_lofile0 or ignore it to do a database dump.