You are not logged in.
- Topics: Active | Unanswered
#1 2025-01-21 22:28:18
- misnad
- Member
- Registered: 2025-01-21
- Posts: 2
[SOLVED] udiskie cannot detect ntfs
When I try to mount an external hard disk (with NTFS) I get this error: Error mounting /dev/sda1 at /run/media/user/disk: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
I tried manually mounting and it works. I tried with udiskctl, and it works with the "-t ntfs" argument passed, but without explicitly specifying the filesystem I still get the same error. Why doesn't udisk automatically figure out the filesystem?
"lsblk -f" shows /dev/sda1 as ntfs.
Last edited by misnad (2025-01-22 11:08:55)
Offline
#2 2025-01-21 22:41:02
- mackin_cheese
- Member
- Registered: 2025-01-07
- Posts: 280
Re: [SOLVED] udiskie cannot detect ntfs
what research have you done so far regarding this issue?
Online
#3 2025-01-21 22:54:49
- seth
- Member
- Registered: 2012-09-03
- Posts: 61,632
Re: [SOLVED] udiskie cannot detect ntfs
Head-start for the research:
https://wiki.archlinux.org/title/NTFS
https://wiki.archlinux.org/title/NTFS-3G
The error message is most likely misleading, one of those drivers is much more lenient when it comes to mouting FS that are marked as dirty because they've not properly been unmounted or, much worse, are still in active use by another OS
Offline
#4 2025-01-22 11:07:05
- misnad
- Member
- Registered: 2025-01-21
- Posts: 2
Re: [SOLVED] udiskie cannot detect ntfs
I have tried ntfsfix, but only without --clear-dirty.
Passing --clear-dirty to ntfsfix solved the issue.
Thanks all.
Offline
#5 2025-01-22 14:54:12
- seth
- Member
- Registered: 2012-09-03
- Posts: 61,632
Re: [SOLVED] udiskie cannot detect ntfs
Passing --clear-dirty to ntfsfix solved the issue.
You do understnad the implications of all of this?
The filesystem was marked dirty for a reason - cause it was.
Glossing over that bears the risk of data loss. Make sure to not run into this by always properly unmounting the filesystem - on linux and windows alike.
ntfs-3g being lenient and allowing you to use the FS "cause whatever" isn't very reliable behavior, ntfs3 telling you to get your stuff straight is more annoying but frankly the more rebust approach as well.
Offline