Dolphin cannot mount drive "wrong fs" but mount command works fine

Help
1

I have a external drive for my data (500GB SSD) using the ntfs file system.
Recently I bricked this by forgetting to unmount a VeraVault before unplugging in a hurry.

Since then the drive is unusable on my Linux PC.
Dolphin gives this error:

image
image1075×45 13.2 KB

And mount gave a similar one.

After running ntfsfix over the drive it can be mounted and accessed fine with mount /dev/sda1 /mount/point, however Dolphin still fails.

So any tips how to mounting from inside dolphin working again?
In my eyes that’s a bug in dolphin or did a miss something there?

Please no advice on backups (I have these) and safe unmount (accident).

2

I have the same problem with a ntfs formatted external drive.

It seems to be some kind of problem with the ntfs3 kernel module.
Blacklisting the ntfs3 module in /etc/modprobe.d/blacklist.conf and installing ntfs-3g solved the problem. Dolphin now mounts the external drive with rw access.

But this can only be a workaround. There should be a way to use the ntfs3 module.

EDIT: Maybe its related to this 445468 – Cannot mount NTFS with the new ntfs3 module from Linux 5.15

3

I also have this problem.

> sudo lsblk /dev/sda1
NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sda1   8:1    0  1.8T  0 part 

> sudo blkid /dev/sda1
/dev/sda1: LABEL="TOSHIBA EXT" BLOCK_SIZE="512" UUID="FC0401410401007E" TYPE="ntfs" PARTUUID="a5222308-01"

> uname -a                                                  
Linux asus 6.17.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 14 21:44:46 UTC 2025 x86_64 GNU/Linux

> lsb_release -a         
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 25.10
Release:	25.10
Codename:	questing

Following two years old instructions with the word “kernel” in them doesn’t feel like a normal way to mount an external drive.

4

Similar/same problem here. Drive mounts fine through the terminal, and I can use dolphin to browse the drive, but if I unmount the drive inside dolphin and try to mount it again it still gives the same error. Weirdly enough, I have an identical drive, both Seagate 3TB drives of a similar age, both ntfs, and the other one mounts fine inside dolphin. But this one doesn’t. Is blacklisting ntfs3 the only solution?

5

Indeed, if you have Arch, it is up to you to fix your configuration, and this is documented here: