Posted on November 29, 2021 at 12:58 pm
If you see this on /var/log/daemon.log:
[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. [ERROR] InnoDB: Page [page id: space=128, page number=621786] log sequence number 403934013668 is in the future! Current system log sequence number 36929011435.
According to this:
The only correct solution is to reinstall and restore from a backup.
The database cannot be modified, such as you may not be able to delete rows from a table.
You’re only real solution is to recover an old backup or reset the database.
- Detect VMWare Virtual Machine
- Detect Microsoft Virtual PC Virtual Machine
- Fix MariaDB 10.5 "Can't create test file" errors
- Use MariaDB and MySQL without Password (MySQL Backup)
- Check if a Trademark is already registered
- Make name server address permanent in /etc/resolv.conf
- InnoSetup error the servicemanager is not available
- InnoSetup disable DesktopIcon via command-line
- Use cURL to check for SSL certificate issues:
- How to test Socks5 proxy with cURL
- How to use variables in a sed command
- Best Socks5 Servers for Linux Debian
- Error NO_PUBKEY in Google Cloud Debian Packages Update
- How to Run a Command with Time Limit in Bash Linux
- MySQL InnoDB log sequence number is in the future
- Download CSV Top 1 Million Websites by Popularity