Resolving Storage Failures

Resolving Storage Failures

While installing the software, you might find that some of your pods are stuck in the
Pending
state. This is often due to storage issues.
Check the state of your PersistentVolumeClaims (PVCs):
kubectl get pvc
If the PVCs show a status of
Pending
, describe the PVC to see the reason:
kubectl describe pvc <pvc name>
Under the
Events
section, you will see the reason for the PVC being stuck in the
Pending
state.
You might see that the error is due to the storage controller not being able to create the volume. This could be due to an issue with the storage controller.
If you are using a multi-node deployment with
Rook
, you can check the status of the storage pods in the
rook-ceph
namespace:
kubectl get pods -n rook-ceph
All pods should show as either
Completed
, or
Running and ready
.
If the storage pods are not running, you can check the logs for the pods to see if there are any errors:
kubectl logs <pod name> -n rook-ceph
The operator
pod rook-ceph-operator-*
frequently logs errors that can help you identify the issue.