Ntfs-3g driver must be used in fstab to properly mount NTFS format drives


Look at your errors, failed mount unit, sdb2 (NTFS).

Seems like their is a bug mounting the junk NTFS file system this week from recent reports.

Be sure to use the nofail flag if you mount via fstab.


Ah that's pretty shit. I had it mounted for rsync reasons as it's an internal SSD.

Seems I'm getting another issue now though. When in Dolphin, I select Basic Data Partition which is my Windows Install. It says the following when clicking on it.

An error occurred while accessing 'Home', the system responded: The requested operation has failed: Error mounting /dev/sdb2 at /run/media/adamj/5AFA22EAFA22C1DD: wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error
man fstab

NTFS is useless for backing up Linux. It wont preserve Linux file permissions (unless contained in an archive).


Oh I see, I'll use an external disk in the future then thanks. But in the meantime, any idea how to fix that problem in Dolphin? I'm not trying to mount it anymore in fstab but it used to work without a problem.

It's a bug from the looks of things.

External hard disk mount problem

Try mounting the drive in fstab using ntfs-3g flag.


Seems to be a bug like you said which is unfortunate. When selecting my Windows drive through Dolphin it says:

An error occurred while accessing 'Home', the system responded: The requested operation has failed: Error mounting /dev/sdb2 at /run/media/adamj/5AFA22EAFA22C1DD: wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error

I entered your text into the fstab file and when running sudo mount -a it didn't give an error for once but I still can't access the drive from within Linux.

Try the linux-lts kernel.

1 Like

Good idea and I will try, but I just managed to fix the problem. I replaced ntfsprogs with ntfs-3g and rebooted and it just worked. Could this be because my fstab contained the wrong ntfs package you gave me or because there's a bug in one package but not the other? I'm very intrigued now so I'm gonna investigate this a bit deeper

As I figured, likely a new kernel bug, as the NTFS driver is in-kernel now, (bad mistake IMO).


Replaced the package name in fstab and same problem again. Gonna just stick to the one that works for now I think. No clue what is different between these packages though

Oh I see, so it may be better to stick with ntfs-3g? Any reason to go with one or the other really?

The Paragon NTFS driver appears to be buggy, (I think that's what they used). The ntfs-3g driver still appears to be stable.

I am going to edit your title to reflect the cause more clearly.


Thanks for all the help. I'm just glad this is finally sorted as I do enjoy accessing different installations even if it is shitty Windows. I wonder why this is even a problem and how it happened but at least there's a more stable ntfs driver available to make it work. The reason I mainly wanted it mounted was to rsync to it but you let me know that NTFS doesn't preserve things from btrfs or at least Linux in general. So I formatted my external drive and worked out how to make it mount when plugged in and not fail to boot if not plugged in like I originally had it set as (nofail and a timeout) and now I can simply plug it when I feel like and run my rsync alias. So thanks! This is what Linux is about I guess, sometimes getting problems like the few I had and then feeling relief in fixing them. Sometimes I wish it was more like Windows in terms of it not breaking once on me in the last few years but then I remember how much more I prefer Linux even if I have to fix a problem here and there. Hopefully no more problems for now though haha

1 Like

Where's the fun in that, how would you learn anything new. :wink:

And you're welcome BTW. :+1:

1 Like

Yeah that's very true haha. It's always annoying and worrying but then relieving and fun to solve it.

Btw, while I have you here, and to prevent making a new post as I can't find the answer on Google for some reason, I'm trying to work out how to delete the rsyncbackup on my Windows drive but all Google is telling me is how to delete files from the destination that aren't on the source anymore. Was hoping you could tell me quick so I can get rid of that and then use my external drive for rsync. Sorry for the OT I figured it would be fine as the issue is resolved now haha.

Not enough details to say.

Sorry, but I'm needing to attend to some productive outside tasks now.

What is preventing you from deleting it?

I wasn't sure tbh. Kept trying everything but no matter what, the home and usr folder would stick whether deleting from Garuda or Windows. From Garuda it said something about not being able to delete directory that isn't empty even though I used rm -rf. Rsync force delete didn't work either. I'm guessing it was because Windows was mounted and for some reason it couldn't be deleted. So I just flashed a fedora image I had to my USB and booted into a live environment and it let me finally delete it from a live environment. Just running rsync now on my external hard drive which I formatted to btrfs like Garuda so it can hopefully have the best opportunity of preserving everything. This is my command btw, pretty happy with how it turned out after some tweaking. Although I need to fix the path to my external drive now it is mounted.

sudo rsync -aAXHv --exclude={"/swapfile","/home/adamj/Documents/OP7Pro","/.snapshots","/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found","/home/*/.thumbnails/*"," /home/*/.cache/mozilla/*"," /home/*/.cache/chromium/*"," /home/*/.local/share/Trash/*","/var/lib/dhcpcd/*"} / /run/media/adamj/fd0e2015-f7ec-44c7-bb14-33981ca47fea/rsyncbackup/

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.