Mounting NTFS drives with ntfs3 fails due to (possibly false) dirty flag

[TLCPlusPlus]

Issue/Description: Mounting: "Unable to access drive

Error mounting /dev/sdb2 at /media/user/Hard Disk: wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error."

Unmounting: Clicking the Eject button does nothing.

Version:

cosmic-files: Installed: 0.1.0~1741902591~24.04~fac5a25

Steps to Reproduce:

1. Open COSMIC Files.
2. Click on Hard Disk.
3. Error.

Expected Behavior: Hard Disk to be mounted or unmounted as needed.

[TLCPlusPlus]

Temporary workaround:

Open cosmic-term (ensure you do mkdir "/media/user/Hard Disk" if it doesnt exist)

To mount: sudo mount /dev/sdb2 "/media/user/Hard Disk" This allows cosmic-files to see into the mounted drive

To unmount: sudo umount "/media/user/Hard Disk" This allows you to unmount the drive, as the eject button does not work. Also properly gets reflected in cosmic-files as it becomes unmounted as well as the eject button disappearing.

[iamkartiknayak]

This issue has been fixed with a recent update.

[TLCPlusPlus]

This issue has been fixed with a recent update.

I wish it was, but its not. I am on 0.1.0~1755744274~24.04~f06029f

[iamkartiknayak]

I have this version installed and it's working fine for me

cosmic-files:
  Installed: 0.1.0~1755744274~24.04~f06029f

[TLCPlusPlus]

I have this version installed and it's working fine for me

cosmic-files:
  Installed: 0.1.0~1755744274~24.04~f06029f

I guess something else about cosmic-files is wrong then, in my specific case.

[Kvikal]

After trying to debug this issue, it seems like it isn't really a problem with cosmic-files itself (at least for me). In my case, NTFS on the flash drive was set as "dirty" which lead to this error message. Mounting via mount works in this state and doesn't produce any errors but cosmic-files doesn't mount in this state.

You can check if this is the same issue by looking into journalctl if there is:

Sep 18 09:42:58 pop-os kernel: ntfs3(sda): It is recommened to use chkdsk.
Sep 18 09:42:58 pop-os kernel: ntfs3(sda): volume is dirty and "force" flag is not set!

Cleared the "dirty" flag on the drive using ntfsfix -d /dev/sda and it works now.

[TLCPlusPlus]

After trying to debug this issue, it seems like it isn't really a problem with cosmic-files itself (at least for me). In my case, NTFS on the flash drive was set as "dirty" which lead to this error message. Mounting via mount works in this state and doesn't produce any errors but cosmic-files doesn't mount in this state.

You can check if this is the same issue by looking into journalctl if there is:

Sep 18 09:42:58 pop-os kernel: ntfs3(sda): It is recommened to use chkdsk.
Sep 18 09:42:58 pop-os kernel: ntfs3(sda): volume is dirty and "force" flag is not set!

Cleared the "dirty" flag on the drive using ntfsfix -d /dev/sda and it works now.

My log was insanely large so I just piped journalctl into grep and found only 1 instance of that saying (the affected drive, sdb2).

Reguardless, it solved my issue, so thank you for reaching out and helping me.

[RTbecard]

Is this issue really closed? I just see a temporary workaround on here. I also have the problem, it's specific to NTFS drives, and I believe its this Ubuntu bug.

In my case, my drive opened correctly, I safely unmounted and unplugged it, then then next time I plugged it in, I got this error. I then opened the drive on windows without issue, ran the drive repair on there, but it still wouldn't work on pop-os after that.

I did the workaround suggest in the bug report, forcing a fall back to the older ntfs-3g driver.

echo 'blacklist ntfs3' | sudo tee /etc/modprobe.d/disable-ntfs3.conf Then reboot the box.

And that has solved it for me. The other workaround listed here (fixing the dirty flag) is only a temporary one.

Do we just have to wait around until Ubuntu updates (or blacklists) the nfts3 package, or is there anything that can be done on the pop-os end to fix this?

Can we please reopen this until a actual fix is made?

IMO, seems like a pretty serious issue for onboarding new windows users if the first time they plug in their NTFS drives, they get this cryptic error message.

[TLCPlusPlus]

Is this issue really closed? I just see a temporary workaround on here. I also have the problem, it's specific to NTFS drives, and I believe its this Ubuntu bug.

In my case, my drive opened correctly, I safely unmounted and unplugged it, then then next time I plugged it in, I got this error. I then opened the drive on windows without issue, ran the drive repair on there, but it still wouldn't work on pop-os after that.

I did the workaround suggest in the bug report, forcing a fall back to the older ntfs-3g driver.

echo 'blacklist ntfs3' | sudo tee /etc/modprobe.d/disable-ntfs3.conf Then reboot the box.

And that has solved it for me. The other workaround listed here (fixing the dirty flag) is only a temporary one.

Do we just have to wait around until Ubuntu updates (or blacklists) the nfts3 package, or is there anything that can be done on the pop-os end to fix this?

Can we please reopen this until a actual fix is made?

IMO, seems like a pretty serious issue for onboarding new windows users if the first time they plug in their NTFS drives, they get this cryptic error message.

Well it worked for me ever since fixing the flag, but I ended up backing up the NTFS drive in question because it was failing (it was rather old). I can't speak of this issue anymore though as my new backup drive is ext4, so I no longer have this problem. I'll be unsubscribing from this personally.

Going back on topic, I do hope this issue gets fixed, having delt with it as long as I did was a pain.