mount point does not exist (ISCSI)

[lime temple]

I searching for an error on our iscsi backend.

The lun is correct created also an ext4 filesystem is on it.
But I got this error , when it want to mount the lun into the pod.

The facts:

Kubernetes v1.30.12+rke2r1
Ubuntu 24.04.2 LTS
Trident 25.02.1 (ontap-san-economy)

command=mount error="exit status 32" logLayer=csi_frontend output="mount: /srv/kubelet/pods/340fe677-1e4b-4d43-a4ff-f852e1f0bae4/volumes/kubernetes.io~csi/pvc-af4ae845-990c-49ca-9c46-a489c44eb116/mount: mount point does not exist.\n dmesg(1) may have more information after failed mount system call." requestID=8ac70f38-c09b-47ae-a564-fe4b74aad5ef requestSource=CSI workflow="node_server=publish"

thanks for helping me ...

[digital fjord]

make sure that you have installed all required prereqs.

[lime temple]

Yes everithing is installed as documented , includeing iscsi and multipath.conf

[latent silo]

Check the kubelet logs as the kubelet is responsible for creating the path that Trident uses for a mount point.

[lime temple]

There is no error in the kubelet.

Mounts:
/srv1 from pv-storage-1 (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-<redacted> (ro)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready True
ContainersReady True
PodScheduled True
Volumes:
pv-storage-1:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: pvc-storage-1
ReadOnly: false
Events:
Type Reason Age From Message

---

Warning FailedScheduling 18m (x2 over 18m) default-scheduler 0/3 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.
Normal Scheduled 18m default-scheduler Successfully assigned test-namespace/pv-pod to node-01.example.com
Normal SuccessfulAttachVolume 18m attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-<redacted>"
Normal Pulling 18m kubelet Pulling image "nginx"
Normal Pulled 18m kubelet Successfully pulled image "nginx" in 2.533s (2.533s including waiting). Image size: 72225394 bytes.
Normal Created 18m kubelet Created container: pv-container
Normal Started 18m kubelet Started container pv-container

So it seems everithing is totaly fine but the iscsi lun is not mounted.

In the pod it looked like :

/dev/mapper/system-srv on /srv1 type ext4 (rw,relatime)

But that is not the lun.

[latent silo]

"pod has unbound immediate PersistentVolumeClaims" Did the PVC create correctly?

[lime temple]

Yes

kubectl get pvc -n testpvc
apiVersion: v1
items:

• apiVersion: v1
  kind: PersistentVolumeClaim
  metadata:
  annotations:
  pv.kubernetes.io/bind-completed: "yes"
  pv.kubernetes.io/bound-by-controller: "yes"
  volume.beta.kubernetes.io/storage-provisioner: csi.trident.netapp.io
  volume.kubernetes.io/storage-provisioner: csi.trident.netapp.io
  creationTimestamp: "2025-07-10T11:59:46Z"
  finalizers:
  • kubernetes.io/pvc-protection
    name: pvc-storage-1
    namespace: testpvc
    resourceVersion: "8252724"
    uid: b7762f33-06e6-447f-8e73-1b2ea7a74f2f
    spec:
    accessModes:
  • ReadWriteOnce
    resources:
    requests:
    storage: 10Gi
    storageClassName: rwo-iscsi
    volumeMode: Filesystem
    volumeName: pvc-b7762f33-06e6-447f-8e73-1b2ea7a74f2f
    status:
    accessModes:
  • ReadWriteOnce
    capacity:
    storage: 10Gi
    phase: Bound
    kind: List
    metadata:
    resourceVersion: ""

multipath -ll
3600a098038314976625d592f63327265 dm-6 NETAPP,LUN C-Mode
size=10G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| - 35:0:0:0 sdd 8:48 active ready running -+- policy='service-time 0' prio=10 status=enabled
`- 34:0:0:0 sdc 8:32 active ready running

Also on the lun ext4 is on it. I can mount the lun in the clusternode.