Linux system errors
Input/output error EIO
Reviewed for reference consistency: August 11, 2026
a read or write operation could not complete
What 5 Means
The 5 error on the Linux system errors indicates input/output error eio — a read or write operation could not complete. This typically occurs due to storage or filesystem layer reports that a read or write could not be completed.
Errno 5, commonly named EIO, means an input/output operation failed below the application layer. It can surface while reading, writing, opening, or executing through a path whose backing storage or filesystem layer could not complete the requested operation.
How to fix 5
General informational guidance, not professional advice. Commands can affect your system or data — back up first and proceed at your own risk. FixerCode is an independent reference, not affiliated with any vendor mentioned.
Look for I/O errors in the kernel log
EIO is reported by the layer below your program, so the kernel ring buffer usually names the device or filesystem that failed.
dmesg -T | grep -iE 'i/o error|blk_update|ext4-fs error'Check the storage device health
A read-only SMART report shows reallocated sectors and pending errors that point to a failing disk.
smartctl -a /dev/sdaConfirm the mount is still healthy
A path that was remounted read-only after an error keeps returning EIO until it is remounted cleanly.
mount | grep ' / ' ; dmesg | grep -i 'remount'Rule out a full device or exhausted inodes
A volume with no free space or inodes can surface I/O failures; check both before assuming hardware faults.
df -h && df -i
Technical Background
EIO is an errno value, not a single program-specific exit code. It tells the calling process that a requested input/output operation could not be completed by the layer responsible for the file, device, mount, or backing service.
The useful distinction is that EIO points below application logic. A program may be using the correct path and permissions, yet still receive errno 5 because the underlying I/O path cannot deliver a reliable result.
For FixerCode's Phase 1 scope, this page treats EIO as an OS-level reference signal. It does not turn the condition into storage repair guidance, hardware triage, or device-specific instructions.
Common Causes
- Storage or filesystem layer reports that a read or write could not be completed
- Mounted path becomes unavailable while a process is accessing it
- Kernel receives an I/O failure from a device, driver, or backing service
Typical Scenarios
- A process tries to read a file and the filesystem reports an input/output failure
- A package or update operation stops because a required file path cannot be read reliably
- An application receives EIO from a mounted volume, network-backed filesystem, or device-backed path
What to Know
An EIO reading means the process reached an input/output boundary that could not return a normal result. It is different from permission denial, command syntax failure, or generic exit status because the failure sits in the underlying I/O path.
Frequently Asked Questions
Common questions about Linux 5 error
No. Permission errors reject access based on authorization. EIO means an input/output operation was attempted but the underlying path could not complete it normally.
Related Error Codes
Related Errors From Other Categories
Similar error codes documented across different platforms and systems
Git's internal object database is missing or corrupted.
The operating system denied Git's request for more RAM during a heavy operation.
Git detected corruption inside one of its compressed data bundles (packfiles).
An uncompressed file in Git's internal database has an invalid checksum or zero bytes.