Check the system EXT4 error event count. Reads /sys/fs/ext4/sda[n]/errors_count, checking if it is not 0, and saves the results in the system check database.
Issues reported by this check might be cleared upon reboot by the automatic file system check, or may be indicators of filesystem issues.
Filesystem errors are common and usually not critical. 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).
Command Executed
cat /sys/fs/ext4/sda[n]/errors_countwhere n is in {1, 2, 3, 5, 7, 8}, and /dev/sda[n] is an ext4 partition.
Example:
cat /sys/fs/ext4/sda3/errors_count💡Tip
use - parted -l - if required, to identify partitions and partition types.
Issue Identification
Navigate to Tracking :: System :: System Check and look for file system corruption events.
Summary Message: File Corrupted.
Drill down into the system check the entry on the System Check Summary Table or click Last Check.
Check for sys_ext4 error count in the Command Table.
Issue Types
errors_count - 1 to n
Example Expected Output
root@nodegrid:~# cat /sys/fs/ext4/sda3/errors_count
0Example Errors Output
root@nodegrid:~# cat /sys/fs/ext4/sda3/errors_count
3