offline-file-system-fault-diagnosis

Name: offline-file-system-fault-diagnosis
Availability: InStock
Author: openEuler

Correlate iBMC hardware logs, OS messages, and InfoCollect data to diagnose Linux file system failures.

3|2|Updated Apr 24, 2026

Search Tags:#diagnosis #linux #storage #log-analysis #file-system #openeuler

Ready to run

npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill offline-file-system-fault-diagnosis-openeuler-mirror

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: offline-file-system-fault-diagnosis
Source: https://github.com/openeuler-mirror/witty-diagnosis-agent/tree/main/skills/offline-file-system-fault-diagnosis
Command: npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill offline-file-system-fault-diagnosis-openeuler-mirror

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill resolves the complexity of diagnosing Linux file system (EXT4/XFS) and storage-related failures by automating the analysis of fragmented server logs, including iBMC, OS messages, and InfoCollect data.

Core Features & Use Cases

Multi-Source Log Correlation: Automatically aligns iBMC hardware events with OS-level kernel messages to reconstruct the exact failure timeline.
Root Cause Localization: Pinpoints specific physical disk slots or logical block offsets causing metadata corruption or I/O errors.
Use Case: When a production server reports a read-only file system or mount failure, this skill analyzes the provided log bundle to determine if the root cause is a physical disk bad block, a RAID controller failure, or a logical file system inconsistency.

Quick Start

Use the offline-file-system-fault-diagnosis skill to analyze the server logs located in the directory /tmp/logs.

Frequently Asked Questions about offline-file-system-fault-diagnosis

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

FAQPage Schema

How do I diagnose Linux file system corruption and I/O errors from server logs?▼

To diagnose Linux file system corruption and I/O errors, you can analyze server log bundles containing iBMC, OS messages, and InfoCollect data to correlate hardware events with kernel messages and pinpoint failing disk slots.

What is the best way to find the root cause of an EXT4 or XFS mount failure?▼

Finding the root cause of EXT4 or XFS mount failures requires aligning iBMC hardware events with OS-level kernel logs to determine if the trigger is a physical disk bad block, a RAID controller failure, or a logical inconsistency.

Why does my Linux production server suddenly report a read-only file system?▼

A Linux read-only file system often indicates underlying storage subsystem failures. By analyzing log time-series data, you can reconstruct the failure timeline and map the mount point to a specific physical hardware component causing the fault.

Can I trace logical file system metadata errors to specific physical disk slots?▼

Yes, you can trace logical file system metadata errors to specific physical disk slots by correlating multi-source server logs, which aligns hardware events with logical block offsets to localize the exact physical component.

How do I analyze server logs in a specific directory to troubleshoot storage subsystem failures?▼

You can troubleshoot storage subsystem failures by running a diagnostic analysis on server logs located in a specific directory, such as /tmp/logs, to automatically process iBMC hardware logs and OS messages.

Does offline file system fault diagnosis work without an active internet connection?▼

Yes, offline diagnosis works without an active internet connection because the skill relies on scripts and references to locally analyze pre-collected server log bundles, including iBMC and InfoCollect data.