# Volume mount failed on iSCSI **URL:** \ **Category:** Percona Operator for MongoDB\ **Created:** [April 15, 2022, 7:53am UTC](https://forums.percona.com/t/volume-mount-failed-on-iscsi/15252 "2022-04-15T07:53:42Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Gloria\_Pedemonte](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/gloria_pedemonte/32/6322_2.png) [@Gloria\_Pedemonte](https://forums.percona.com/u/Gloria_Pedemonte)\ **Post date:** [April 15, 2022, 7:53am UTC](https://forums.percona.com/t/volume-mount-failed-on-iscsi/15252/1 "2022-04-15T07:53:42Z")
Hello everyone. I tried to install Percona operator on k3s. I edited the crd manifest to use a storage class I had previously created with Trident to interface with two ONTAP iSCSI disks. I had already verified that volumes pertaining to this storage class could be successfully mounted on ordinary pods. Nevertheless, when I tried to deploy the modified crd manifest I got the following output. ```auto Warning FailedMount 31m (x73 over 13h) kubelet Unable to attach or mount volumes: unmounted volumes=[mongod-data], unattached volumes=[mongod-data kube-api-access-9kwgq my-cluster-name-mongodb-keyfile ssl ssl-internal my-cluster-name-mongodb-encryption-key]: timed out waiting for the condition Warning FailedMount 15m (x43 over 13h) kubelet Unable to attach or mount volumes: unmounted volumes=[mongod-data], unattached volumes=[ssl-internal my-cluster-name-mongodb-encryption-key mongod-data kube-api-access-9kwgq my-cluster-name-mongodb-keyfile ssl]: timed out waiting for the condition Warning FailedMount 10m (x67 over 13h) kubelet Unable to attach or mount volumes: unmounted volumes=[mongod-data], unattached volumes=[my-cluster-name-mongodb-encryption-key mongod-data kube-api-access-9kwgq my-cluster-name-mongodb-keyfile ssl ssl-internal]: timed out waiting for the condition Warning FailedMount 6m17s (x57 over 12h) kubelet Unable to attach or mount volumes: unmounted volumes=[mongod-data], unattached volumes=[kube-api-access-9kwgq my-cluster-name-mongodb-keyfile ssl ssl-internal my-cluster-name-mongodb-encryption-key mongod-data]: timed out waiting for the condition Warning FailedMount (x247 over 13h) kubelet MountVolume.MountDevice failed for volume "pvc-4e91d600-7d68-43c9-b27a-461e85b7f444" : rpc error: code = Internal desc = no devices present yet ``` Have you got any clue about the reason why it’s happening? Thank you a lot for your attention. Other contextual information: - k3s v. 1.21.3 - Trident v. 21.04 - Percona operator v. 4.4.3-5 ---
**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\ **Post date:** [April 15, 2022, 9:02am UTC](https://forums.percona.com/t/volume-mount-failed-on-iscsi/15252/2 "2022-04-15T09:02:12Z")
Hey @Gloria_Pedemonte , well, it says that storage device is not there. What do you see in `kubectl get pvc` ? Were volumes created already? ---
**Author:** ![Gloria\_Pedemonte](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/gloria_pedemonte/32/6322_2.png) [@Gloria\_Pedemonte](https://forums.percona.com/u/Gloria_Pedemonte)\ **Post date:** [April 15, 2022, 11:35am UTC](https://forums.percona.com/t/volume-mount-failed-on-iscsi/15252/3 "2022-04-15T11:35:19Z")
Thank you for your answer, @Sergey_Pronin . Yes, the pvc has been created and bound. Moreover, if I run `kubectl describe pvc` it appears used by the first mongo pod. ---
**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\ **Post date:** [April 15, 2022, 1:51pm UTC](https://forums.percona.com/t/volume-mount-failed-on-iscsi/15252/4 "2022-04-15T13:51:09Z")
Operator does not do much magic here. It provisions statefulset, statefulset has specific storage class for volume in the volume spec. Does trident work for other pods? ---
**Author:** ![Gloria\_Pedemonte](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/gloria_pedemonte/32/6322_2.png) [@Gloria\_Pedemonte](https://forums.percona.com/u/Gloria_Pedemonte)\ **Post date:** [April 15, 2022, 2:54pm UTC](https://forums.percona.com/t/volume-mount-failed-on-iscsi/15252/6 "2022-04-15T14:54:32Z")
It does work for other pods. ---
**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\ **Post date:** [April 18, 2022, 8:43am UTC](https://forums.percona.com/t/volume-mount-failed-on-iscsi/15252/7 "2022-04-18T08:43:43Z")
Hello @Gloria_Pedemonte I don’t have trident env to reproduce. We will be able to help if you share more details - Pods, PVCs, Statefulsets statuses, describes, yamls, etc. Also please let me know what you have already tried and what you see. ---
**Author:** ![Gloria\_Pedemonte](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/gloria_pedemonte/32/6322_2.png) [@Gloria\_Pedemonte](https://forums.percona.com/u/Gloria_Pedemonte)\ **Post date:** [April 21, 2022, 11:35am UTC](https://forums.percona.com/t/volume-mount-failed-on-iscsi/15252/8 "2022-04-21T11:35:47Z")
Hello again @Sergey_Pronin, sorry for the belated answer. I discovered this same problem extends to other stetefulsets, so it’s probably more like a trident-related issue. I will post updates as soon as there are any. Thank you for your time.