# Diagnose Storage Issue

> Diagnose storage and persistent volume issues. Checks PVC binding, storage class configuration, and volume mount status. Use when pods are stuck pending due to volume issues. Keywords: PVC, PV, storage, volume, pending, mount, storage class.

- Skill: `majiayu000/diagnose-storage-issue` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/diagnose-storage-issue`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/diagnose-storage-issue/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/diagnose-storage-issue

---


# Diagnose Storage Issue

## Preconditions

Before applying this skill, verify:

- PVC name or pod name is known
- Namespace is specified
- Storage issue symptoms observed

## Actions

### 1. Get PVC Status

Check PersistentVolumeClaim binding status.

```yaml
mcp_tool: kubernetes-mcp-server/resources_get
params:
  apiVersion: v1
  kind: PersistentVolumeClaim
  name: $pvc_name
  namespace: $namespace
timeout: 30s
```

### 2. Get PV Details

Check bound PersistentVolume if exists.

```yaml
mcp_tool: kubernetes-mcp-server/resources_list
params:
  apiVersion: v1
  kind: PersistentVolume
timeout: 30s
```

### 3. Check Storage Classes

Verify storage class exists and is configured.

```yaml
mcp_tool: kubernetes-mcp-server/resources_list
params:
  apiVersion: storage.k8s.io/v1
  kind: StorageClass
timeout: 30s
```

### 4. Get Pod Volume Mounts

Check pod's volume mount status.

```yaml
mcp_tool: kubernetes-mcp-server/pods_get
params:
  name: $pod_name
  namespace: $namespace
timeout: 30s
```

### 5. Check Events

Look for storage-related events.

```yaml
mcp_tool: kubernetes-mcp-server/events_list
params:
  namespace: $namespace
timeout: 30s
```

## Success Criteria

The skill succeeds when:

- [ ] PVC status determined (Bound/Pending/Lost)
- [ ] Storage class availability confirmed
- [ ] Root cause identified

## Failure Handling

If storage issue cannot be resolved:

1. Check CSI driver logs
2. Verify node has available storage
3. Escalate with volume details

## Examples

**Input Context:**
```json
{
  "pvc_name": "data-volume",
  "namespace": "default",
  "pod_name": "db-pod-abc123"
}
```

**Output:**
```json
{
  "pvc_status": "Pending",
  "pv_bound": false,
  "storage_class": "local-path",
  "diagnosis": "No available PV matching storage class requirements",
  "recommendation": "Create PV with matching storage class or use dynamic provisioning"
}
```