ntfs partition does not mount with linux 6.8 and CONFIG_BLK_DEV_WRITE_MOUNTED=n

Bug #2062972 reported by Chris Balabanis
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned
ntfs-3g (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I am using Ubuntu 24.04 Development Branch (Beta). I am dualbooting it with Windows 11. When I try to mount my NTFS Windows partition via the Ubuntu Dock, I get: "Error mounting /dev/nvme01np3 at /media/chris(my username)/Windows:wrong fs type, bad option, bad superblock on /dev/nvme01np3, missing codepageor helper program, or other error".

Output of sudo apt-cache policy ntfs-3g: ntfs-3g:
  Installed: 1:2022.10.3-1.2ubuntu3
  Candidate: 1:2022.10.3-1.2ubuntu3
  Version table:
 *** 1:2022.10.3-1.2ubuntu3 500
        500 http://gr.archive.ubuntu.com/ubuntu noble/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ntfs-3g 1:2022.10.3-1.2ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
Uname: Linux 6.8.0-28-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 20 18:25:55 2024
InstallationDate: Installed on 2024-04-20 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
SourcePackage: ntfs-3g
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Chris Balabanis (chris0nlinux) wrote :
Revision history for this message
Jean-Pierre (jean-pierre-andre) wrote :

First of all, please show you are using ntfs-3g. In your syslog, you
should have something like :

Cmdline options: rw,permissions,umask=0022
Mount options: allow_other,default_permissions,subtype=ntfs-3g,rw,fsname= [...]

Are these followed by other errors ?

Then, problems have been reported when using kernel 6.8.x when mounting from fstab,
and a kernel issue is suspected, see :

https://github.com/tuxera/ntfs-3g/issues/108

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ntfs-3g (Ubuntu):
status: New → Confirmed
Revision history for this message
N (sunnybubblegum) wrote :

I've been experiencing a similar issue since performing a fresh install of Ubuntu 24.04 LTS yesterday. While my external NTFS USB hard drive is recognized upon plugging it in, trying to mount it or access its contents gives me the 'wrong fs type, bad option, bad superblock' error.

I was able to get the external hard drive to mount via Terminal with the help of an article...
https://linovox.com/how-to-fix-failed-to-mount-wrong-fs-type-bad-option-bad-superblock-on-linux/
...however, its files are only accessible by navigating to my newly created /mnt/Media folder.

The drive is not visible in Nautilus, but I can see it in the Disks app (which is also how I unmount it). I get an error when trying to access its contents with the Steam app, specifically when I attempt to use the Restore Game Backup feature.

My external hard drive had been working fine with Ubuntu 22.04 a few hours earlier, and running a disk check said it was healthy.

Revision history for this message
thiago (tsoeiro88) wrote :

Fresh Ubuntu 24.04 install here.
Tried to mount my NFTS partition and I get the same error attached.

Revision history for this message
Jean-Pierre (jean-pierre-andre) wrote :
summary: - ntfs partition does not mount
+ ntfs partition does not mount with linux 6.8 and
+ CONFIG_BLK_DEV_WRITE_MOUNTED=n
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Pranav Dalvi (pranavd) wrote (last edit ):

If you are mounting drive by referring to
https://linovox.com/how-to-fix-failed-to-mount-wrong-fs-type-bad-option-bad-superblock-on-linux/
Then mount the drive in /media/ dir to be able to detect the drive in Nautilus.

Revision history for this message
Matthias (msiewert) wrote :

sudo ntfsfix -d /dev/sda1

fixed this temporarily on my USB key until I plug it in again

Revision history for this message
Olivier in Belgium (tousavelo) wrote (last edit ):

Observed similar symptoms on Ubuntu 24.04 on a NTFS partition on a USB SSD. (wrong fs type, bad option, bad superblock on /dev/XXXXXXXX, missing codepageor helper program, or other error).

I'm not too sure if I should report in this item or in https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2063985

The partition is not a Windows system partition. It "merely" has data.

The partition mounted without issue with Ubuntu 22.04 on the same laptop; and still mounts without issue on another Ubuntu 22.04 laptop.

After sudo ntfsfix -d /dev/sdb5, with 24.04, the partition appear as mounted in Disks. And files can be accessed in Files/Nautilus.

sudo ntfsfix -d /dev/sdb5
[sudo] password for XXXXXXX:
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sdb5 was processed successfully.

Still OK after I "safely removed drive" and reconnected.
Not tested after a reboot.
Good luck.

sudo apt-cache policy ntfs-3g
[sudo] password for XXXXXXXX:
ntfs-3g:
  Installed: 1:2022.10.3-1.2ubuntu3
  Candidate: 1:2022.10.3-1.2ubuntu3
  Version table:
 *** 1:2022.10.3-1.2ubuntu3 500
        500 http://be.archive.ubuntu.com/ubuntu noble/main amd64 Packages
        100 /var/lib/dpkg/status

UPDATE:
Similar symptoms, and solution/workaround with ntfsfix for another drive. This one from Lacie, also NTFS.
sudo ntfsfix -d /dev/sdc1
Mounting volume... $MFTMirr does not match $MFT (record 0).
FAILED
Attempting to correct errors...
Processing $MFT and $MFTMirr...
Reading $MFT... OK
Reading $MFTMirr... OK
Comparing $MFTMirr to $MFT... FAILED
Correcting differences in $MFTMirr record 0...OK
Correcting differences in $MFTMirr record 3...OK
Processing of $MFT and $MFTMirr completed successfully.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sdc1 was processed successfully.

Revision history for this message
Avinash (avinash-manoli) wrote :

I had the same problem. I dual boot Ubuntu 24.04 and Windows 11. The issue was resolved for me by disabling fast startup in Windows 11

https://support.lenovo.com/us/en/solutions/ht513773-how-to-enable-or-disable-fast-startup-on-windows-11

The fast start up option which is enabled by default on Windows 11 hibernates the system instead of shutting it down which seems to be causing this problem when trying to access the NTFS partition from Ubuntu.

Revision history for this message
Fazekas, Lajos (superskyhawk) wrote :

I ran into the same issue on:

Linux Lenovo-ThinkPad-X13-Gen-1 6.8.0-36-generic #36-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun 10 10:49:14 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Finally I found a resolution after reading this article:
https://wiki.archlinux.org/title/NTFS#Unable_to_mount_with_ntfs3_with_partition_marked_dirty

Steps to resolve the problem:

Under linux:
sudo ntfsfix --clear-dirty /dev/_yourdiskAndPartition_here_

Rebooted into Windows 11, then command line with administrator rights:
chkdsk c: /f /r

Booted win11, checkdisk done and issues resolved.

Rebooted to Ubuntu, then mounting was fine.

Revision history for this message
Charles Faulkner (deadofnight) wrote :

This affects me too, just finished the upgrade to 24.04 manually (I'm on Kubuntu), and on first reboot into new system, I saw my external SATA pop up in Dolphin, but I got an error when I tried to mount it, the same one which Chris received, as a warning in the top portion of Dolphin.

After following Matthias' ntfsfix solution, I now have the disk mounted and accessible. Anyone have any ideas where this has broken, or is it too soon to be asking? :)

Revision history for this message
nmaxx (nmaxx) wrote (last edit ):

Until this is fixed properly, would it be an option for Ubuntu to revert to the 6.7 behavior by building the kernel with CONFIG_BLK_DEV_WRITE_MOUNTED=y instead?
Once 6.8 hits the HWE channel this will also break NTFS in many 22.04 installs eventually...

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.