From the logs it looks the disk which you provisioned is already in use:
@k8s-master portworx[6628]: Device is in use: /dev/vdb1, skipping...
@k8s-master portworx[6628]: Head node:
@k8s-master portworx[6628]: No disks specified, starting as a storage-less node.
Portworx needs a raw disk (unformated) additional disk, you cannot use your root disk.
Can you share your lsblk and blkid output from worker node.
Hello @ryzam, thank you for posting on Portworx forums ! The logs you shared were useful.
PX failed to come up because you provided /dev/vdb1 as a disk but this disk appears to be in use.
These logs indicate this
Input arguments: /px-oci-mon -c px-cluster-0126654e-078b-475a-90ac-f4043abf2ac0 -s /dev/vdb1 -secret_type k8s -j auto -b --oem esse -x kubernetes"
...
@k8s-master portworx[6628]: Device is in use: /dev/vdb1, skipping...
The disk you provide to Portworx needs to be unmounted and should not have a filesystem on it. Can you upload output of lsblk and blkid from this node and we can confirm that /dev/vdb1 is in use by something else in the system.
vdb 252:16 0 10G 0 disk
└─vdb1 252:17 0 10G 0 part /disk2
I think this is what your giving backing disk for portworx, this doesn’t needs to be formated.
Make sure disk is not formatted and you deleted the partitions and clean up the traces on disk with wipefs -a /dev/vdb. Also if you can provision 50G of disk would be good.
Before proceeding clean up the portworx install and once your ready with above changes apply your spec file again.
Here is the command for cleanup : curl -fsL https://install.portworx.com/px-wipe | bash
Can you share the output of following:
1- Describe the pod share the output
2- lsblk & blkid output
3 - Login to one of worker node and collect journalctl -lu portworx* > node.logs and share it.
4 - Spec file used for installation. The output above is showing oci-mon:2.4, Did you tried to install 2.4 version of portworx ?