Reads the last 24 hours of dmesg Linux logs and filter for critical errors, saving the results in the system check database.
Issues indicated by this check are application-dependent and should be investigated in a case-by-case basis depending on the application that generated them.
Command Executed
dmesg -T --since "24 hours ago" | grep -i "Critical"Issue Identification
Navigate to Tracking :: System :: System Check and look for dmesg events.
Summary Message: Critical Error in dmesg
Drill down into the system check the entry on the System Check Summary Table or click Last Check.
Check for dmesg_crit error count in the Command Table.
Example Expected Output
root@nodegrid:~# dmesg -T --since "24 hours ago" | grep -i "Critical"Example Errors Output
root@nodegrid:~# dmesg -T --since "24 hours ago" | grep -i "Critical"
[11681.875200] blk_update_request: critical medium error, dev sdb, sector 2212099538 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[11685.578885] blk_update_request: critical medium error, dev sdb, sector 2212099538 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[11689.224689] blk_update_request: critical medium error, dev sdb, sector 2212099538 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[12161.978436] blk_update_request: critical medium error, dev sdb, sector 2212099298 op 0x0:(READ) flags 0x80700 phys_seg 32 prio class 0
[12165.740028] blk_update_request: critical medium error, dev sdb, sector 2212099538 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[12169.443682] blk_update_request: critical medium error, dev sdb, sector 2212099538 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[19226.037858] print_req_error: critical target error, dev sda, sector 8695057304