# Error: MountVolume.SetUp failed for volume with error: Unknown/Unhandled OS type **URL:** \ **Category:** Portworx on Kubernetes\ **Created:** [June 1, 2020, 6:05pm UTC](https://forums.portworx.com/t/error-mountvolume-setup-failed-for-volume-with-error-unknown-unhandled-os-type/427 "2020-06-01T18:05:50Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![dgrekov](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/dgrekov/32/156_2.png) [@dgrekov](https://forums.portworx.com/u/dgrekov)\ **Post date:** [June 1, 2020, 6:05pm UTC](https://forums.portworx.com/t/error-mountvolume-setup-failed-for-volume-with-error-unknown-unhandled-os-type/427/1 "2020-06-01T18:05:50Z")
I have been following the tutorials to set up Portworx on a Flatcar Container Linux Kubernetes Cluster on bare-metal. When trying to mount the volume to a pod I get the following error: MountVolume.SetUp failed for volume “pvc-faf1e7ac-13e1-4e81-b1e8-1b55cf0361b6” : rpc error: code = Internal desc = failed to attach volume: cannot attach volume as NFS installation failed on this node [ID: 9ca3418a-8716-4552-8516-d6be206b2e3b] [IP: xxx.xxx.xxx.xxx] with error: Unknown/Unhandled OS type Does anyone know what is causing this issue? ---
**Author:** ![adityadani](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/adityadani/32/128_2.png) [@adityadani](https://forums.portworx.com/u/adityadani)\ **Post date:** [June 1, 2020, 6:16pm UTC](https://forums.portworx.com/t/error-mountvolume-setup-failed-for-volume-with-error-unknown-unhandled-os-type/427/2 "2020-06-01T18:16:13Z")
Looks like you are trying to use sharedv4 volumes. Until 2.5.2 they were not supported on Flatcar OS. Can you upgrade your cluster to use the latest Portworx version 2.5.2 ? ---
**Author:** ![dgrekov](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/dgrekov/32/156_2.png) [@dgrekov](https://forums.portworx.com/u/dgrekov)\ **Post date:** [June 1, 2020, 6:45pm UTC](https://forums.portworx.com/t/error-mountvolume-setup-failed-for-volume-with-error-unknown-unhandled-os-type/427/3 "2020-06-01T18:45:21Z")
@adityadani, Oh wow, that version is only 3 days old and I pulled my spec just a day or two before that. Talk about bleeding edge. Will try it now. Thank you. ---
**Author:** ![dgrekov](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/dgrekov/32/156_2.png) [@dgrekov](https://forums.portworx.com/u/dgrekov)\ **Post date:** [June 1, 2020, 8:31pm UTC](https://forums.portworx.com/t/error-mountvolume-setup-failed-for-volume-with-error-unknown-unhandled-os-type/427/4 "2020-06-01T20:31:05Z")
That did it. Thank you very much! One remaining question. For me to be able to access a volume from outside of k8s for example for maintenance does it need to be sharedv4 or is there a different way as well? ---
**Author:** ![adityadani](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/adityadani/32/128_2.png) [@adityadani](https://forums.portworx.com/u/adityadani)\ **Post date:** [June 1, 2020, 8:58pm UTC](https://forums.portworx.com/t/error-mountvolume-setup-failed-for-volume-with-error-unknown-unhandled-os-type/427/5 "2020-06-01T20:58:57Z")
Yes sharedv4 will be the right kind of volume if you want to access the volume from outside the kubernetes cluster. This forum post will guide you on how to do it: > [@NFS External Exporter Script | How to export Sharedv4 volume to an external node as NFS target](https://forums.portworx.com/t/nfs-external-exporter-script-how-to-export-sharedv4-volume-to-an-external-node-as-nfs-target/422): > > This document describes how to export Portworx sharedv4 (ReadWriteMany) volumes in your Kubernetes cluster to an external node / host. Sharedv4 volumes are useful when you want multiple PODs to access the same PVC (volume) at the same time. They can use the same volume even if they are running on different hosts. They provide a global namespace and the semantics are POSIX compliant. The basic steps are to create a SharedV4 StorageClass, PVC and Pod that will attach and mount the PV to one of t… Also if you plan to do this only during a maintenance window you can convert a regular RWO volume into a sharedv4 (RWX) volume. The following commands can be used to update a volume type when the volume is **Not Attached (Not in Use)** ```plaintext ## To turn on sharedv4 /opt/pwx/bin/pxctl volume update --sharedv4=on ## Perform maintenance and access the volume outside of k8s ## Once maintenance is done turn the volume back into a regular volume ## To turn off sharedv4 /opt/pwx/bin/pxctl volume update --sharedv4=off ```