This presents information usage details. The sub-tabs provide read-only information.
System Check sub-tab
Availability
The System Check sub-tab is available from Nodegrid 6.0.26 release onwards.
Troubleshooting
For information on how to troubleshoot potential issues raised by system check, see the How To Guide titled “How to Troubleshoot System Check Issues”.
The Nodegrid System Check feature enables you to monitor the health of your system more closely. This page gives you better visibility into any warnings or potential failures detected during the most recent system check. When an issue is found, a banner appears at the top as the notification.
This banner includes a direct link to the System Check Tracking page. Clicking on this link navigates to the Tracking:: System:: System Check page. Use this page to review details and take appropriate action.
The System Check Tracking page displays a chart where each block represents a single system check run.
Each block is color-coded to reflect the result of the check:
Green – The system check was completed successfully with no errors.
Yellow – The system check was completed with warnings.
Red – The system check detected one or more errors.
Grey - No system check data is available.
Hover over any block to see details such as the date the check was performed and the status of that specific run.
You can also search for system checks by a specific date range using the From and To fields to view results within that selected period.
The System Check Tracking page also provides the same information in a table format. The table includes the following details for each system check run:
Date – When the system check was performed.
Summary – A brief description of any issues detected during the check. If no issues were found during a run, the summary field will be empty, and the error count will be zero.
Error Count – The number of errors identified.
Click Run Check to trigger a new system check instantly. Review the red bars in the chart to identify runs where issues were detected. Click on a specific run (in the chart or table) to view detailed information about the errors and warnings found during that check.
If needed, click Last Check Results to review the in the latest system check. This is same as clicking on the latest block in the chart. Doing this drills down the more detailed information about the selected system check as shown in the following diagram.
A separate Commands table is available, listing all the commands used during the system check. This table includes:
The command executed.
The type of issues that can be detected by that command.
A counter showing how many times each type of error occurred.
You can also review the summary of errors showing a quick overview of what happened during the last five system check runs. Additionally, if any command output contains issues or errors, the details are displayed in the Logs section.
System Check Tracking CLI
Run the command system_check_history to track the system check history. Following is an example of system check history and the commands used during the system check.
[admin@nodegrid]# cd /system/system_check_history
[admin@nodegrid system_check_history]# show
date and time summary severity errors
========================= ============================ ============== ======
2025-03-27T02:30:01-00:00 - 0
2025-03-26T02:30:01-00:00 - 0
2025-03-25T02:30:01-00:00 - 0
2025-03-24T02:30:01-00:00 - 0
2025-03-23T02:30:02-00:00 - 0
2025-03-22T02:30:01-00:00 - 0
2025-03-21T02:30:01-00:00 - 0
2025-03-20T14:05:46-00:00 - 0
2025-03-20T02:30:02-00:00 - 0
2025-03-04T02:00:00-00:00 message, message, message... Critical Error 6
2025-03-03T02:00:00-00:00 message, message, message Error 3
2025-03-02T02:00:00-00:00 Warning 0
2025-03-01T02:00:00-00:00 - 0
2025-02-25T16:02:50-00:00 No Data - -
[admin@nodegrid system_check_history]# cd 2025-03-04T02:00:00-00:00
[admin@nodegrid 2025-03-04T02:00:00-00:00]# show
command errors severity
==================== ====== ========
tune2fs 1 High
sys_ext4 5 High
dmesg_crit 0 Critical
dmesg_io_err 0 Critical
dmesg_wlan 0 Critical
read_only 0 Critical
badblocks 0 High
badblocks_timeout 0 High
badblocks_tmp_fail 0 High
smartctl_err 0 High
ssd_life_left_10 0 High
ssd_life_left_20 0 High
part_full 0 High
temperature 0 Critical
fsck_err_corrected 0 Warning
fsck_reboot 0 Warning
fsck_err_uncorrected 0 High
fsck 0 High
Refer to the section How to Troubleshoot System Check Issues on identifying and resolving common issues encountered during system checks.