Comment 10 for bug 2062972

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.