You are not logged in.
Pages: 1
Hi, with the new kernel update I thought I'd try the new ntfs driver, however when I try:
sudo mount /dev/device /mountpoint -t ntfs3I get error:
mount: /mountpoint: mount(2) system call failed: No such file or directory.I tried running strace and get the following output:
mount("/dev/device", "/mountpoint", "ntfs3", 0, NULL) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/mountpoint", {st_mode=S_IFDIR|0755, st_size=4096, ...}, AT_SYMLINK_NOFOLLOW|AT_NO_AUTOMOUNT) = 0
newfstatat(AT_FDCWD, "/mountpoint", {st_mode=S_IFDIR|0755, st_size=4096, ...}, AT_NO_AUTOMOUNT) = 0
newfstatat(AT_FDCWD, "/dev/device", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x8, 0x11), ...}, 0) = 0Both mountpoint and device exist (return code 0), however mount command returns -1. I looked in lsmod and ntfs3 is loaded, so I don't see why the mount command shouldn't work, any ideas?
Last edited by zvon (2021-11-13 17:11:55)
Offline
sudo file -s /dev/deviceDoes it mount on ntfs-3g? Is it bitlocker encrypted?
Offline
/dev/sdb1: DOS/MBR boot sector, code offset 0x52+2, OEM-ID "NTFS ", sectors/cluster 8, Media descriptor 0xf8, sectors/track 63, heads 255, hidden sectors 2048, dos < 4.0 BootSector (0x80), FAT (1Y bit by descriptor); NTFS, sectors/track 63, sectors 3907024895, $MFT start cluster 786432, $MFTMirror start cluster 2, bytes/RecordSegment 2^(-1*246), clusters/index block 1, serial number #################; contains bootstrap BOOTMGRMounts fine on ntfs-3g, not encrypted as far as I know
Offline
I tried running ntfsfix on the partition and now I'm getting EINVAL, so progress I guess?
Offline
Nevermind, when I give it ro option I get ENOENT again, so it was actually a step back, ntfs-3g still works though.
Last edited by zvon (2021-11-13 12:11:28)
Offline
You want to try chkdsk (on windows) and make sure that windows isn't hibernating (so the drive is left dirty) - does ntfs-3g mount it rw or ro?
Offline
chkdsk fixed it, thanks! I can now mount with ntfs3 in rw mode!
Offline
Assuming there's a windows installation, see the 3rd link below and make very sure that it's not hibernating (instead of shutting down) because that's the most common cause for the dirty bit to be set.
Edit:
Also please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Last edited by seth (2021-11-13 17:06:14)
Offline
Pages: 1