41

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,695
  • 134
  • 305
  • 337
Marty
  • 695
  • 1
    Was the disk in question last used on a Windows system with the "Fast boot" setting enabled?

    The Windows "Fast Boot" (Windows defaults to "ON") setting leaves the disk partition in an undocumented, proprietary state that Linux isn't permitted to recognize. Boot back into Windows and disable "Fast Boot". Be prepared to have to re-disable "Fast Boot" - Windows updates have been known to turn it back on. See https://www.windowscentral.com/how-disable-windows-10-fast-startup

    – waltinator May 03 '24 at 16:00
  • No, I backed up all my data to the drive before installing Lubuntu 24.04LTS with the intention of reinstalling my data afterwards, unfortunately I can't do that because of the error as I have described. Should I try sudo ntfsfix -b /dev/sdb1 or could this damage my data? – Marty May 03 '24 at 16:23
  • As NTFS is a windows file-system, I'd perform checks and apply fixes on windows. Does the drive work correctly on other windows machines? as windows fastboot/hibernate etc. unclean drives can be used normally on the windows system that left the file-system unclean, but you'll have problems on other machines (regardless of OS where file-system is unclean). Providing command you used & full output of what you see maybe helpful (or if you use GUI tools, what you did maybe inc. tool used). Message implies unclean fs OR incorrect mount command to me. – guiverc May 04 '24 at 01:54
  • Yes the drive works on a windows 11 laptop. I connected the drive to a usb port & the error message comes up. In (disks) the drive is shown but I get the same error when I select mount. – Marty May 04 '24 at 08:46
  • I am facing similar issue since i installed Kubuntu 24.04 – Ismail Yushaw May 04 '24 at 21:34
  • When I use Windows to access the drive, it says there is a problem with the drive. When I select fix/repair the drive windows says it is unable to but still lets me access all of the data on the drive. – Marty May 05 '24 at 10:02
  • This is still very annoying as I use Lubuntu, any further help would be much appreciated. – Marty May 06 '24 at 08:58

14 Answers14

98

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

  1. Run Disks app.
  2. Select the 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,139
50

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
  • 599
  • 8
    worked. but for ntfsfix you have to sudo apt-get install ntfs-3g – Talha Anwar Oct 13 '24 at 15:10
  • 3
    Worked. As above commenter said. Also, ntfs-3g was already installed, so I just needed to install cifs-utils. – Nighto Nov 08 '24 at 10:58
  • Worked for me. Thank you – Hannes Dec 01 '24 at 09:10
  • Why are you asking users to install nfs-common or cifs-common? It seems to me that those two packages have nothing to do with ntfsfix. – TSJNachos117 Dec 19 '24 at 17:06
  • 2
    Thank god this worked. I unplugged my HD from one computer and plugged it into another and couldn't access any of my files. Then I plugged it back into the original computer and that couldn't access the files anymore either. – Charles Clayton Feb 01 '25 at 00:52
  • THANK You, Windows 11 had corrupted the superblock of my external hdd. This fixed and all the data is intact – nabeel May 25 '25 at 11:22
  • This worked for me after my machine was unintentionally restarted using the physical reset button – Jonno_FTW Aug 18 '25 at 07:44
  • NOTE: you need to use sudo fdisk -l to identify the drive that you want to modify - it's probably not /dev/sdb1 - replace that with the path you find with fdisk. After doing that, this solution works. I did wonder why install nfs-common and cifs-utils though, they seem irrelevant. – Peter Kionga-Kamau Sep 19 '25 at 16:34
7

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
  • 81
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
  • 185
Davide
  • 21
  • As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers in the help center. – Community May 10 '24 at 06:20
  • I have error mounting /dev/sdb1 So why would I try sudo mount /dev/sda2 ~/temp? Where should I create the temp directory and what is it for? On Windows what should I change the disk letter to? – Marty May 10 '24 at 09:48
  • to fix the issue in any case go on windows check the letter associated to the disk you want to check (e.g. for my case the disk was in D:) and run the command chkdsk /f D: (replace D with the letter of where is the disk on windows). I just noticed that sometimes "mount" works anyway from command line, but this is less important. just fix the disk from windows and everything should work – Davide May 11 '24 at 21:46
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,695
  • 134
  • 305
  • 337
JRU
  • 21
1

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"
0

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

nikosal
  • 181
  • Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center. – Community Aug 10 '24 at 08:29
  • The gnome-disk-utility app is a GNOME package, and isn't found on a LXQt or Lubuntu system. As LXQt is a Qt5 desktop, the closest would be KDE Partition Manager but it isn't found with the term 'disks' – guiverc Aug 10 '24 at 09:09
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."

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.

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.

  • 1
    There is no Disks app pre-installed; KDE Partition Manager is pre-installed as Lubuntu uses a LXQt desktop (ie. Qt5 based). The app you mention is found on GNOME systems such as Ubuntu Desktop, not Lubuntu. – guiverc Sep 27 '24 at 21:57
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.

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.