# Pod fails to see disk path

**URL:** <https://forums.suse.com/t/pod-fails-to-see-disk-path/16421>\
**Category:** General\
**Created:** [January 26, 2020, 2:49pm UTC](https://forums.suse.com/t/pod-fails-to-see-disk-path/16421 "2020-01-26T14:49:28Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rhugga](https://avatars.discourse-cdn.com/v4/letter/r/71e660/32.png) [@rhugga](https://forums.suse.com/u/rhugga)\
**Post date:** [January 26, 2020, 2:49pm UTC](https://forums.suse.com/t/pod-fails-to-see-disk-path/16421/1 "2020-01-26T14:49:28Z")

</div>

I installed the rook/minio operator and am trying to create a small 4-node minio cluster. I mounted a disk on each of 4 nodes under the path “/kubernetes/disk2”. I labeled each of these 4 nodes with a specific tag. I deployed a 4-node minio cluster.

The pod gets assigned correctly to one of the 4 nodes but it complains it doesn’t find the disk path.

```
MountVolume.NewMounter initialization failed for volume "minio-1-vol02" : path "/kubernetes/disk2" does not exist

```

The persistent volume reaches a bound state:

```
minio-1-vol02 10Gi RWO Retain Bound minio-1/minio-1-data1-minio-1-0 ssd-noraid 18h

```

I also have a mysql pod running using a local disk, created the same way with the same permissions and it’s working fine.

Anyone have any ideas what I’m missing here?

---

<div class="post-metadata">

**Author:** ![jpeake](https://avatars.discourse-cdn.com/v4/letter/j/c0e974/32.png) [@jpeake](https://forums.suse.com/u/jpeake)\
**Post date:** [January 27, 2020, 7:41pm UTC](https://forums.suse.com/t/pod-fails-to-see-disk-path/16421/2 "2020-01-27T19:41:09Z")

</div>

How is the volume mounted to the nodes? Is it NAS of some kind?

---

<div class="post-metadata">

**Author:** ![rhugga](https://avatars.discourse-cdn.com/v4/letter/r/71e660/32.png) [@rhugga](https://forums.suse.com/u/rhugga)\
**Post date:** [January 27, 2020, 8:54pm UTC](https://forums.suse.com/t/pod-fails-to-see-disk-path/16421/3 "2020-01-27T20:54:39Z")

</div>

Nah it’s a local disk. This is a chassis that has 80 internal SSDs.

---

<div class="post-metadata">

**Author:** ![adampl](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/adampl/32/4182_2.png) [@adampl](https://forums.suse.com/u/adampl)\
**Post date:** [October 12, 2020, 8:29am UTC](https://forums.suse.com/t/pod-fails-to-see-disk-path/16421/4 "2020-10-12T08:29:19Z")

</div>

what was the reason? I have the same issue ☹

---

<div class="post-metadata">

**Author:** ![adampl](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/adampl/32/4182_2.png) [@adampl](https://forums.suse.com/u/adampl)\
**Post date:** [October 12, 2020, 12:07pm UTC](https://forums.suse.com/t/pod-fails-to-see-disk-path/16421/5 "2020-10-12T12:07:33Z")

</div>

OK, now I know - dockerized kubelet doesn’t see path on the host, it has to be mapped into kubelet containers in the cluster config:

> **[Extra Args, Extra Binds, and Extra Environment Variables](https://rancher.com/docs/rke/latest/en/config-options/services/services-extras/#extra-binds)**
