Why USB Drives Won't Mount on Linux Mint
USB drive mounting failures on Linux Mint 21.x and 22.x are caused by a surprisingly narrow set of root causes: the udisks2 daemon that handles automounting has crashed or frozen, the filesystem on the drive needs to be checked (fsck), the drive is formatted with a filesystem Linux Mint doesn't handle automatically (exFAT, NTFS), or kernel 6.8 and 6.11 introduced a regression in the USB mass storage driver affecting certain drive controllers. Here are 9 targeted fixes.
Fix 1: Check If the Drive Is Detected at All
Before mounting, verify Linux Mint sees the drive at the hardware level.
1. Open a terminal (Ctrl + Alt + T).
2. Run: lsusb — your drive should appear (e.g., "Kingston Technology DataTraveler").
3. Also run: lsblk — look for a new device like /dev/sdb or /dev/sdc with partitions.
4. Run: dmesg | tail -20 immediately after plugging in. Look for lines like "usb X-X: new high-speed USB device" and "sdb: sdb1". If you see "I/O error" or "device descriptor read" errors, the drive or USB port has a hardware fault.
If lsblk shows the device but no mount point, proceed to the fixes below. If lsusb shows nothing, try a different USB port or test the drive on another computer.
Fix 2: Restart udisks2 and Re-plug the Drive
udisks2 is the daemon that handles automounting in Linux Mint. If it crashes or freezes, drives plug in and out without triggering any mount action.
1. Restart udisks2: sudo systemctl restart udisks2
2. Unplug your USB drive completely.
3. Wait 5 seconds.
4. Plug back in. The drive icon should appear in the Files (Nemo) sidebar.
If it still doesn't appear, check the udisks2 service status: sudo systemctl status udisks2 — look for any error messages.
Fix 3: Mount the Drive Manually
If automounting is broken but the drive is detected, mount it manually from the terminal.
1. Find the drive partition: lsblk — note the device name (e.g., /dev/sdb1).
2. Create a mount point: sudo mkdir -p /media/$USER/usbdrive
3. Mount it:
For FAT32/exFAT: sudo mount /dev/sdb1 /media/$USER/usbdrive
For NTFS: sudo mount -t ntfs-3g /dev/sdb1 /media/$USER/usbdrive
For exFAT: sudo mount -t exfat /dev/sdb1 /media/$USER/usbdrive
4. Access the drive: cd /media/$USER/usbdrive && ls
If mount returns "wrong fs type" or "unknown filesystem", proceed to Fix 5.
Fix 4: Install Missing Filesystem Support Packages
Linux Mint does not install exFAT or NTFS write support by default. Drives formatted with these filesystems silently fail to mount without the right packages.
For exFAT (common on USB drives formatted on Windows 10/11 and macOS for files over 4GB):
sudo apt install exfat-fuse exfatprogs
For NTFS (Windows drives):
sudo apt install ntfs-3g
For HFS+ (Mac-formatted drives):
sudo apt install hfsplus hfsutils
After installing, unplug and re-plug the drive. It should automount. If not, use the manual mount command from Fix 3.
Fix 5: Run fsck to Repair the Filesystem
A filesystem error (unclean shutdown, interrupted write, or sector errors) causes the kernel to refuse to mount the drive to prevent further corruption.
Warning: only run fsck when the drive is NOT mounted.
1. Confirm the drive is not mounted: mount | grep sdb — if it shows up, unmount first: sudo umount /dev/sdb1
2. Run filesystem check:
For FAT32: sudo fsck.fat -a /dev/sdb1
For ext4: sudo fsck.ext4 -fy /dev/sdb1
For NTFS: sudo ntfsfix /dev/sdb1
3. If fsck reports errors and fixes them: try mounting again.
4. If fsck reports "too many errors" or cannot fix them: the drive may have bad sectors. Use ddrescue to attempt data recovery before the drive fails completely.
Fix 6: Fix Permissions and Automount Settings in Nemo
Linux Mint's file manager (Nemo) has its own automount settings that may have been accidentally disabled.
1. Open Nemo (Files) -> Edit -> Preferences -> Behavior tab.
2. Ensure "Automatically mount media" and "Automatically open a folder for automounted media" are checked.
Also check the system-wide automount settings via gsettings:
gsettings get org.gnome.desktop.media-handling automount
If it returns false: gsettings set org.gnome.desktop.media-handling automount true
Fix 7: Fix the Kernel USB Regression (Kernel 6.8/6.11)
Linux Mint 22 with kernel 6.8.0 and certain 6.11.x builds introduced a USB mass storage driver regression that causes drives with JMicron and VIA Labs USB controllers to not mount or appear with I/O errors.
1. Check your kernel version: uname -r
2. Open Update Manager -> View -> Linux Kernels.
3. If on 6.8.0 or 6.11.0: install 6.8.12+ or 6.11.8+ which include the USB mass storage fix.
4. Alternatively, install the 6.12 LTS kernel from Update Manager if available.
5. Reboot into the new kernel and test your USB drive.
Fix 8: Check USB Power Management
Linux Mint's aggressive USB autosuspend can cause drives to appear disconnected even while plugged in, especially external HDDs that require more power to spin up.
1. Check if autosuspend is active: cat /sys/bus/usb/devices/*/power/control 2>/dev/null | grep -c auto
2. To disable autosuspend temporarily: sudo sh -c "for f in /sys/bus/usb/devices/*/power/control; do echo on > $f; done"
3. Re-plug your USB drive and test.
To make this permanent, create a udev rule: sudo nano /etc/udev/rules.d/50-usb-power.rules
Add: ACTION=="add", SUBSYSTEM=="usb", TEST=="power/control", ATTR{power/control}="on"
Save and reload: sudo udevadm control --reload-rules && sudo udevadm trigger
Fix 9: Recover Data from an Unreadable USB Drive
If the drive won't mount and you need to recover files before attempting a full repair:
1. Install TestDisk and PhotoRec: sudo apt install testdisk
2. For a failed partition: run sudo testdisk /dev/sdb and use the Analyse -> Quick Search function to find lost partitions.
3. For file recovery: run sudo photorec /dev/sdb to recover files from a damaged filesystem regardless of partition table.
4. For drives with bad sectors: sudo apt install gddrescue then sudo ddrescue -d -r3 /dev/sdb /path/to/image.img /path/to/logfile.log to create a forensic image, reading around bad sectors.
Frequently Asked Questions
Why does my USB drive mount on Windows but not on Linux Mint?
Most likely the drive is formatted with exFAT or a Windows-specific NTFS configuration. Install exfat-fuse and exfatprogs (for exFAT) or ntfs-3g (for NTFS) with sudo apt install, then re-plug. Also check if the drive has a Windows "dirty bit" set from an unclean disconnect - run sudo ntfsfix /dev/sdb1 to clear it.
My USB drive shows as read-only on Linux Mint — how do I make it writable?
Read-only mounts are caused by filesystem errors, NTFS dirty bit, or hardware write-protect switches. For NTFS: run sudo ntfsfix /dev/sdb1 to clear the dirty flag. For FAT32: run sudo fsck.fat -a /dev/sdb1. Also check if your drive has a physical write-protect switch on its body. If none of these apply, the drive may have failed and locked itself read-only as a protective measure.
Linux Mint says "Unable to mount — wrong filesystem type" — what does that mean?
Linux Mint does not have the correct filesystem driver installed. The most common causes: exFAT drive without exfat-fuse installed, NTFS drive without ntfs-3g, or Mac HFS+ drive without hfsplus. Install the appropriate package with sudo apt install and retry.
My USB drive worked last week but stopped mounting today — what changed?
A kernel update is the most common cause of sudden USB mount failures. Check your kernel version with uname -r and compare to when it last worked. Also check dmesg | tail -30 for USB error messages immediately after plugging in. If you see I/O errors, the drive may be failing. If you see a kernel module error, try booting a previous kernel from the GRUB menu.
How do I automatically mount a USB drive at startup on Linux Mint?
Add an entry to /etc/fstab. First find the drive UUID: sudo blkid /dev/sdb1. Then add a line to /etc/fstab: UUID=YOUR-UUID /mnt/myusb auto defaults,nofail,x-systemd.device-timeout=30 0 0. The nofail option ensures Linux Mint boots normally even if the drive is not plugged in at startup.
If your USB drive still won't mount after all 9 fixes, the drive itself may be failing. CloudHouse Technologies Linux support can remotely diagnose kernel USB issues, filesystem corruption, and perform data recovery triage in a single session.