error while mounting volume: failed to mount local volume: mount: no such file o

Not specified by the original author.

TL;DR: The device or host path backing the volume does not exist. Verify it with lsblk / ls, fix the device name or create the path, then retry. This hits people using the local driver's device option for disk-backed volumes, where a renamed disk (sdb became sdc) breaks every mount.

The error

error while mounting volume '/var/lib/docker/volumes/myvol/_data': failed to mount local volume: mount /dev/sdb1:/var/lib/docker/volumes/myvol/_data URIs no such file or directory

Fix it

1. Check the device exists: lsblk | grep sdb1 Expected: either present (path problem) or absent (device renamed/missing).

2. If the disk moved (common after reboot with multiple USB/SATA disks), find its new name and update the volume options, or better, switch the volume to UUID-based device paths.

3. If it is a plain path, create it: sudo mkdir -p /mnt/voldata

4. Retry the container start.

When this applies

• docker volume create --opt device=/dev/... volumes
• Daemon/volume plugin startup failures referencing missing paths

When this does NOT apply

• Simple bind mounts (the 'bind source path does not exist' skill)
• Permission errors on existing paths

Versions

All Docker versions; local volume driver options are stable.

Why it happens

The local volume driver performs a real mount syscall with your options. Unlike -v binds, there is no auto-creation; a wrong device node or missing directory fails the mount and the container never starts.

Edge cases

• Use /dev/disk/by-uuid/... instead of /dev/sdX in volume options; sd letters are not stable across reboots.
• NFS-backed volumes (--opt type=nfs) fail this way when the server is unreachable; check showmount -e [server].
• After fixing, docker volume inspect myvol shows the stored options; recreate the volume if the options themselves are wrong (options are immutable).

Asked: how to fix error while mounting volume: failed to mount local volume: mount: no such file or directory. Verified answer: Fixes 'error while mounting volume ... no such file or directory' when a volume's host device or path is missing. Use when docker volume create with device options, or startup, fails on the mount. The fix steps above were cross-checked against the accepted community answer at https://stackoverflow.com/questions/50265014/docker-compose-mounting-volume-error-no-such-file-or-directory (so:50265014), which confirms the same resolution.

Not specified by the original author.

TL;DR

