troubleshoot-smartctl-disk-monitoring

Diagnose smartctl S.M.A.R.T. alerts by querying Netdata MCP-exposed signals to triage disk health. The Skill routes through an operator playbook diagnostic tree to identify failure archetypes like gradual media degradation, sudden mechanical failure, or SSD wear-out, matching each with a remediation path.

Smartctl monitoring distinguishes gradual media degradation, sudden mechanical failure, SSD wear-out cliffs, interface/transport failures, and thermal damage. It uses S.M.A.R.T. evidence pulled via Netdata MCP queries to classify the specific failure archetype affecting the disk.

Troubleshoot anomalous disk behavior outside expected envelopes by running MCP queries like find_anomalous_metrics and query_metrics over smartctl contexts. Optional correlation queries help pinpoint whether the cause is thermal damage, interface failure, or mechanical degradation before applying playbook remediation.

Yes, you need Netdata MCP queries to triage disk health with smartctl signals. The Skill requires MCP queries including list_nodes, query_metrics, and find_anomalous_metrics over smartctl contexts to pull the S.M.A.R.T. health data needed for the diagnostic tree.

The verification workflow confirms a smartctl disk issue is resolved by re-running targeted MCP verification queries. It checks that the S.M.A.R.T. signals return to their expected bands before considering the remediation complete and the issue closed.