Read-only File System Error in Linux

The "Read-only file system" error is one of the common issues in Linux that users and system administrators encounter. This error means that the file system has been mounted or switched to a mode that allows only reading of data, and any attempts to write, create, or modify files fail.

Symptoms of the Error

When the error occurs, you may observe the following symptoms:

• Inability to create, modify, or delete files
• Errors like "Read-only file system" when attempting to write
• Inability to save changes to configuration files
• Warnings from applications about the inability to write data

cp: cannot create regular file '/path/to/file': Read-only file system
touch: cannot touch '/path/to/file': Read-only file system
echo "text" > file.txt: Read-only file system

Causes of the Error

There are several main reasons why a file system may switch to read-only mode:

1. Automatic Protection Against Corruption

The Linux kernel automatically switches the file system to read-only mode when critical errors are detected to prevent further data corruption. This can occur upon detecting:

• Errors in the file system journal
• Mismatched checksums
• Critical input/output errors

2. Media Issues

Hardware problems with the disk or SSD can also cause this error:

• Physical damage to the disk
• Issues with the SATA/NVMe cable
• Malfunction of the storage controller
• SSD wear (reaching the rewrite limit)

3. Incorrect Mount Options

Errors in the /etc/fstab configuration can lead to the file system being mounted in the wrong mode:

# Example of incorrect entry (ro = read-only)
UUID=xxx / ext4 ro 0 1

4. Permission Issues

Although this is less common, incorrect permissions on the mount point can cause write issues.

5. External Media

USB drives, SD cards, and external hard drives may have hardware write protection or may be damaged.

Diagnosing the Problem

Step 1: Check Mount Status

First, you need to determine which file systems are mounted and in what mode:

# View all mounted file systems
mount | grep -i '/dev/sd'

# Detailed information about a specific file system
mount | grep '/dev/sda1'

# Check disk usage
df -h

Pay attention to the mount options in the command output. If you see ro instead of rw, it means the file system is mounted as read-only.

Step 2: Check System Log

The system log often contains valuable information about the reasons for switching to read-only mode:

# View the last kernel messages
dmesg | tail -100 | grep -i 'error\|fail\|readonly'

# View the systemd log (for modern distributions)
journalctl -xe | grep -i 'filesystem\|mount\|error'

# Filter by specific device
dmesg | grep -i sda

Look for messages about input/output errors, file system errors, or warnings about disk issues.

Step 3: Check Disk Status (S.M.A.R.T.)

If there are suspicions of hardware problems, check the status of the storage device:

# Install smartmontools (if not installed)
sudo apt install smartmontools  # Debian/Ubuntu
sudo yum install smartmontools  # CentOS/RHEL

# Get disk information
sudo smartctl -i /dev/sda

# Short health test
sudo smartctl -H /dev/sda

# Detailed information
sudo smartctl -a /dev/sda

Ways to Resolve the Error

Method 1: Remount the File System

If the file system was mounted in read-only mode (but not locked by the kernel), you can try to remount it:

# Remount in read/write mode
sudo mount -o remount,rw /mount/point

# For example, for the root file system
sudo mount -o remount,rw /

# For a specific partition
sudo mount -o remount,rw /dev/sda1 /mnt

If the remounting is successful, you will see a corresponding message or simply return to the command prompt without errors.

Method 2: Check and Repair the File System

If there are errors in the file system, it needs to be checked and repaired:

Important: Before checking the file system, the partition must be unmounted!

# For the root file system, boot from LiveUSB

# Check ext4 file system
sudo fsck -y /dev/sda1

# Check with automatic fixing
sudo fsck -fy /dev/sda1

# Check XFS file system
sudo xfs_repair /dev/sda1

# Check Btrfs file system
sudo btrfs check --repair /dev/sda1

Method 3: Fix /etc/fstab Configuration

If the problem is caused by incorrect options in /etc/fstab, you need to correct the configuration:

# Backup fstab
sudo cp /etc/fstab /etc/fstab.backup

# Edit the file
sudo nano /etc/fstab

Find the line with the problematic partition and change the ro option to rw:

# Was (incorrect)
UUID=xxx / ext4 ro 0 1

# Now (correct)
UUID=xxx / ext4 rw 0 1

Also, ensure that the necessary options are specified in the mount parameters:

# Recommended options for the root file system
UUID=xxx / ext4 defaults,errors=remount-ro 0 1

Method 4: Check and Replace Cables and Connectors

If the problem is related to hardware connections:

1. Turn off the computer
2. Check the connection of SATA/NVMe cables
3. Try using a different cable
4. Connect the disk to another port on the motherboard

Method 5: Working with External Media

For USB drives, SD cards, and external disks:

# Check write protection status
lsblk -o NAME,RO /dev/sdb

# Attempt to remount
sudo mount -o remount,rw /dev/sdb1

# Check the write protection switch on the media
# (hardware protection cannot be disabled via software)

Preventing the Problem

To avoid encountering the "Read-only file system" error in the future:

1. Regularly check the status of disks — use S.M.A.R.T. monitoring
2. Monitor the health of the file system — conduct periodic checks
3. Use uninterruptible power supplies — protection against power surges
4. Create backups — regularly back up important data
5. Update the system — timely updates fix known bugs
6. Monitor logs — pay attention to warning messages

Conclusion

The "Read-only file system" error in Linux is a protective mechanism that safeguards data from further corruption. Although it can be caused by various reasons, most cases can be resolved using the methods described.

It is important to remember that upon encountering such an error, you should not ignore the problem. Attempts to continue working may lead to data loss or the inability to recover the file system. Always conduct diagnostics and seek professional help if necessary.

If you are unsure of your actions or the data is of particular value, it is recommended to seek professional data recovery services.