// Module included in the following assemblies:
//
// storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc

:_mod-docs-content-type: PROCEDURE
[id="recovering-from-missing-lvms-or-operator-components_{context}"]
= Recovering from a missing storage class

[role="_abstract"]
Resolve the "storage class not found" error by verifying that the LVMCluster custom resource (CR) exists and all {lvms-first} pods are running, then reviewing logs to identify configuration issues.

.Prerequisites
* You have installed the {oc-first}.
* You have logged in to the {oc-first} as a user with `cluster-admin` permissions.

.Procedure
. Verify that the `LVMCluster` CR is present by running the following command:
+
[source,terminal]
----
$ oc get lvmcluster -n <namespace>
----
+
.Example output
[source,terminal]
----
NAME            AGE
my-lvmcluster   65m
----

. If the `LVMCluster` CR is not present, create an `LVMCluster` CR. For more information, see "Ways to create an LVMCluster custom resource".

. In the namespace where the operator is installed, check that all the {lvms} pods are in the `Running` state by running the following command:
+
[source,terminal]
----
$ oc get pods -n <namespace>
----
+
.Example output
[source,terminal]
----
NAME                                  READY   STATUS    RESTARTS      AGE
lvms-operator-7b9fb858cb-6nsml        3/3     Running   0             70m
topolvm-controller-5dd9cf78b5-7wwr2   5/5     Running   0             66m
topolvm-node-dr26h                    4/4     Running   0             66m
vg-manager-r6zdv                      1/1     Running   0             66m
----
+
The output of this command must contain a running instance of the following pods:

* `lvms-operator`
* `vg-manager`
+
If the `vg-manager` pod is stuck while loading a configuration file, it is due to a failure to locate an available disk for {lvms} to use. To retrieve the necessary information to troubleshoot this issue, review the logs of the `vg-manager` pod by running the following command:
+
[source,terminal]
----
$ oc logs -l app.kubernetes.io/component=vg-manager -n <namespace>
----
