offline-disk-fault-diagnosis

Analyzes iBMC, OS, and FARM logs to diagnose disk failures and classify R1-R16 root causes.

3|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill offline-disk-fault-diagnosis-openeuler-mirror
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: offline-disk-fault-diagnosis
Source: https://github.com/openeuler-mirror/witty-diagnosis-agent/tree/main/skills/offline-disk-fault-diagnosis
Command: npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill offline-disk-fault-diagnosis-openeuler-mirror

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the complexity of diagnosing storage subsystem failures by correlating multi-source logs—iBMC, OS, and FARM—to pinpoint root causes in offline disks, RAID controllers, and storage links.

Core Features & Use Cases

  • Multi-Source Correlation: Automatically aligns iBMC hardware events, OS kernel logs, and FARM telemetry to reconstruct fault timelines.
  • Deep Root Cause Analysis: Identifies specific hardware failure modes (R1-R16) including head degradation, vibration, and link instability.
  • Use Case: When a server reports a degraded RAID array or file system read-only errors, this Skill analyzes the provided log package to determine if the issue is a failing disk head, a faulty backplane, or a transient link reset, providing actionable repair steps.

Quick Start

Use the offline-disk-fault-diagnosis skill to analyze the server logs located in the /tmp/logs directory and generate a comprehensive root cause report.

Frequently Asked Questions about offline-disk-fault-diagnosis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose root causes of offline disk failures from server logs?

You can diagnose offline disk failures by correlating server storage logs like iBMC, OS messages, and FARM telemetry. This process aligns multi-source time-series data to pinpoint specific hardware failure modes and generate actionable repair recommendations.

Why does my RAID array report a degraded state and how can I analyze it?

A degraded RAID array often indicates disk hardware or link-level failures. Analyzing OS kernel logs and FARM telemetry with diagnostic scripts helps identify specific failure modes like head degradation or link instability to determine exact repair steps.

What is multi-source time-series alignment for hardware fault diagnosis?

Multi-source time-series alignment is the process of correlating iBMC hardware events, OS logs, and FARM telemetry. It reconstructs fault timelines to classify root causes based on defined R1-R16 failure modes for storage subsystems.

Can I run disk fault diagnosis scripts with Python 3 on openEuler?

Yes, you can execute disk fault diagnosis workflows using Python 3 and standard log parsing scripts. It analyzes log packages on openEuler systems to diagnose hardware failures in offline disks, RAID controllers, and storage links.

Does storage log analysis distinguish between a failing disk head and a faulty backplane?

Yes, deep root cause analysis of storage logs identifies specific hardware failure modes including head degradation, vibration, and link instability. It determines whether degraded array issues stem from a failing disk, faulty backplane, or transient link reset.

What logs are required to classify R1-R16 disk failure modes?

Classifying R1-R16 disk failure modes requires server-level storage logs including iBMC hardware events, OS kernel messages, and FARM telemetry. These multi-source logs are aligned to accurately diagnose hardware and link-level disk failures.