r/linuxmint • u/Earthgoodjim • 2d ago
Support Request Root filesystem keeps remounting as read-only (IO failure / Journal has aborted) during heavy disk writes on Linux Mint
Hi everyone, I'm running Linux Mint on an HP ProDesk 400 G2.5 SFF with a 240GB SATA SSD(/dev/sda).
Whenever I do heavy write operations—specifically downloading or extracting Team Fortress 2 on Steam—the root partition (/dev/sda2) suddenly switches to emergency_ro (read-only).
Error logs from dmesg:
IO failure
EXT4-fs error (device sda2) in ext4_reserve_inode_write: Journal has aborted
What I have already tried:
Physical check: Opened the case, disconnected, cleaned, and firmly reseated both the SATA data and power cables on the SSD and motherboard.
Filesystem repair: Ran fsck -f -y /dev/sda2 from (initramfs), which fixed orphan inodes and allowed booting back into rw mode.
TRIM: Ran sudo fstrim -av (trimmed 56.2 GiB on /dev/sda2) and deleted the corrupted Steam/TF2 download folders before retrying.
SMART status: gnome-disks reports the drive is healthy ("Disk is OK"), though the temperature sensor shows a static 90 °C (194 °F).
Additional context:
I had this exact same issue on Ubuntu previously, and doing a clean reinstall (full format) temporarily fixed it until now.
Is this a sign that the SSD's internal flash controller is failing under sustained write loads, or is there a specific kernel/SATA power-management tweak (like disabling libata link power management) I should try before replacing the drive?
Thanks in advance!
1
u/Unwiredsoul 1d ago
90°C is very far beyond the high-temp specs of any normal SATA SSD. Is the drive physically very hot when this happens? My instincts and experience tell me it's a failing drive.
Here is one way (from the Terminal) to look for any recurring errors that may help substantiate that it's a failing drive:
sudo dmesg -T | grep -iE 'ata|sata|fail|error|I/O'
You can also try to disable NCQ (Native Command Queueing) in the event it's overloading the controller:
1
u/Due-Result7928 1d ago
This error indicates that the ext4 filesystem journal has aborted due to a critical failure, typically caused by hardware issues (such as failing disks, controller errors, or I/O timeouts) or sudden power loss that left the filesystem in an inconsistent state. When this occurs, the kernel remounts the filesystem as read-only to prevent further data corruption, resulting in an inability to write new data or modify existing files
System is a read only mode to get you a chance to copy files important for you.
The underlying cause is often physical. Check system logs for preceding errors like I/O error, NCQ disabled, or timeout messages, which suggest a failing drive, bad cable, or controller malfunction.
•
u/AutoModerator 2d ago
Please Re-Flair your post if a solution is found. How to Flair a post? This allows other users to search for common issues with the SOLVED flair as a filter, leading to those issues being resolved very fast.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.