Looks like mysqld crashes when trying to open a specific table. There is likely corruption in the ibd file.
If you are able to identify which table this is, you can try to see if you can trigger mysqld to crash on reading from the table with:
SELECT * FROM <suspect_table>
If you want to try to repair it before doing the upgrade, you can do:
ALTER TABLE <suspect_table> ENGINE=InnoDB;
And if mysqld still crashes after doing the ALTER, then you’ll likely have to upgrade using logical dump / load, for example from mydumper or mysql-shell
Hello,
Thank you very much. I
've able to startup using the same data directory from backup on 5.7 however the upgrade process is failing If there is corruption it would be corrupted in both versions isn’t?
Forgot to add another part of the log:
"
2023-09-13T17:06:56.824282Z 1 [System] [MY-011012] [Server] Starting upgrade of data directory.
2023-09-13T17:06:56.824300Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-09-13T17:07:01.629682Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2023-09-13T17:07:01Z UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=ca49d76ef174ee7e1c54a2f96f416aa56b1c07aa
Server Version: 8.0.33-25 Source distribution
"
and there is coming stack trace .
Update.
I found the tables and it seems I do hit bug but different one:
There is tables that prevent me from upgrade.
I don’t see any reason.
CREATE TABLE f1 ( id bigint(20) unsigned NOT NULL AUTO_INCREMENT, text varchar(255) COLLATE ascii_bin NOT NULL,
PRIMARY KEY (id),
FULLTEXT KEY text (text)
) ENGINE=InnoDB AUTO_INCREMENT=112 DEFAULT CHARSET=ascii COLLATE=ascii_bin
CREATE TABLE f2 ( id int(10) unsigned NOT NULL, text varchar(255) CHARACTER SET ascii COLLATE ascii_bin NOT NULL,
PRIMARY KEY (id),
FULLTEXT KEY text (text)
) ENGINE=InnoDB DEFAULT CHARSET=latin1