[ERROR] InnoDB: Database page corruption on disk or a failed file read of page
Hello,
I ran into a problem with my MySQL database on a Nvidia Jetson Nano. All of a sudden the database went corrupt with message:
[ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=0, page number=2078]. You may have to recover from a backup.
According to the IT-guy who restored the database one of the files were missing
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
The version was:
Server version: 5.7.42-0ubuntu0.18.04.1 (Ubuntu)
The restoration process was:
* Put mysql in recovery mode
* Made a backup with mysqldump
* Deleted the databases
* Cleared transaction logs
* Restored the system database
* Imported the mysql dump
* Removed recovery mode
* Started in normal mode
No data was lost but we had some off time, and we don't want this to happen again. I am grateful for responses so we can prevent this to happen again.
Is there any knowns bugs for this version that could have caused this or any other known problems that can cause this?
$ sudo tail /var/log/mysql/error.log -n 10000
2024-06-17T11:22:36.184533Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.42-0ubuntu0.18.04.1) starting as process 9827 ...
2024-06-17T11:22:36.196894Z 0 [Note] InnoDB: PUNCH HOLE support available
2024-06-17T11:22:36.196969Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2024-06-17T11:22:36.196999Z 0 [Note] InnoDB: Uses event mutexes
2024-06-17T11:22:36.197026Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2024-06-17T11:22:36.197053Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2024-06-17T11:22:36.197080Z 0 [Note] InnoDB: Using Linux native AIO
2024-06-17T11:22:36.198518Z 0 [Note] InnoDB: Number of pools: 1
2024-06-17T11:22:36.198950Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2024-06-17T11:22:36.204126Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2024-06-17T11:22:36.240555Z 0 [Note] InnoDB: Completed initialization of buffer pool
2024-06-17T11:22:36.246257Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2024-06-17T11:22:36.262871Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2024-06-17T11:22:36.266851Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 11307628957
2024-06-17T11:22:36.266921Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 11307629499
2024-06-17T11:22:36.267349Z 0 [Note] InnoDB: Database was not shutdown normally!
2024-06-17T11:22:36.267387Z 0 [Note] InnoDB: Starting crash recovery.
2024-06-17T11:22:36.453977Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-06-17T11:22:36.454055Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-06-17T11:22:36.454205Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-06-17T11:22:37.092688Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2024-06-17T11:22:37.095278Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2024-06-17T11:22:37.095333Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2024-06-17T11:22:37.096459Z 0 [Note] InnoDB: Waiting for purge to start
2024-06-17T11:22:37.146798Z 0 [Note] InnoDB: 5.7.42 started; log sequence number 11307629499
2024-06-17T11:22:37.147194Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2024-06-17T11:22:37.147768Z 0 [Note] Plugin 'FEDERATED' is disabled.
2024-06-17T11:22:37.157476Z 0 [Note] InnoDB: Buffer pool(s) load completed at 240617 13:22:37
2024-06-17T11:22:37.170107Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2024-06-17T11:22:37.170190Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory.
2024-06-17T11:22:37.170215Z 0 [Warning] A deprecated TLS version TLSv1 is enabled. Please use TLSv1.2 or higher.
2024-06-17T11:22:37.170234Z 0 [Warning] A deprecated TLS version TLSv1.1 is enabled. Please use TLSv1.2 or higher.
2024-06-17T11:22:37.172061Z 0 [Warning] CA certificate ca.pem is self signed.
2024-06-17T11:22:37.172185Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
2024-06-17T11:22:37.172456Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2024-06-17T11:22:37.172497Z 0 [Note] - '127.0.0.1' resolves to '127.0.0.1';
2024-06-17T11:22:37.172566Z 0 [Note] Server socket created on IP: '127.0.0.1'.
2024-06-17T11:22:37.218912Z 0 [Note] Event Scheduler: Loaded 0 events
2024-06-17T11:22:37.219457Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.42-0ubuntu0.18.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
2024-06-17T11:22:37.288008Z 0 [ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=0, page number=2078]. You may have to recover from a backup.
2024-06-17T11:22:37.288078Z 0 [Note] InnoDB: Page dump in ascii and hex (16384 bytes):
Subject
Views
Written By
Posted
[ERROR] InnoDB: Database page corruption on disk or a failed file read of page
269
June 19, 2024 06:23AM
102
July 22, 2024 03:30AM
Sorry, only registered users may post in this forum.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.