os-restart-diagnosis

To diagnose an unexpected Linux OS restart, run the skill to collect system logs and hardware telemetry. It applies a four-stage diagnostic workflow to aggregate fault fingerprints and output a structured root-cause analysis.

Perform root-cause analysis on a Linux kernel panic or hardware fault by gathering signals and kernel messages. The skill cross-validates hardware indicators and power events to construct a verifiable fault chain revealing the true root cause.

Yes, Linux restart diagnosis works with ipmitool and smartctl to collect hardware indicators. It coordinates these dependencies alongside system logs to cross-validate hardware faults and power events during the diagnostic workflow.

The best way to trace why a Linux workstation lost power and restarted is using a multi-source data fusion approach. The skill gathers power and environment signals, system logs, and hardware telemetry to determine the cause and impact of power loss.

Yes, you can use journalctl and ausearch to investigate unexpected OS reboots. The skill leverages these dependencies during its information gathering stage to collect system logs before drilling into hypotheses and cross-validating data.

You should not rely solely on sar and last for OS restart diagnosis when hardware faults or kernel panics are suspected. Accurate root-cause analysis requires cross-validating these tools' data with kernel messages and hardware telemetry from ipmitool.