rrors 126, 136 and 144 usually mean crashed index files or failed repairs. REPAIR TABLE and myisamchk cover basic MyISAM cases, but InnoDB corruption often needs more.

Two rules first: stop writes to the affected database, and back up the data directory before touching anything.

For deeper recovery — tables, data, indexes, keys, triggers and views — Kernel for MySQL Database Recovery supports MySQL 3.x through 8.x and both InnoDB and MyISAM. It saves into a new or existing database, restores online via MySQL Settings or offline through Batch File Mode, and logs any files it couldn't save. A free trial lets you preview recovered objects first.

How do you handle InnoDB corruption — innodbforcerecovery or a dedicated recovery tool?
https://www.nucleustechnologies.com/mysql-repair.html