Failed to obtain node locks, tried [[/opt/opensearch/data]] with lock id [0]

@YaswaniT Forcing the deletion of the pod and not allowing the service to stop gracefully could cause the reported issue. If you take a look at the data of the related PVC, you’ll find a file node.lock in <PV_data_folder>/nodes/0/
This file should be removed whenever you stop the service gracefully. Because you’ve forced it, the file remained.

Do you have snapshots/backups of those indices?

I’ve reproduced your issue. When I removed the node.lock file, the OpenSearch pod started again.