You are not logged in.
My kernel version is:
❯ uname -r
5.15.5-arch1-1
I wanted to mount a ntfs partition using ntfs3 driver, so I entered:
❯ sudo mount -t ntfs3 /dev/sdb1 /mnt/Data
mount: /mnt/Data: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
I tried to confirm if the driver was loaded:
❯ lsmod | grep ntfs
ntfs3 274432 0
Then I tried to fix the partition,but I got the same error:
❯ sudo ntfsfix /dev/sdb1
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/sdb1 was processed successfully.
❯ sudo mount -t ntfs3 /dev/sdb1 /mnt/Data
mount: /mnt/Data: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
Then I mounted the partition without any option:
❯ sudo mount /dev/sdb1 /mnt/Data
❯ mount -l
......
/dev/sdb1 on /mnt/Data type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096) [数据]
As you can see,it drives by ntfs-3g not ntfs3. What can I do?
Last edited by d1s12t (2021-11-28 15:59:53)
Offline
Check your dmesg for errors with ntfs3. Chances are the volume is still marked dirty, and ntfs3 will not mount a partition where that is the case without the force option. ntfsfix without any arguments will actively set the dirty bit, so that a chkdsk from Windows can do a real check/analysis. If you don't have that handy and want to clear the dirty bit despite ntfsfix not being entirely a good checking tool you can pass the -d argument to ntfsfix.
Offline
Thanks! You are right! Just need to enter the follow comands:
sudo ntfsfix -d /dev/sdb1
sudo mount -t ntfs3 /dev/sdb1 /mnt/Data
Last edited by d1s12t (2021-11-28 15:51:01)
Offline
anyone new coming here for solve who is getting the same error,
install "ntfs-3g" package & then use gnome-disks or similar application (or manually) to mount a NTFS filesystem.....
Offline
The following command is fine:
$ntfsfix --clear-dirty /dev/nvme0n1p4
but an error will be reported if you use etc/fstab auto-mount:
wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
Offline