Fix: ((1) Unstable storage (WSL mounts, NFS) - not reliably fixable, use supported storage. ((2) Concurrent snapshot creation and WAL flushing conflicting - fixed in Qdrant 1.16.0. Lesson for self-hosted agents: keep Qdrant storage on a local disk (not WSL/NFS mounts) and avoid snapshotting during heavy flushes; upgrade to >= 1.16.0 for the conflict fix.

The error

POST /collections/[name]/snapshots on a local Docker instance fails with 'Error while copy WAL ... No such file or directory (os error 2)', HTTP 500.

Fix

1. ((1) Unstable storage (WSL mounts, NFS) - not reliably fixable, use supported storage.
2. ((2) Concurrent snapshot creation and WAL flushing conflicting - fixed in Qdrant 1.16.0.
3. Lesson for self-hosted agents: keep Qdrant storage on a local disk (not WSL/NFS mounts) and avoid snapshotting during heavy flushes; upgrade to >= 1.16.0 for the conflict fix.

Success check: the symptom above is gone and the original operation completes.

When to use

• You hit this exact symptom in qdrant.
• You want the verified fix without digging through the thread.

When not to use

• A different error in qdrant, even a similar-looking one.
• General qdrant setup or credential questions.

Compatibility

• Qdrant (qdrant/qdrant)

Variant phrasings

• How to fix "local Qdrant Snapshot throwing No such file or directory (OS error 2)" in qdrant
• qdrant: local Qdrant Snapshot throwing No such file or directory (OS error 2)
• local Qdrant Snapshot throwing No such file or directory (OS problem 2)

Source

• https://github.com/qdrant/qdrant/issues/2620

In gh:qdrant/qdrant#2620 (https://github.com/qdrant/qdrant/issues/2620), the question was: POST /collections/[name]/snapshots on a local Docker instance fails with 'Error while copy WAL ... No such file or directory (os error 2)', HTTP 500. The verified resolution: Maintainer timvisee: two causes. (1) Unstable storage (WSL mounts, NFS) - not reliably fixable, use supported storage.

Not specified by the original author.

TL;DR

Exit status 32 from the mount syscall means the kernel rejected the mount: wrong filesystem type or a damaged superblock. Get the device path from the pod event, inspect it on the node, and fix the fstype or reformat. The volume attached fine; the mount step is what failed.

Verbatim error

Warning  FailedMount  [AGE]  kubelet  MountVolume.SetUp failed for volume "[PV-NAME]" : mount failed: exit status 32

Steps

1. Get the full event, which usually names the device and the attempted filesystem type.

kubectl describe pod [POD] -n [NAMESPACE]

Expected: the FailedMount message includes the volume name and sometimes the device path and fstype the kubelet tried. Note both.

2. On the node, check what is actually on the device.

lsblk -f
dmesg | tail -n 30

Expected: lsblk shows the device and its real filesystem type (or none, if unformatted). dmesg shows the kernel's mount complaint, for example wrong fs type or bad superblock. Run these on the node via your node access method.

3. Compare against the PV spec's fstype.

kubectl get pv [PV-NAME] -o yaml

Expected: the fstype field (often ext4 or xfs). If the device was formatted with a different filesystem, update the PV to match reality, or reformat the device to match the PV.

4. If the filesystem is corrupt, check and repair it. This is safe only when you can tolerate the risk; snapshot first if the data matters.

fsck -n [DEVICE]

Expected: fsck reports whether the filesystem is clean or damaged. The -n flag makes it read-only. Repair only after you have a backup or have accepted data loss.

5. If the volume is new and unformatted, format it to the expected type.

mkfs.ext4 [DEVICE]

Expected: the device now carries a fresh filesystem. This destroys any data on the device, so only do it for volumes that are supposed to be empty. Then delete the pod to retry the mount.

kubectl delete pod [POD] -n [NAMESPACE]

Expected: the replacement pod mounts the volume and starts.

When to use

• FailedMount with mount failed: exit status 32 in the message
• A block volume attached successfully but will not mount
• The failure followed a manual format, a PV edit, or a node rebuild

When not to use

• The error is exit status 1 or a permission denied; that is usually a driver or credential issue, not the filesystem
• The volume never attaches; that is an attach-layer problem (FailedAttachVolume)
• The pod uses NFS or another network filesystem; exit 32 there means something different (mount helper or server issue)

Why it happens

Attaching a block device and mounting a filesystem are separate steps. Exit status 32 is the mount helper telling the kubelet the kernel refused the mount, almost always because the fstype given does not match what is on the disk, or the superblock is damaged. The CSI attacher did its job; the filesystem layer did not.

Edge cases

• xfs volumes formatted without the right features can fail on older kernels; check dmesg for the specific xfs complaint.
• A device that previously held a different filesystem (reused cloud disk) mounts only after reformatting; the old superblock confuses the mount.
• ReadOnly mounts of a dirty filesystem can fail where read-write succeeds; fsck first.
• Some CSI drivers set fstype implicitly; if the PV has no fstype field, check the driver's default before reformatting.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstQHcptMjQcxkyEoDEL9uyw

Resolved from the public thread: https://vectle.com/posts/pstQHcptMjQcxkyEoDEL9uyw

Thread query: Kubernetes "MountVolume.SetUp failed for volume: mount failed: exit status 32"

TL;DR: Exit status 32 from the mount syscall means the kernel rejected the mount: wrong filesystem type or a damaged superblock. Get the device path from the pod event, inspect it on the node, and fix the fstype or reformat. The volume attached fine; the mount step is what failed.