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

**URL:** <https://forums.percona.com/t/database-page-corruption-on-disk-or-a-failed-file-read-of-page/3308>\
**Category:** Other MySQL® Questions\
**Created:** [February 28, 2014, 4:14am UTC](https://forums.percona.com/t/database-page-corruption-on-disk-or-a-failed-file-read-of-page/3308 "2014-02-28T04:14:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![adriansmith](https://avatars.discourse-cdn.com/v4/letter/a/e0b2c6/32.png) [@adriansmith](https://forums.percona.com/u/adriansmith)\
**Post date:** [February 28, 2014, 4:14am UTC](https://forums.percona.com/t/database-page-corruption-on-disk-or-a-failed-file-read-of-page/3308/1 "2014-02-28T04:14:43Z")

</div>

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 [url][http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html[/url]](http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html%5B/url%5D)  
InnoDB: about forcing recovery.

---

<div class="post-metadata">

**Author:** ![adriansmith](https://avatars.discourse-cdn.com/v4/letter/a/e0b2c6/32.png) [@adriansmith](https://forums.percona.com/u/adriansmith)\
**Post date:** [February 28, 2014, 8:10am UTC](https://forums.percona.com/t/database-page-corruption-on-disk-or-a-failed-file-read-of-page/3308/2 "2014-02-28T08:10:18Z")

</div>

an update, I’ve run every query (its a slave) for the hour preceeding the crash without any errors