Home / Linux / Mount errors
Linux · Filesystem

Fixing /mnt mount errors
in Linux

The most common reasons your drive, NAS share, or network filesystem won't mount — and exactly how to fix each one.

Beginner friendly ~15 min read Linux · fstab · NFS · SMB
On this page

The basics

How mounting works

In Linux, mounting means attaching a filesystem (a disk, partition, network share, or image) to a directory — called a mount point. Typically this is somewhere under /mnt or /media.

bash — basic mount syntax
# Basic syntax
$ mount -t [filesystem] [device] [mountpoint]

# Example: mount an ext4 drive
$ mount -t ext4 /dev/sdb1 /mnt/data

# See what's currently mounted
$ lsblk
$ df -h
$ findmnt
💡 Always create the mount point directory before mounting: mkdir -p /mnt/data. If the directory doesn't exist, the mount command will fail immediately.
Very common
Wrong filesystem type
mount: unknown filesystem type 'ntfs'

Why it happens: Linux needs the right driver/tool to understand a filesystem. NTFS (Windows), exFAT, and HFS+ are not built in by default on most distros.

bash
# First, detect the actual filesystem on the device
$ blkid /dev/sdb1
/dev/sdb1: UUID="3A2F..." TYPE="ntfs"

# Install the right tools for NTFS
$ sudo apt install ntfs-3g # Debian/Ubuntu
$ sudo dnf install ntfs-3g # Fedora/RHEL

# Install for exFAT
$ sudo apt install exfatprogs exfat-fuse

# Now mount with the correct type
$ sudo mount -t ntfs-3g /dev/sdb1 /mnt/data
✓ Mounted successfully
Common
Permission denied
mount: only root can do that

Why it happens: The mount command requires root privileges unless the filesystem or entry in /etc/fstab explicitly allows users.

bash
# Always use sudo for mount
$ sudo mount /dev/sdb1 /mnt/data

# After mounting, fix ownership so your user can write
$ sudo chown -R $USER:$USER /mnt/data

# Or allow any user to mount via fstab (add 'user' option)
/dev/sdb1 /mnt/data ext4 defaults,user,noauto 0 0
⚠️ Don't chmod 777 /mnt/data as a quick fix — this opens the mountpoint to all users. Use chown to assign the correct owner instead.
Common
Device or resource busy
umount: /mnt/data: target is busy

Why it happens: Something — a process, an open terminal, or a background service — still has a file open on the mounted filesystem. You can't unmount it until everything lets go.

bash
# Find what's using the mountpoint
$ lsof +f -- /mnt/data
COMMAND PID USER FD TYPE NAME
bash 2341 alex cwd DIR /mnt/data

# Or use fuser
$ fuser -m /mnt/data
/mnt/data: 2341

# Kill the blocking processes and retry
$ fuser -km /mnt/data
$ sudo umount /mnt/data
✓ Unmounted

# Last resort: lazy unmount (detaches when free)
$ sudo umount -l /mnt/data
Easy fix
No such file or directory
mount: /mnt/data: special device /dev/sdb1 does not exist

Why it happens: The device path is wrong, the drive isn't plugged in, or Linux assigned it a different letter (sda vs sdb).

bash
# List all block devices to find the right one
$ lsblk -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT
NAME SIZE FSTYPE LABEL MOUNTPOINT
sda 500G
├─sda1 512M vfat EFI /boot/efi
└─sda2 500G ext4 root /
sdb 4T
└─sdb1 4T ext4 NAS-data

# Use UUID instead of /dev/sdX — it never changes
$ blkid /dev/sdb1
/dev/sdb1: UUID="a1b2c3d4-..." TYPE="ext4"
$ sudo mount UUID="a1b2c3d4-..." /mnt/data
💡 Device names like /dev/sdb can change between reboots. Always use UUID in /etc/fstab to keep mounts stable.

Boot-time mounts

fstab errors on boot

The /etc/fstab file defines what gets mounted at boot. A typo here can prevent your system from booting. Here's the field breakdown:

Field Example What it means
Device UUID=a1b2c3... What to mount. Use UUID, never /dev/sdX
Mount point /mnt/data Where to attach it. Must exist before boot
Type ext4 Filesystem: ext4, ntfs-3g, nfs, cifs, etc.
Options defaults,nofail Mount flags. Use nofail for non-essential drives
Dump 0 Backup via dump — almost always 0
Pass 2 fsck order: 0 = skip, 1 = root, 2 = others
/etc/fstab — safe NAS drive entry
# A safe fstab entry for a local NAS data drive
UUID=a1b2c3d4-e5f6-... /mnt/data ext4 defaults,nofail,x-systemd.device-timeout=5 0 2

# Test your fstab BEFORE rebooting
$ sudo mount -a
✓ No output = no errors

# Recover from a broken fstab (boot into rescue mode, then)
$ sudo mount -o remount,rw /
$ nano /etc/fstab
⚠️ Always add nofail to any non-root drive in fstab. Without it, a missing or faulty drive will drop your system into emergency mode on boot.

Network mounts

NFS & SMB share errors

Mounting a NAS share over the network adds another layer of failure points: firewall, service state, DNS, and protocol version all matter.

bash — mount NFS share
# Install NFS client
$ sudo apt install nfs-common

# Mount an NFS share
$ sudo mount -t nfs 192.168.1.10:/volume1/data /mnt/nas

# If it hangs or fails — check the NFS server is exporting
$ showmount -e 192.168.1.10
Export list for 192.168.1.10:
/volume1/data 192.168.1.0/24

# Force NFS version if auto-negotiation fails
$ sudo mount -t nfs -o vers=4 192.168.1.10:/volume1/data /mnt/nas
bash — mount SMB/CIFS share
# Install CIFS utilities
$ sudo apt install cifs-utils

# Mount a Samba/Windows share
$ sudo mount -t cifs //192.168.1.10/data /mnt/nas \
  -o username=admin,password=secret,vers=3.0

# Use a credentials file instead (safer — no password in history)
# Create /etc/nas-credentials:
username=admin
password=secret
$ sudo chmod 600 /etc/nas-credentials
$ sudo mount -t cifs //192.168.1.10/data /mnt/nas \
  -o credentials=/etc/nas-credentials,vers=3.0
✓ Mounted

Reference

Quick cheatsheet

mount commands — copy & paste
# See all mounted filesystems
$ findmnt --real

# Identify a disk and its filesystem
$ lsblk -f
$ blkid /dev/sdb1

# Mount read-only (safe for investigation)
$ sudo mount -o ro /dev/sdb1 /mnt/data

# Remount as read-write
$ sudo mount -o remount,rw /mnt/data

# Unmount safely
$ sudo umount /mnt/data

# Test all fstab entries without rebooting
$ sudo mount -a && echo "fstab OK"

# Run fsck on an unmounted drive (fixes corruption)
$ sudo fsck -y /dev/sdb1

Keep going

Related guides

Up next
Setting up /etc/fstab for persistent NAS mounts
→
Related
Fixing SMB disconnects on Windows 11 with TrueNAS
→
Related
Tailscale for secure remote NAS access
→