1674
MariaDBERRORCommonStorage EngineHIGH confidence
I/O read error occurred
Production Risk
Critical — I/O errors indicate potential hardware failure; immediate action required.
What this means
MySQL encountered an I/O read error while attempting to read data from a tablespace file, indicating a disk, filesystem, or file corruption issue.
Why it happens
- 1Physical disk failure or bad sectors.
- 2File system corruption.
- 3The .ibd file was deleted or is inaccessible.
- 4Storage hardware or RAID controller returning read errors.
How to reproduce
trigger — this will error
trigger — this will error
SELECT * FROM t; -- where t's .ibd file has I/O errors
expected output
ERROR 1674 (HY000): Got error 23 when reading file './mydb/t.ibd' (OS errno 5 - Input/output error)
Fix 1
Check filesystem and disk health
Check filesystem and disk health
-- Run fsck or chkdsk on the affected filesystem -- Check dmesg/Event Viewer for disk errors
Why this works
Identifying and resolving disk errors at the OS level is the first step.
Fix 2
Restore from backup
Restore from backup
-- Stop MySQL, restore from a known-good backup, restart MySQL
Why this works
A clean backup eliminates corrupted data files.
What not to do
✕
Sources
Official documentation ↗
MySQL 8.0 — 1674 ER_IO_READ_ERROR
Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev