Not the answer you need?
Register and ask your own question!

Database page corruption on disk or a failed file read of page

adriansmithadriansmith EntrantCurrent User Role Beginner
Hi there,

We're having a checksum issue on Windows Server 2012, MySQL 5.5.30 64-bit. The service stops after 100 attempts with an assertion failure. This has happened with 3 different tables. On restarting the service everything seems fine. We have replaced all of the memory (we have an identical server with identical config with about 60% size dataset that is rock solid), suspecting it might be a hardware issue, but not sure where to go from here - do we go and replace RAID controller, mboard etc. This particular table is in the region of 380GB. Is this likely still a hardware issue?

Any pointers would be really helpful.

Thanks
Adrian

InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 15777685.
InnoDB: You may have to recover from a backup.
140228 1:05:54 InnoDB: Page dump in ascii and hex (16384 bytes):
InnoDB: End of page dump
140228 1:05:54 InnoDB: Page checksum 1191678779, prior-to-4.0.14-form checksum 529395600
InnoDB: stored checksum 2474991995, prior-to-4.0.14-form stored checksum 529395600
InnoDB: Page lsn 715 358488128, low 4 bytes of lsn at page end 358488128
InnoDB: Page number (if stored to page already) 15777685,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 323
InnoDB: Page may be an index page where index id is 1032
InnoDB: (index "datetime" of table "autotrak"."vehpos")
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 15777685.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.

Comments

  • adriansmithadriansmith Entrant Current User Role Beginner
    an update, I've run every query (its a slave) for the hour preceeding the crash without any errors
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.