Mounting ntfs partition errors out with "$MFTMirr does not match $MFT"

hikmateustad · 2025-03-01 07:08:48

Previously worked with no issues in thunar. I have other ntfs partitons also which host Windows OS, those work but this particular partition /dev/sda6 does not. All of a sudden clicking on partition name in thunar brought up the authentication diaglog, entered admin password and was met with an error (text with red background) saying cannot mount since it is corrupted, bad fs type etc (long message shorted here)

Searched and found ntfs commands which mount partition. On issuing mounting command it errored out with "$MFTMirr does not match $MFT".
Then i ran ntfsfix command and I can now mount my partition only through command line and can then access from thunar.

[hikmateustad@archlinux ~]$ sudo ntfsfix /dev/sda6
[sudo] password for hikmateustad: 
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/sda6 was processed successfully.
[hikmateustad@archlinux ~]$ sudo ntfs-3g /dev/sda6 /mnt
[hikmateustad@archlinux ~]$

But I want to mount it through thunar like I used to do earlier. I upgraded to kernel 6.13.4-zen1-1-zen and now on 6.13.5-zen1-1-zen . It all started with 6.13.4-zen1-1-zen, do not know if it is a kernel upgrade issue.

Following are the relevant output

[hikmateustad@archlinux ~]$ neofetch
                   -`                    hikmateustad@archlinux 
                  .o+`                   ---------------------- 
                 `ooo/                   OS: Arch Linux x86_64 
                `+oooo:                  Host: HP Pavilion g6 Notebook PC 0884110000385910000610100 
               `+oooooo:                 Kernel: 6.13.5-zen1-1-zen 
               -+oooooo+:                Uptime: 50 mins 
             `/:-:++oooo+:               Packages: 1107 (pacman) 
            `/++++/+++++++:              Shell: bash 5.2.37 
           `/++++++++++++++:             Resolution: 1366x768, 3840x2160 
          `/+++ooooooooooooo/`           DE: Plasma 
         ./ooosssso++osssssso+`          WM: KWin 
        .oossssso-````/ossssss+`         Theme: Breeze-Dark [GTK2], Breeze [GTK3] 
       -osssssso.      :ssssssso.        Icons: breeze-dark [GTK2/3] 
      :osssssss/        osssso+++.       Terminal: konsole 
     /ossssssss/        +ssssooo/-       CPU: Intel i5-3210M (4) @ 3.100GHz 
   `/ossssso+/:-        -:/+osssso+-     GPU: Intel 3rd Gen Core processor Graphics Controller 
  `+sso+:-`                 `.-/+oso:    Memory: 1884MiB / 15881MiB 
 `++:.                           `-/+/
 .`                                 `/                           
                                                                 


[hikmateustad@archlinux ~]$ lsblk -f
NAME   FSTYPE FSVER LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                
├─sda1 vfat   FAT32            00D5-7A98                                           
├─sda2                                                                             
├─sda3 ntfs         Win11-Bare AA5ED81D5ED7E05D                       95.3G    20% /run/media/hikmateustad/Win11-Bare
├─sda4 ntfs                    4AB63566B63553A3                                    
├─sda5 ntfs         Win11-VM   1AB29151B29131ED                       72.8G    27% /run/media/hikmateustad/Win11-VM
├─sda6 ntfs         Data       3828F3F328F3ADCE                       43.5G    56% /mnt
├─sda7 vfat   FAT32            1123-7FD4                             831.2M    19% /boot
├─sda8 swap   1                9990f372-55ca-4cf9-a416-90abe5ee5651                [SWAP]
└─sda9 ext4   1.0              51310cd1-8cdb-4407-aabe-224f7654d930   75.6G    18% /
sr0                                                                                
zram0  swap   1     zram0      8be0f0a7-afc1-4862-88ed-43bfc79223ef                [SWAP]
[hikmateustad@archlinux ~]$ 
[hikmateustad@archlinux ~]$  sudo fdisk -l /dev/sda
[sudo] password for hikmateustad: 
Disk /dev/sda: 698.64 GiB, 750156374016 bytes, 1465149168 sectors
Disk model: WDC WD7500BPVT-6
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 3A698EA5-D16F-479E-9CA1-0256D3A63C42

Device         Start       End   Sectors   Size Type
/dev/sda1       2048    206847    204800   100M EFI System
/dev/sda2     206848    239615     32768    16M Microsoft reserved
/dev/sda3     239616 250580991 250341376 119.4G Microsoft basic data
/dev/sda4  250580992 251895807   1314816   642M Windows recovery environment
/dev/sda5  251895808 461611007 209715200   100G Microsoft basic data
/dev/sda6  461611008 671326207 209715200   100G Microsoft basic data
/dev/sda7  671326208 673423359   2097152     1G EFI System
/dev/sda8  673423360 706977791  33554432    16G Linux swap
/dev/sda9  706977792 916692991 209715200   100G Linux filesystem
[hikmateustad@archlinux ~]$

After ntfsfixing command line mounting works and then I can access from thunar. But I want to access directly from thunar without going through these hoops.

How can I fix this issue on mounting from thunar.

P.S

The error message in thunar reads An error occurred while accessing "Data", the system responded. The requested operation has failed: Error mounting /dev/sda6 at /run/media/hikmateustad/Data: wrong gs type, bad option, bad superblock on /dev/sda6, missing codepage or helper program or other error I had to reboot to see this thunar error fresh.

Last edited by hikmateustad (2025-03-01 08:25:24)

seth · 2025-03-01 08:31:47

I have other ntfs partitons also which host Windows OS

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Then run chkdsk on the drives from windows, the difference you experience is likely because thunar via udisks will default to in-tree ntfs3 instead of (previously used and more lenient ntfs-3g)
You can revert that by udisks config BUT IGNORING INCONSISTENT FILESYSTEMS WILL PROVOKE DATA LOSS!
So fix the filesystem and make sure to always properly close it from every OS before accessing it elsewhere, regardless of which ntfs driver you end up using.

hikmateustad · 2025-03-03 11:12:54

seth wrote:

I have other ntfs partitons also which host Windows OS
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
Then run chkdsk on the drives from windows, the difference you experience is likely because thunar via udisks will default to in-tree ntfs3 instead of (previously used and more lenient ntfs-3g)
You can revert that by udisks config BUT IGNORING INCONSISTENT FILESYSTEMS WILL PROVOKE DATA LOSS!
So fix the filesystem and make sure to always properly close it from every OS before accessing it elsewhere, regardless of which ntfs driver you end up using.

I tried reverting udisk2 behaviour to no avail. Created that config file in the appropriate place and rebooted to same problem.

I did not find any 3rd link.

seth · 2025-03-03 13:57:50

There're 4 links in my signature, the 3rd one is http://wiki.archlinux.org/title/Dual_bo … ibernation
Post the udisks config you created (and where) and mount some ntfs partition using udisks and post the output of "mount", but regardless of all of that: fix the filesystem w/ windows chkdsk and make sure to disable windows fast-start and to always close the filesystem.
Even if ntfs-3g ignores that error, that's not "safe" at all.

Arch Linux

#1 2025-03-01 07:08:48

Mounting ntfs partition errors out with "$MFTMirr does not match $MFT"

#2 2025-03-01 08:31:47

Re: Mounting ntfs partition errors out with "$MFTMirr does not match $MFT"

#3 2025-03-03 11:12:54

Re: Mounting ntfs partition errors out with "$MFTMirr does not match $MFT"

#4 2025-03-03 13:57:50

Re: Mounting ntfs partition errors out with "$MFTMirr does not match $MFT"

Board footer