Reads the last 24 hours of dmesg logs and filter for io errors, saving the results in the system check database.
I/O errors are usually not critical if not seen often, but when composed with other persistent indicators might indicate issues related to the filesystem or even hardware failure on the corresponding disk. If problem indications persist, consider backing up important data stored in the filesystem. If other indicators of persistent and critical filesystem-related issues are noticed in addition to this check, a full reinstall of the system through USB with the “format partitions” option will rebuild the filesystems (and wipe all existing data). In extreme cases, the disk may need to be replaced.
Command Executed
dmesg -T --since "24 hours ago" | grep -i "IO Error"Example:
dmesg -T --since "24 hours ago" | grep -i "IO Error"Issue Identification
Navigate to Tracking :: System :: System Check and look for IO error events.
Summary Message: IO Errors.
Drill down into the system check the entry on the System Check Summary Table or click Last Check.
Check for dmesg_io_err error count in the Command Table.
Issue Types
Buffer I/O Error: Low-level block device read/write failure (bad sectors or hardware issues).
JBD2: Detected I/O Errors: Filesystem journal corruption (ext3/ext4 journaling failure).
Example Expected Output
root@nodegrid:~# dmesg -T --since "24 hours ago" | grep -i "I/O Error"Example Errors Output
root@nodegrid:~# dmesg -T --since "24 hours ago" | grep -i "I/O Error"
[19226.037866] EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 5 writing to inode 135856475 (offset 0 size 0 starting block 1086882164)
[19226.037873] Buffer I/O error on device sda1, logical block 1086881907
[19226.037887] EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 5 writing to inode 135856478 (offset 0 size 0 starting block 1086882165)
[19226.037892] Buffer I/O error on device sda1, logical block 1086881908