01
Requested storage class is not advertised
The deployment may require a class or storage attribute that the provider inventory does not publish.
Akash provider troubleshooting
Your Akash provider cannot satisfy the requested storage class.
An Akash provider can be healthy and reachable while rejecting workloads that request a storage class, capacity or persistence capability the cluster does not advertise or have available.
Run the free provider checkStorage and inventory matching
Why Akash reports a storage class mismatch
The requested storage type, class and capacity must match the provider inventory and Kubernetes storage configuration. Lower pricing cannot correct a storage mismatch.
02
Persistent versus ephemeral mismatch
The workload may require persistent storage while the provider offers only ephemeral disk, or the reverse.
03
SSD or NVMe requirement mismatch
The order may request SSD, NVMe or another performance class that is absent or named differently in provider inventory.
04
Insufficient available capacity
The correct storage class may exist but lack enough currently available space to satisfy the requested quantity.
05
Kubernetes StorageClass unavailable
The required StorageClass, provisioner or volume-binding configuration may be missing, unhealthy or unable to create volumes.
06
Stale provider inventory
The inventory operator may advertise outdated storage information after disks, classes or Kubernetes resources have changed.
Free diagnosis
What to check when storage requirements do not match
Compare the deployment storage request with the provider inventory, available disk capacity, Kubernetes StorageClass objects and provisioner status.
+Read the deployment storage request
Identify the requested size, persistence type, class and storage attributes.
Identify the requested size, persistence type, class and storage attributes.
+Review advertised provider inventory
Confirm which storage classes, quantities and capabilities the provider publishes.
Confirm which storage classes, quantities and capabilities the provider publishes.
+List Kubernetes StorageClass objects
Verify the required class exists and uses the intended storage provisioner.
Verify the required class exists and uses the intended storage provisioner.
+Check available disk capacity
Confirm the cluster has enough unallocated storage to fulfill the workload.
Confirm the cluster has enough unallocated storage to fulfill the workload.
+Review provisioner and inventory logs
Look for failed volume creation, stale inventory, binding errors or unavailable nodes.
Look for failed volume creation, stale inventory, binding errors or unavailable nodes.
+Submit the mismatch evidence
Use the free checker and include the requested storage details and provider decline message.
Use the free checker and include the requested storage details and provider decline message.
Start with evidence
Find the exact storage mismatch first
Run the free check, review the results and submit the failed items when you need help diagnosing lease declines or provider readiness.
Run the free Akash provider check