Nautiulus not open a NTFS drive from usb

Bug #2041155 reported by www2
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

The problem:
When i try to open a NTFS USB drive in nautilus i get the error "Error mounting /dev/sda1 at /media/<user name>/<drive name>: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error".

What i expect:
Mound the drive and show the drive directory in nautilus.

Extra
the drive that i use is a 2.5 inch external hardrive that connect with usb3.
Ubuntu version that i use is Ubuntu 23.10 that is upgrade from Ubuntu 23.04.
Early Ubuntu versions include ubuntu 23.04 work normal.

Revision history for this message
www2 (j-p-r-anceaux) wrote :

I forgot to write that using command line command: "ntfs-3g /dev/sda1 /mnt" work as normal.

Revision history for this message
draekko (draekko) wrote :

I had the same issue, and I got the following when inserting a usb drive or external HD formatted with NTFS

"Error mounting /dev/some-device at /media/username/some-drive-name: wrong fs type, bad option, bad superblock on /dev/some, missing codepage or helper program, or other error"

It makes it sound like it was detecting an EXT2/3/4 type partition instead of NTFS.

It was all working fine literally the hour before upgrading to Ubuntu 23.10 and now have the issue with drives that have never been touched by Windows but have NTFS on them needing to be rescued.

Running ntfsfix or running Disks to check the file system option on the partition says that there are no errors.

I did find an item from syslog about the kernel finding a dirty flag for one device when i went looking there but it happened AFTER upgrading to 23.10

2023-11-08T15:03:42.163421-05:00 NA kernel: [38161.331242] ntfs3: dm-3: volume is dirty and "force" flag is not set!

Clearing the flag with ntfsfix -d /dev/devices-to-fix seems to handle it but the error message from the Nautilus dialog is severely misleading.

But clearly something has changed and the error messaging is wrong, it also seems like something after the upgrade is setting the flag to dirty causing it all to fail.

From what i've seen the issue is starting to pop up on various forums.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.