# StorageCluster failing to start (KVDB issues)

**URL:** <https://forums.portworx.com/t/storagecluster-failing-to-start-kvdb-issues/2246>\
**Category:** Portworx on Kubernetes\
**Created:** [August 19, 2025, 4:13pm UTC](https://forums.portworx.com/t/storagecluster-failing-to-start-kvdb-issues/2246 "2025-08-19T16:13:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Craig\_Smith](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/craig_smith/32/862_2.png) [@Craig\_Smith](https://forums.portworx.com/u/Craig_Smith)\
**Post date:** [August 19, 2025, 4:13pm UTC](https://forums.portworx.com/t/storagecluster-failing-to-start-kvdb-issues/2246/1 "2025-08-19T16:13:14Z")

</div>

Hey all, Trying to get to the bottom of this. I am deploying a 3.3.1.1 cluster to my k8s env. Below are the storagecluster manifest and logs I am seeing. There seems to be an issue with me using a logical volume for the metadata drive. I have used this in the past with no issue however. If this is not ideal should I just use standard partitions? I also noticed that it seems to think the nvme1n1 has a size of 0. I have three bare metal nodes and all are the same physical config. Any help would be appreciated.  
[storagecluster.yaml](https://gist.github.com/nctiggy/aeeae73d40d5440bb8f570d1d2d937c2#file-storagecluster-yaml)  
[logs.txt](https://gist.github.com/nctiggy/f5bdc897f9cfc5e5b1b58ac7d51e22da)

---

<div class="post-metadata">

**Author:** ![dcastellani\_portworx](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/dcastellani_portworx/32/856_2.png) [@dcastellani\_portworx](https://forums.portworx.com/u/dcastellani_portworx)\
**Post date:** [August 21, 2025, 4:00pm UTC](https://forums.portworx.com/t/storagecluster-failing-to-start-kvdb-issues/2246/2 "2025-08-21T16:00:46Z")

</div>

@Craig_Smith hi, i believe this is a regression due to the transition from PX-StoreV1 to PX-StoreV2.

There is a bug fix in to support LVM again, though I am not certain which release its tied to.

I would use standard partitions until this shows up in a future release.
