> ## Documentation Index
> Fetch the complete documentation index at: https://docs.domino.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# FailedMount event "efs.csi.aws.com not found in the list of registered CSI drivers"

> Troubleshoot the FailedMount "efs.csi.aws.com not found in registered CSI drivers" warning on EKS pods, including how to verify driver installation with kubectl.

## Issue

Admins may see the following warning when describing a pod:

```
Warning FailedMount 55s (x2 over 1m2s) kubelet MountVolume.MountDevice failed for volume "domino-shared-store-domino-compute" : kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient: driver name efs.csi.aws.com not found in the list of registered CSI drivers
```

## Root cause

This warning typically appears only in Elastic Kubernetes Service (EKS) clusters. It's usually temporary — the Container Storage Interface (CSI) driver is still exposing the file system to the node's pods.

If the `FailedMount` warnings stop and the volume mounts successfully, the issue is transient and requires no action.

## Resolution

If `FailedMount` warnings persist and the pod does not mount successfully, follow the steps below.

### Step 1: Confirm the EFS CSI driver is registered

Run the following command to check whether the `efs.csi.aws.com` driver appears in the list of registered CSI drivers:

```
kubectl get csidrivers.storage.k8s.io
```

Verify that `efs.csi.aws.com` appears in the output.

If the driver is not listed, the node may not have been provisioned correctly. Review your EKS node provisioning configuration to confirm the EFS CSI add-on was enabled during cluster or node group setup.

### Step 2: Inspect CSI driver pods

If `efs.csi.aws.com` is listed but the mount failure continues, inspect the CSI-related pods across all namespaces:

```
kubectl get po -A | grep csi
```

For any pods returned, review their descriptions and logs. Include the `kube-system` namespace in your search. Check both the CSI controller pods and the CSI node pod assigned to the same node as your failing pod.

If you need help, contact Technical Support and include your screenshots, pod descriptions, and logs.


## Related topics

- [Troubleshooting](/knowledge-base/troubleshooting-overview.md)
- [Manage External Data Volumes](/cloud/admin/data-administration/external-data/external-data-volumes/index.md)
- [Container & Kubernetes security](/cloud/admin/security-and-compliance/pod-security-policies.md)
- [Set up Domino on EKS, AKS and GKE](/cloud/admin/architecture-and-deployment/architecture/domino-on-eks-aks-gke.md)