Linux IO_ERRORHigh

Input/Output Error in Linux: Causes and Solutions

The Input/Output Error (I/O error) in Linux indicates problems with reading or writing data. It may be caused by hardware issues, file system corruption, or driver errors.

Updated at February 13, 2026
15-45 min
Medium
FixPedia Team
Применимо к:UbuntuDebianCentOSRHELFedoraLinux Mint

Input/Output Error in Linux

The Input/Output Error (I/O Error) is one of the most common issues in Linux systems, indicating an inability to read or write data. This error can occur when working with files, directories, or when accessing a disk, and can be caused by both hardware and software problems.

Symptoms of the Error

The I/O error may manifest itself in the following ways:

  • Message Input/Output error when attempting to read or write a file
  • Inability to mount a partition
  • Errors when launching applications
  • System hangs when accessing files
  • Boot issues

Causes of Occurrence

Hardware Issues

  1. Hard Disk (HDD/SSD) Problems
    • Physical damage to the disk
    • Bad sectors
    • Issues with the SSD controller
    • Overheating of the drive
  2. Connection Issues
    • Faulty SATA cable
    • Poor power connection
    • Problems with connectors on the motherboard
  3. Memory Issues
    • Faulty RAM modules
    • Memory errors can cause false input/output errors

Software Issues

  1. File System Corruption
    • Improper unmounting
    • Power failures
    • Metadata errors
  2. Driver Issues
    • Outdated or incompatible drivers
    • Driver conflicts
  3. Access Rights Issues
    • Insufficient read/write permissions

Error Diagnosis

Step 1: Check the System Log

First, you need to examine the system log for detailed information:

dmesg | grep -i -E '(error|io error|sd[a-z])'

This command will show the latest kernel messages related to input/output errors. Pay attention to the device name (e.g., sda, sdb) — this will help identify the problematic disk.

Step 2: Check SMART Status

To diagnose the health of the disk, use SMART technology:

# Check overall status
smartctl -H /dev/sda

# Detailed information
smartctl -a /dev/sda

# Run a short test
smartctl -t short /dev/sda

# Run a long test
smartctl -t long /dev/sda

If smartctl -H shows FAILED, this indicates serious problems with the disk.

Step 3: Check the File System

To check and fix file system errors:

# First unmount the partition
sudo umount /dev/sda1

# Check the file system (with automatic fixing)
sudo fsck -f /dev/sda1

Warning: Always unmount the partition before running fsck. For the root partition, use recovery mode or a Live CD.

Step 4: Check SMART Attributes

Review the key SMART attributes:

smartctl -A /dev/sda | grep -E '(Reallocated_Sector_Ct|Power_On_Hours|Seek_Error_Rate|Spin_Retry)'

Pay attention to:

  • Reallocated_Sector_Ct — number of reallocated sectors
  • Spin_Retry — number of spin retry attempts

Step 5: Check Memory

To rule out RAM issues, run a memory test:

# Install memtest86+
sudo apt install memtest86+

# Run from the bootloader
sudo memtester 1024 1

Problem Solutions

Solution 1: Replace Cable and Check Connections

  1. Turn off the computer
  2. Disconnect and reconnect the SATA cable
  3. Try a different cable
  4. Connect the disk to another SATA port

Solution 2: Restore the File System

# Create a backup of data (if possible)
sudo dd if=/dev/sda of=/path/to/backup.img bs=4M status=progress

# Run the check
sudo fsck -y /dev/sda1

Solution 3: Update Drivers and Firmware

# Update the system
sudo apt update && sudo apt upgrade -y

# Update SSD firmware (if supported)
sudo apt install nvme-cli
sudo nvme list

Solution 4: Replace the Disk

If diagnostics show critical errors:

  • The number of reallocated sectors is increasing
  • SMART shows FAILED
  • Unusual sounds (clicking, grinding) are present

It is recommended to immediately replace the disk and restore data from a backup.

Prevention

To prevent I/O errors from occurring:

  1. Regularly check disk health using SMART
  2. Create backups of important data
  3. Use a UPS to protect against power interruptions
  4. Monitor the temperature of disks and the system
  5. Update firmware of disks and drivers
  6. Conduct regular checks of the file system

Conclusion

The Input/Output Error in Linux is a serious issue that requires a systematic approach to diagnosis. Start by examining the system log, then check the health of the disk and the integrity of the file system. Timely detection and resolution of problems will help avoid data loss and ensure stable system operation.

F.A.Q.

What to do if Input/Output Error appears during system boot?
Can an I/O error be caused by RAM issues?
How to determine which disk is causing the error?

Hints

Check the system log
Check disk health
Check the file system
Check disk connection
FixPedia

Free encyclopedia for fixing errors. Step-by-step guides for Windows, Linux, macOS and more.

© 2026 FixPedia. All materials are available for free.

Made with for the community