Disk Mount Error in Linux: Causes and How to Fix

What a Disk Mount Error Means

A disk mount error in Linux occurs when the system cannot connect a partition's or device's file system (e.g., a USB flash drive, external HDD, virtual disk) to a directory in the file system tree (the mount point). Typical messages:

mount: /dev/sdb1: wrong fs type, bad option, bad superblock on /dev/sdb1,
       missing codepage or helper program, or other error
       (for some file systems it is useful to run the `fsck` utility).

mount: /mnt/usb: permission denied.

mount: /dev/sdc1: can't read superblock

These errors can appear when attempting manual mounting via mount or during automatic mounting (e.g., when connecting the device through a graphical interface). The problem blocks access to data on the disk.

Causes

1. The mount point does not exist. The specified directory (e.g., /mnt/backup) is missing.
2. The file system is not supported by the kernel. No driver for FAT32, NTFS, exFAT, HFS+, etc. Often resolved by installing a userspace package (e.g., ntfs-3g).
3. File system corruption (superblock). The disk was unsafe to remove, or a crash occurred. A fsck check is required.
4. Insufficient permissions. The mount point belongs to another user or has overly restrictive permissions (chmod). Mounting as root requires administrator privileges.
5. The device is already mounted. Attempting to mount a partition that is already connected elsewhere (check mount | grep sdb1).
6. Conflict with another process. A process (e.g., a file manager) is already trying to mount the device or is using it.
7. Incorrect entry in /etc/fstab. Error in the line format, incorrect UUID, or file system type.
8. Hardware failure. Issues with the USB cable, port, or the drive itself.

Solutions

Method 1: Basic Command and Log Analysis

First, perform the mount manually in the terminal to see the exact error message. Assume the device is /dev/sdb1 and the mount point is /mnt/usb.

sudo mount /dev/sdb1 /mnt/usb

Then check the kernel system log for error details. Filter the output by the device name.

sudo dmesg | tail -30 | grep sdb
# Or for a more current log (systemd)
sudo journalctl -k | tail -50 | grep sdb

Pay attention to lines containing error, fail, SCSI, USB. They often indicate the specific cause (e.g., SCSI error: sense key — a problem with the device).

Method 2: Creating the Mount Point and Checking Permissions

Ensure the directory for mounting exists and is accessible.

# 1. Create the directory if it does not exist
sudo mkdir -p /mnt/usb

# 2. Check permissions. Usually 755 is sufficient.
ls -ld /mnt/usb
# drwxr-xr-x 2 root root 4096 Feb 16 10:00 /mnt/usb

# If permissions are different, fix them:
sudo chmod 755 /mnt/usb

Try mounting again. If the permission denied error persists, the issue might be with permissions on the device itself (/dev/sdb1). Check:

ls -l /dev/sdb1
# brw-rw---- 1 root disk 8, 17 Feb 16 09:55 /dev/sdb1

In this example, the device belongs to the disk group. Add your user to this group (sudo usermod -aG disk $USER) and log out and back in.

Method 3: Checking and Repairing the File System (fsck)

If dmesg mentions superblock, corrupted, I/O error, or the disk was removed without umount, a check is required.

⚠️ Warning: fsck can destroy data in case of serious corruption. If possible, make a backup of important files using another method (e.g., via ddrescue).

1. Ensure the disk is not mounted.
2. Run the check for the appropriate file system.
   • For ext4/ext3/ext2:

     sudo fsck -y /dev/sdb1
     

   • For NTFS (uses ntfsfix — an fsck equivalent):

     sudo ntfsfix /dev/sdb1
     

   • For exFAT (uses fsck.exfat):

     sudo fsck.exfat /dev/sdb1
     

3. After successful completion, try mounting again.

Method 4: Manual Mounting with Explicit File System Type

If the system does not detect the file system type automatically, specify it manually.

# For NTFS (requires the ntfs-3g package)
sudo mount -t ntfs-3g /dev/sdb1 /mnt/usb

# For exFAT (requires the exfat-utils or exfatprogs package)
sudo mount -t exfat /dev/sdb1 /mnt/usb

# For HFS+ (requires the hfsprogs package)
sudo mount -t hfsplus /dev/sdb1 /mnt/usb

# With options for NTFS (read/write, no caching for reliability)
sudo mount -t ntfs-3g -o rw,noatime,nodiratime /dev/sdb1 /mnt/usb

If the file system package is not installed, you will get an error like unknown filesystem type or failed to find /sbin/mount.ntfs. Install it:

# Debian/Ubuntu
sudo apt update
sudo apt install ntfs-3g exfat-utils hfsprogs

# RHEL/CentOS/Fedora
sudo yum install ntfs-3g exfat-utils hfsplus-tools

Method 5: Checking Mount Point Usage and Processes

Sometimes the directory you are trying to use as a mount point is not empty. The system will not allow mounting a disk over existing files.

# Check the mount point's contents
ls -la /mnt/usb

# If there are files, move them or choose another directory.
# Also check if this point is already used by a mounted device:
mount | grep /mnt/usb

If the issue is that the device is already mounted elsewhere (e.g., in /media/user/DRIVE), unmount it first:

sudo umount /dev/sdb1
# or
sudo umount /media/user/DRIVE

Then mount it in the desired location.

Method 6: Fixing NTFS Issues via Windows (chkdsk)

For disks that were actively used in Windows, errors may be in the file system itself. The best way to fix them is to run chkdsk in Windows.

1. Connect the disk to a computer with Windows.
2. Open the command prompt (cmd) as an administrator.
3. Enter (replace X: with your drive letter):

   chkdsk X: /f
   

   The system may offer to schedule the check on the next reboot — agree.
4. After chkdsk completes, reconnect the disk to Linux and try mounting again.

Method 7: Forced Mounting (Read-Only Only!)

Use only for urgent data access and if other methods have failed. Forced mounting can lead to data loss or further corruption.

# Mount in "read-only" mode, ignoring file system errors
sudo mount -o ro /dev/sdb1 /mnt/usb

# Or with type specified and ignoring some errors (for NTFS)
sudo mount -t ntfs-3g -o ro,remove_hiberfile /dev/sdb1 /mnt/usb
# The remove_hiberfile option removes the Windows hibernation file, which blocks write access.

After successfully mounting in ro mode, copy important files to another medium. Then format the disk in Linux or perform a full check in Windows.

Prevention

1. Always use 'Safe Removal' (umount or the eject icon in the file manager) before physically disconnecting a USB drive.
2. Regularly check disks for errors, especially after power failures:

   sudo fsck -f /dev/sdXn  # -f to force check even on a clean file system
   

3. Update the system and packages (sudo apt upgrade) to get the latest file system drivers.
4. For external drives used in both Windows and Linux, prefer file systems with good cross-platform support: exFAT (modern standard) or FAT32 (4 GB file limit). NTFS via ntfs-3g is also reliable but may have issues with Windows hibernation.
5. When setting up automatic mounting via /etc/fstab, always use the disk's UUID (find out: sudo blkid), not the device name (/dev/sdb1), as the latter can change when other disks are connected. Example fstab line for NTFS:

   UUID=1234-ABCD /mnt/usb ntfs-3g defaults,noatime 0 0
   

6. Avoid forcibly disconnecting the USB port during active disk writes.

Frequently Asked Questions (FAQ)

💡 Tip: If you frequently work with different external drives, set up automatic mounting of all USB drives to a common directory (e.g., /media/usb) via udev rules and a script. This is beyond the scope of this article but is an advanced solution for workstations.