Linux Disk Mount Point Not Found – 3 Fixes That Actually Work

Fix #1: The Mount Point Folder Doesn't Exist (Most Common)

This happens way more than you'd think. You add a new hard drive or SSD, run mount /dev/sdb1 /mnt/mydisk, and get back "mount point /mnt/mydisk does not exist." Every time I train a new technician, this is the first thing I check.

The fix is dead simple – you just need to create the folder. Linux won't do it for you automatically.

1. Open a terminal. You can use Ctrl+Alt+T on Ubuntu or just right-click and open terminal.
2. Run sudo mkdir -p /mnt/mydisk. The -p flag creates any parent folders that don't exist, so if /mnt is missing too (rare but happens), it makes that as well.
3. After you run the command, type ls -ld /mnt/mydisk. You should see something like drwxr-xr-x 2 root root 4096 Jan 15 10:30 /mnt/mydisk. If you see that, the folder exists.
4. Now try mounting again: sudo mount /dev/sdb1 /mnt/mydisk.
5. Check if it worked: run df -h | grep /mnt/mydisk. You should see the device name and size, like /dev/sdb1 1.8T 200G 1.6T 12% /mnt/mydisk.

That's it. Nine times out of ten, this is the fix. If you still get the same error after creating the folder, move to the next fix.

Fix #2: The fstab Entry Has the Mount Point Wrong

You might've created the folder but the error pops up at boot. Or you're trying mount -a and it fails. That usually means your /etc/fstab file is pointing to a folder that doesn't exist or is misnamed.

I've seen people type /mnt/my-disk in fstab but create /mnt/mydisk – one little dash makes the whole thing fail.

1. Check your fstab: cat /etc/fstab. Look for the line with your disk's UUID or device name. It looks like UUID=abc123 /mnt/mydisk ext4 defaults 0 2.
2. Verify the mount point folder exists: ls -ld /mnt/mydisk. If it says "No such file or directory", you found the problem. Create it using sudo mkdir -p /mnt/mydisk from Fix #1.
3. If the folder exists, double-check the path in fstab exactly matches. Even a trailing slash can break things. For example, /mnt/mydisk/ vs /mnt/mydisk – I've had users swear they're the same, but Linux treats them differently.
4. Test the mount without rebooting: sudo mount -a. If it runs without errors, you're good. To verify, run mount | grep /mnt/mydisk and look for the device name.
5. If mount -a still fails, check the UUID or device name. Use sudo blkid to see all connected disks and their UUIDs. Your fstab must use the exact UUID from that output.

Real-world example: A client had /dev/sdb1 in fstab, but they unplugged the drive and plugged in a different one. The new drive was /dev/sdc1, so the mount point kept failing. Always use UUID instead of device names – sudo blkid gives you the UUID, paste that into fstab.

Fix #3: The Disk Isn't Even Connected or Recognized

This one is embarrassing when it happens, but we've all been there. You're trying to mount /dev/sdb1, but the drive isn't plugged in or the system doesn't see it. The error message can be misleading – sometimes it says "mount point not found" even though the real issue is the disk is missing.

I once spent 20 minutes troubleshooting a server only to realize the external USB drive was unplugged. Yes, I felt stupid. Learn from my mistake.

1. List all block devices: lsblk. This shows all disks, partitions, and their mount points. Look for your disk. If you expect sdb and it's not there, the disk isn't connected.
2. Check sudo fdisk -l for a detailed list. You'll see sizes and partition types. If your 2TB drive isn't listed, check cables or power.
3. For USB drives, run lsusb to see if the system detects the USB controller. If nothing shows, try a different port or cable.
4. If the disk shows in lsblk but you're still getting the mount point error, run sudo dmesg | tail -20 after plugging in the drive. Look for lines like [ 123.456789] sd 0:0:0:0: [sdb] Attached SCSI disk. If you see errors like I/O error, the disk might be dead.
5. If the disk is detected but not mounted, create the mount point folder (Fix #1) and try sudo mount /dev/sdb1 /mnt/mydisk again.

Pro tip: For external drives that get unplugged and plugged back in, the device name can change. /dev/sdb might become /dev/sdc if another disk is added. That's why UUIDs are safer – they stay the same.

Quick-Reference Summary Table

That's the three reasons this error shows up. Start with Fix #1 – it's the quickest and most common. If that doesn't work, move to Fix #2, then Fix #3. You'll have your disk mounted in under five minutes.