Linux Mount Error — Unable to Mount Drive Fix

What Does This Error Mean?

A Linux mount error means the system cannot attach a drive or partition to the file system so you can access it. You might see messages like 'mount: wrong fs type, bad option' or 'mount: can't read superblock' or 'mount: special device does not exist.' This is caused by a bad file system, a missing driver, or specifying the wrong device path.

Affected Models

Ubuntu
Debian
Fedora
CentOS
Arch Linux
Linux Mint
openSUSE

Common Causes

The partition has file system errors and needs to be repaired with fsck before mounting
The required file system driver is not installed (for example, ntfs-3g for NTFS drives)
The device path is wrong — specifying /dev/sdb1 when the drive is actually /dev/sdc1
The drive was not safely ejected previously and has a 'dirty' flag that prevents mounting
The mount point directory does not exist yet and needs to be created

How to Fix It

Find the correct device name. Run: lsblk or sudo fdisk -l to list all connected drives and partitions. Note the exact device name (like /dev/sdb1) for the drive you want to mount.

Device names can change between boots. A drive that was /dev/sdb yesterday might be /dev/sdc today if another drive was added.
Create the mount point if it does not exist. Run: sudo mkdir -p /mnt/mydrive (replace 'mydrive' with whatever name you want). Then mount: sudo mount /dev/sdb1 /mnt/mydrive

A mount point is just an empty folder. Linux attaches the drive's contents to that folder location.
Install missing file system support. For Windows NTFS drives: sudo apt install ntfs-3g. For exFAT drives: sudo apt install exfat-fuse exfatprogs. Then retry mounting.

Linux does not include drivers for all file system types by default. NTFS and exFAT are commonly used on Windows drives and external storage.
Run fsck to repair the partition. First make sure the drive is unmounted: sudo umount /dev/sdb1. Then run: sudo fsck -y /dev/sdb1

Never run fsck on a mounted partition — it can cause data loss. The -y flag automatically answers yes to all repair prompts.
Force mount a dirty NTFS partition. If an NTFS drive shows 'Windows is hibernating' or 'dirty flag set,' run: sudo mount -t ntfs-3g -o remove_hiberfile /dev/sdb1 /mnt/mydrive

A Windows drive that was hibernated (not shut down cleanly) will refuse to mount in read-write mode. This command overrides that protection — only use it if you know Windows is not using the drive.

When to Call a Professional

Mount errors are usually fixable with the terminal commands below. If fsck finds errors it cannot repair or the drive is not recognized at all by the kernel, the hardware may be failing. Physical drive problems require professional data recovery if the data cannot be backed up first.

Frequently Asked Questions

What does 'can't read superblock' mean?

The superblock is a small section at the beginning of a partition that stores information about the file system structure. If it is corrupted, Linux cannot understand the partition. Linux keeps backup superblocks — run: sudo fsck -b [backup-superblock-location] /dev/sdb1 to try recovering using a backup.

How do I make a drive mount automatically at startup?

Edit the /etc/fstab file to add an entry for the drive. Each line in fstab specifies a device, mount point, file system type, and options. Use the drive's UUID (found with: blkid) instead of /dev/sdX to ensure the correct drive is always mounted.

My drive mounted but I can only read it, not write to it. Why?

This usually means the partition was mounted in read-only mode. For NTFS drives, this often happens because Windows hibernated rather than fully shutting down. For Linux partitions, read-only mounting usually indicates file system errors that Linux detected at mount time.