36

I have just clean installed Lubuntu 24.04 LTS from Lubuntu downloads to my HP 255 G1 laptop. Now I cannot access my external hard drive.

Error mounting /dev/sdb1 at/media/name/Transcend:  
wrong fs type,bad option,bad superblock on /dev/sdb1,missing codepage  
or helper program,or other error.

I can access the NTFS formatted external drive from another laptop.

The answer which worked for me has been deleted for some reason. The answer is:

I did this using Windows 10.

Run Disk Error Checking

Plug in your external hard disk.

Open File Explorer by pressing the Windows keys button + E.

Go to This PC.

Right-click your external hard disk under Devices and drives.

Select Properties

Go to Tools tab.

Under Error checking, click Check.

If prompted, click Yes or enter the administrator password.

Click Scan drive > Repair drive.

Wait for the process to finish.

The scanning process may take a while depending on the size of your external hard disk

and the specifications of your PC.
karel
  • 122,292
  • 133
  • 301
  • 332
Marty
  • 645

14 Answers14

92

Occasionally, I'm facing the same issue with Ubuntu 24.04. The following steps helped me:

  1. Run Disks app.
  2. Select problematic disk.
  3. Click the cog wheel.
  4. Edit Mount Options….
  5. Turn off User Session Defaults.
  6. Change other parameters as required (I've noticed that this issue resets the list of options).
ENIAC
  • 1,051
42

If you're encountering an issue while trying to mount a disk and getting the error "mount: wrong fs type, bad option, bad superblock" on Ubuntu 24.04 LTS, here’s a possible solution:

sudo fdisk -l
sudo apt install nfs-common
sudo apt install cifs-utils
sudo ntfsfix -d /dev/sdb1
eaitfakir
  • 519
  • 4
  • 4
4

Problem mounting NTFS external drives is a known bug in 24.04.

Solution : blacklist the ntfs3 driver from running.

From command line :

echo 'blacklist ntfs3' | sudo tee /etc/modprobe.d/disable-ntfs3.conf

Then reboot.

​ SOURCE : https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/2062972

R3uK
  • 107
PJW
  • 51
  • 2
2

To fix the disk run on Windows chkdsk /f D:. Change the drive letter with the letter the disk is named on Windows.
This should fix the issue.

Not required: I also noticed that "mount" can mount the disk anyway: Try to do lsblk to get the disk path. Make a temp directory before and change /dev/sda2 with the path to the disk. And then:

sudo mount /dev/sda2 ~/temp
rzickler
  • 187
  • 1
  • 2
  • 8
Davide
  • 21
2

For me what worked was the following:

  1. Open the Disks application.
  2. Select the disk with the problem in the left panel.
  3. Select the partition with the problem.
  4. Click the configuration gear icon at the bottom left.
  5. Click Edit mounting options.
  6. Disable the User Session Defaults toggle option.
karel
  • 122,292
  • 133
  • 301
  • 332
JRU
  • 21
0

Much simpler. Just start "disks" app and press the little black arrow ("mount disk"). That's all.

nikosal
  • 181
  • 1
  • 7
0

Run this bash script after changing "/dev/sdb2" to your disk device

#!/bin/bash

Script to troubleshoot and repair issues with mounting /dev/sdb2


PARTITION="/dev/sdb2"
MOUNT_POINT="/mnt"


echo "Starting troubleshooting for $PARTITION"


Step 1: Perform a file system check


echo "Running fsck on $PARTITION..."
sudo fsck $PARTITION
if [ $? -ne 0 ]; then
    echo "fsck encountered errors on $PARTITION."
else
    echo "fsck completed without errors."
fi


Step 2: Attempt to repair NTFS file system


echo "Running ntfsfix on $PARTITION..."
sudo ntfsfix $PARTITION
if [ $? -ne 0 ]; then
    echo "ntfsfix encountered errors on $PARTITION."
else
    echo "ntfsfix completed without errors."
fi


Step 3: Attempt to mount the partition


echo "Attempting to mount $PARTITION to $MOUNT_POINT..."
sudo mount $PARTITION $MOUNT_POINT
if [ $? -ne 0 ]; then
    echo "Failed to mount $PARTITION to $MOUNT_POINT."
else
    echo "$PARTITION successfully mounted to $MOUNT_POINT."
fi


Step 4: Check for bad blocks


echo "Checking for bad blocks on $PARTITION..."
sudo badblocks -v $PARTITION > badblocks_output.txt
if [ $? -ne 0 ]; then
    echo "Bad blocks check encountered errors. Please review the badblocks_output.txt file."
else
    echo "Bad blocks check completed. Results saved in badblocks_output.txt."
fi


echo "Troubleshooting completed for $PARTITION."
Himanshu Attri
  • 1
  • 1
0

In Kubuntu plasma I solved this by going KDE Partition Manager (which you can search it from the main menu)

In the left sidebar I clicked the hard drive (disk) that I wasn't able to mount and it showed me the details in the right window, from that I did a right click on the specific drive and selected "edit mount point"

I found out that there was no mount point specified "none", at first I typed a path manually as /mnt/toshibadrive and applied the changes but it didn't work, then after some other tries which didn't work, I came back to "edit mount point" and I clicked the button "select" then I was able to select that same folder I specified before! once I saved it worked.

I am just writing this answer here in case it helps anyone who is under kde plasma.

michel smith
  • 1
0
  1. Run Disks (app) from utilities. [It is pre-installed]
  2. Select your disk (& partition if needed).
  3. Below the graph-like figure, open Settings by clicking on settings (gear) icon.
  4. Click on Repair FileSystem. [Took me 1 second for 1.5 TB drive.]
  5. Click on play button besides settings button to mount.

Hope this helps.

Chainsaw Man
  • 1
0

For me, the error message indicated that the directory /media/usrname/PART II does not exist, so the mount command is failing because there’s no target directory for it.

I fixed it like so:

  1. sudo mkdir -p "/media/usrname/PART II"
  2. sudo mount -t ntfs /dev/sda5 "/media/usrname/PART II"
ANIKET MISHRA
  • 1
0

I had the same problem with an external hard drive. I could solve it pretty quickly by:

  1. Open the Disks application (Ubuntu default).
  2. Select the desired disk.
  3. Click the cogwheel button and use the option "Check Filesystem".
  4. Click on it again and now use "Repair Filesystem".
  5. Done.
Alex
  • 1
0

Everything was solved for me quite simply, I think the problem is caused by the fact that I use two operating systems. Apparently, at some point I did not correctly remove the USB flash drive from the windows operating system, that's where everything broke. After that, linux did not open the flash drive and displayed an error from the problem header. Solution: insert the USB flash drive into windows, a window will appear stating that you need to restore the USB flash drive and restore it, do this and extract it after completion. Then it should work fine on linux.

Shama LK
  • 1
0

I faced the same issue a few days back, while my external disk was working fine but suddenly it stopped working so did same as follows

  • Open the Disks application (Ubuntu default)
  • Select the desired disk.
  • Click the cogwheel button and use the option "Check Filesystem".
  • Click on it again and now use "Repair Filesystem". it shouldn't take long, mine was done within 1-2 sec.
Ankit
  • 1
0

I recently upgraded to Ubuntu 25.04 and was copying file from nvme0n1(exFAT) to sdb1 (SanDisk CruzerBlade Pendrive)(NTFS) when suddenly my PC ran out of battery, the operation was terminated obviously but when I restarted the PC and tried mounting my Pendrive again, I ran into this issue.

Yeah, I tried sudo mount and what not, but only this terminal workaround was helpful.

sudo fdisk -l
sudo apt install nfs-common
sudo apt install cifs-utils
sudo ntfsfix -d /dev/sdb1

I'd recommend trying this if you encounter a similar issue.

PS: In my case, the Pendrive just had the System Volume Information Folder (created by Windows), so I had the guts to bear a data wipe, although the contents are preserved and data wasn't lost in the above workaround, but be cautious during the operation.

Divya Agrawal
  • 1
  • 1