# MountVolume.SetUp failed for volume "pvc-xxx" : rpc error: code = Internal desc = rpc error: code = Internal desc = mount failed: exit status 32

- **ID:** `kubernetes/failed-to-mount-volume`
- **Domain:** kubernetes
- **Category:** runtime_error
- **Error Code:** `ExitStatus32`
- **Verification:** ai_generated
- **Fix Rate:** 80%

## Root Cause

The CSI driver or node filesystem fails to mount the persistent volume, often due to incorrect filesystem type, corrupted disk, or missing mount utilities on the node.

## Workarounds

1. **Check the node's filesystem and repair it: ssh to the node and run 'sudo fsck -y /dev/<device>' or 'sudo xfs_repair /dev/<device>' if using XFS.** (75% success)
   ```
   Check the node's filesystem and repair it: ssh to the node and run 'sudo fsck -y /dev/<device>' or 'sudo xfs_repair /dev/<device>' if using XFS.
   ```
2. **Ensure the 'nfs-common' or 'cifs-utils' package is installed on the node: 'sudo apt-get install -y nfs-common' for NFS volumes.** (85% success)
   ```
   Ensure the 'nfs-common' or 'cifs-utils' package is installed on the node: 'sudo apt-get install -y nfs-common' for NFS volumes.
   ```

## Dead Ends

- **Restart the kubelet service on the node** — Kubelet restart doesn't repair underlying filesystem issues or CSI driver bugs; the mount operation still fails. (80% fail)
- **Delete and recreate the PersistentVolumeClaim** — The PVC is bound to a specific PV; recreating it doesn't fix the node-level mount failure unless the underlying volume is repaired. (70% fail)