Recent update broke mounting NTFS

The most recent update seems to have broken mounting NTFS partitions.

  1. NTFS-3g is installed
  2. Fuse-common is installed
  3. No issue mounting ext4 partitions on the same physical drives(3 different drives)
lsblk -f
sda                                                                                    
├─sda1                                                                                 
└─sda2      ntfs         HHD1      01D5B8EB1D08F7D0                                    
sdb                                                                                    
└─sdb1      ext4   1.0   linuxssd  34b473cc-a33c-4b8b-9d1f-61739c72aa0a  196.4G    50% /run/media/hardbrocklife/linuxssd
sdc                                                                                    
├─sdc1                                                                                 
├─sdc2      ntfs         HDD2      A4D84095D840679E                                    
└─sdc3      ext4   1.0   linuxstor abf3e9c1-0bc9-4772-8461-b78e3be2ba2c    2.2T    32% /run/media/hardbrocklife/linuxstor
nvme0n1                                                                                
├─nvme0n1p1 vfat   FAT32           2C40-C070                              13.1M    66% /boot/efi
├─nvme0n1p2                                                                            
├─nvme0n1p3 ntfs                   01D72E8C4125BB90                                    
├─nvme0n1p4 ntfs                   01D72E8C4300E430                                    
├─nvme0n1p5 ext4   1.0             d9fc4efc-4790-4c7e-845c-c879e81a351d   54.8G    58% /var/lib/snapd/snap
│                                                                                      /
└─nvme0n1p6 ext4   1.0             7b0bab14-8018-4bd9-84d8-2f347b415fb8  414.7G    57% /home

It wont mount them in Dolphin when I try to click on them.

Error mounting /dev/nvme0n1p3 at /run/media/hardbrocklife/01D72E8C4125BB90: wrong fs type, bad option, bad superblock

I was able to manually mount them via replicating what clicking them in Dolphin would do:

  1. create mount point /run/media/hardbrocklife/01D72E8C4125BB90
  2. mount /dev/nvme0n1p3 /run/media/hardbrocklife/01D72E8C4125BB90

That worked for 2 of the partitions.

The 3rd partition had to be the problem child:

sudo mount /dev/sda2 /run/media/hardbrocklife/HDD1                                                                                        ✔ 
$MFTMirr does not match $MFT (record 3).
Failed to mount '/dev/sda2': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.

I have not booted into windows on this PC in over 8 months, and that partition has been working perfectly for the last 8 months. That is not a Windows OS partition either. The windows partition is actually the one that I used as a working example, and it mounted fine.

It could be failing, but its highly improbable as I more recently ran disk checks and no issues were found. It is also occurring at the same time I was unable to mount the other partitions.

I am having this exact same issue on my laptop as well, starting with the recent update(which also broke my internet access on my laptop but Im creating another thread for that)

Have a look here:

1 Like

Interesting!

The other 2 partitions that I had to manually mount now mounts fine with clicking on them in Dolphin.

Interestingly, the problematic partition did not, though its error messaged changed. Unfortunately its the least helpful an error message could be. This is the error Dolphin threw:

An error occurred while accessing 'HHD1', the system responded: The requested operation has failed: Error mounting /dev/sda2 at /run/media/hardbrocklife/HHD1: Unknown error when mounting /dev/sda2

Interesting that the command didnt fix that partition, but did facilitate some sort of change as the error message changed.

Looks to be the same error I got previously when I tried manually mounting the partition:

sudo mount /dev/sda2 /run/media/hardbrocklife/HDD1                                                                                       
[sudo] password for hardbrocklife: 
$MFTMirr does not match $MFT (record 3).
Failed to mount '/dev/sda2': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.      

Do you think it would serve me to booted into Windows, which makes me sad, to attempt something? Gunna bum me out if I do and it works as I have been really wanting to remove Windows as dual boot. I do not want Windows to ever be the good guy lol.

1 Like

Yes, try to perform chkdsk from with Windoof and also make sure to properly shutdown Win afterwards, no Fastboot enabled to make sure not ending in a kind of hibernating situation.

2 Likes

Freaking A. This worked!

sudo ntfsfix /dev/sda2  
sudo ntfsfix /dev/sda2                                                                                                                    ✔ 
[sudo] password for hardbrocklife: 
Mounting volume... $MFTMirr does not match $MFT (record 3).
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 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/sda2 was processed successfully.

Was doing some more research becuase I dont want to invite Gates back into my life and found a similar issue posted on another forum. Ran this command and it immediately loaded.

Marking this thread as resolved and this as the resolution, but any idea as to why this worked?

“Correcting differences in $MFTMirr record 3…OK”

This correlates the error the it spat out earlier:

“$MFTMirr does not match $MFT (record 3).”

MFT, and whatever it is, is beyond my knowledge at the moment.

3 Likes

MFT = Master File Table, MFT Mirror = partial backup of MFT used to recover from corruption.

Somehow they got out of sync (system crash or power failure while writing to the device is the most likely cause).

1 Like

Thank you. For me, having understanding of the resolution has as great a value as the resolution itself.

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