может зависеть от дистрибутива и текущей конфигурации, в первую очередь стоит посмотреть наличие /var/lib/mysql, /var/lib/mysqld

/var/log/mysql, конечно, про lib это я упал слегка

InnoDB: End of page dump 2017-09-29T15:32:21.498430Z 8 [Note] InnoDB: Uncompressed page, stored checksum in field1 1297768405, calculated checksums for field1: crc32 1189935544/1680539700, innodb 1742113934, none 3735928559, stored checksum in field2 1297768405, calculated checksums for field2: crc32 1189935544/1680539700, innodb 1556522974, none 3735928559, page LSN 22 715582511, low 4 bytes of LSN at page end 715582511, page number (if stored to page already) 51083, space id (if created with >= MySQL-4.1.1 and stored already) 417 InnoDB: Page may be an index page where index id is 2796 2017-09-29T15:32:21.498441Z 8 [Note] InnoDB: Index 2796 is `IX_Chrt_nm_id` in table `GoodsDB`.`Chrt` 2017-09-29T15:32:21.498444Z 8 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2017-09-29T15:32:21.498491Z 8 [ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=417, page number=51083]. You may have to recover from a backup. 2017-09-29T15:32:21.498494Z 8 [Note] InnoDB: Page dump in ascii and hex (16384 bytes):

Как-то так, но я пробовал перезагружаться и инспектор таблиц говори, что они в порядке

Попробуй ребилд индекса сделать

Может поможет

Если есть возможность