block-dm-raid-diagnosis

Diagnose block device, Device-Mapper, RAID, LVM, and multipath configurations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a systematic, non-destructive diagnostic framework for complex storage stack issues, including block device IO bottlenecks, Device-Mapper errors, RAID degradation, and LVM/multipath failures.

Core Features & Use Cases

  • Three-Stack Analysis: Automatically drills down through the block layer, DM/MD mapping stack, and physical device layer to isolate root causes.
  • Expert-Guided Troubleshooting: Implements a rigorous, read-only diagnostic workflow that prevents accidental data loss while providing actionable repair recommendations.
  • Use Case: When a production server reports high IO wait times or filesystem read-only errors, this Skill identifies whether the issue stems from a failing physical disk, a degraded RAID array, or a misconfigured IO scheduler.

Quick Start

Use the block-dm-raid-diagnosis skill to analyze the storage stack for device sdb after a reported IO error.

Frequently Asked Questions about block-dm-raid-diagnosis

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

FAQPage Schema
How do I diagnose high IO wait times and filesystem read-only errors in Linux?

Diagnose high IO wait times by performing a three-stack block layer, Device-Mapper, and physical device analysis to isolate whether the bottleneck stems from failing hardware or a misconfigured IO scheduler.

What is the best way to troubleshoot Device-Mapper and LVM mapping inconsistencies?

Troubleshoot Device-Mapper and LVM mapping inconsistencies by drilling down through the DM/MD mapping stack and logical volume status to identify misconfigurations and resolve IO bottlenecks non-destructively.

Can I use a read-only diagnostic workflow to identify software RAID degradation without risking data loss?

Yes, you can safely identify software RAID degradation using a rigorous read-only diagnostic workflow that prevents accidental data loss while providing actionable repair recommendations.

Does this Linux storage diagnostics approach require Ansible to run?

Yes, this Linux storage diagnostics approach requires Ansible as a dependency to automate the comprehensive analysis of block devices, multipath configurations, and software RAID stacks.

How do I isolate whether a storage IO bottleneck originates from physical hardware or logical volume configurations?

Isolate storage IO bottlenecks by correlating kernel-level IO errors with physical hardware health and logical volume status through a layered analysis across the block layer and DM stack.