@soundofthunder
I tried the chkdsk, and now I can auto mount the 2 drives through fstab.
But, I have another issue, I can’t access many of the data inside, I can’t delete, cut, rename, tag or duplicate files.
When I run this command sudo findmnt --verify, I get this:
[minaw@mina-manjaro ~]$ sudo findmnt --verify
[sudo] password for minaw:
/mnt/Data
[W] ntfs3 does not match with on-disk ntfs
/mnt/Fun
[W] ntfs3 does not match with on-disk ntfs
none
[W] non-bind mount source /swapfile is a directory or regular file
0 parse errors, 0 errors, 3 warnings
Is it only in Linux that you notice this? Are those files still accessible in Windows without any problem? Are you mounting the Windows system drive (C:) in Linux? - if so, that’s not a good idea (mounting a secondary partition or disk is preferred).
Post your current/etc/fstab content; maybe that will be useful to someone; otherwise, nothing comes immediately to mind.
I have never used findmnt --verify; the tool might not support ntfs3 (a guess). Keep in mind that most Linux tools are designed for use with native Linux filesystems, without much thought given to Microsoft (or Apple) formats. In any case, you’ll notice they are warnings and not errors; you can probably ignore them. Cheers.
GNU nano 7.2 /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=A999-BF76 /boot/efi vfat umask=0077 0 2
UUID=d4407709-5ea0-42a1-915f-202fc30174a2 / ext4 defaults,noatime 0 1
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
UUID=01D6D6DDA6146800 /mnt/Data ntfs3 defaults 0 0
UUID=5E7E4E247E4DF575 /mnt/Fun ntfs3 defaults 0 0
/swapfile none swap defaults 0 0
Why you can’t access some of those files, I can’t say, however it seems likely to be permissions related. That’s a whole new topic in itself.
For now, mark the post that you feel solved the mounting issues, and then start another thread with the new issue.
Aside:- I just noted this threads title - are Data and Funactually external USB disks? If so, they shouldn’t actually need to be listed in /etc/fstab; they should mount only manually using the disk mount feature in the taskbar. Just something to keep in mind. Cheers.
When I chose from grub the LTS kernel and changed the fstab back to /mnt/Data ntfs-3g auto,nofail,uid=1000,gid=1000,utf8,umask=022,defaults 0 0, it works fine and I can access all the files. With ntfs3 on the newest kernel, I can read, but can’t write to almost all files. That’s what I mean.
They are hard drives that I am sharing between Windows and Linux. I am adding them to fstab as I access them a lot on both systems and I don’t need to mound them dolphin panel with entering the sudo password every time I use them.
NTFS on linux is a reverse engineered implementation of a proprietary Microsoft filesystem.
Such implementation can only be a best effort when no specification has been released by Microsoft.
Therefore it is recommended to use exFAT as this is the only filesystem which can be used to exchange data between platforms without issues.
While NTFS has an extended attribute set designed for access control - those attributes only work on Windows and have no meaning for a Linux system.
Write permission errors with NTFS is never rooted in Linux but in how the filesystem was previously handled on a Windows system when the device was unmounted or shutdown.
NTFS formatted file systems should never be mounted using fstab but always mounted ad-hoc.
With today’s Linux such devices will always appear in the file manager’s device pane and can be mounted on the fly.
If it doesn’t appear it is a matter of configuring the file manager to display devices not yet mounted.
I think it works only for Data drive. If I am right, then it still has the same accessibility issue that I had with fstab. I still can’t cut, delete, rename or tag.
Update: this issue was due to naming i.e., inside the mount file of Fun, it was called Data. I changed it and they both are auto mount. But, still can’t write to both f them.
total 56
drwxr-xr-x 2 root root 4096 Apr 4 19:11 data
drwxrwxrwx 1 root root 12288 Mar 24 15:52 Data
drwxrwxrwx 1 root root 40960 Apr 5 21:34 Fun
I noticed something weird. The files and folders inside any of the main directory of 2 drives can be partially modified, but any subfolder can’t be.
For example: /mnt/Fun/<file 1>or<folder 1> (This <file 1> or <folder 1> in the main directory can be copied, cut, renamed and deleted, but can’t be tagged, duplicated or compressed).
But, /mnt/Fun/<folder 1>/<file 2>or<folder 2> (This <file 2> or <folder 2> inside the <folder 1> can’t be modified, it can only be copied).
Do you mean adding iocharset=utf8 inside one mount file, then reload and add inside the another mount file of the second drive? And I add only to the mount files, not the auto mount?
I think this works, finally . I don’t know what does umask=0000 make? And is it dangerous to files or anything?
I tried it with systemd method and then disabled those file and moved them to another folder to test it on fstab. And till now it works fine. I’ll deeply try it and if I found any wrong, I’ll post it. Thank you so much for help.
@soundofthunder Thank you so much for your patience and help, I really appreciate your efforts.
umask=0000 ensures everything is rwx for user,group,other - and no it is not dangereous ntfs device but it would be quite unsafe on a Linux filesystem - it corresponds to chmod 0777 <path-or-name> or chmod ugo+rwx <path-or-name>.
The default umask for filesystems on Manjaro is 0022 which translates to u=rwx,g=rx,o=rx
I have learned something as well - something I wouldn’t have been able to otherwise - I don’t use Windows - I don’t have any disks with Windows generated NTFS filesystems - so you helped me learn as well - so thank you.
What I think I have learned is:
The ntfs3 kernel driver applies some kind of ACL and that ACL is not inherited from the mountpoint but is read from the filesystem inside the mountpoint.
drwxrwxrwx 1 root root 12288 Mar 24 15:52 Data
drwxrwxrwx 1 root root 40960 Apr 5 21:34 Fun
If I had such ntfs device I would look deeper into the file tree and look at folder and file permission below /mnt/Data and /mnt/Fun
The umask tells the ntfs3 driver to apply read,write,execute on everything that is available on the device.
The execute is necesary only for folders - otherwise you wouldn’t be able to navigate the filesystem.
The other is are self explainatory.
It is possible to experiment with the umask - remember default is 0022
Get current value
I am trying to do that, I found something.
When I make the systemd method, the existing files and folder ownership is root, but still I can control them as far as I test them. And the new created folder or files are owned by me as a user. On fstab method, it’s all owned by me except for a file I was trying on it in the terminal with sudo command to cut it, may be this changed the permissions of the file.
May be because in fstab I use this line with uid=1000?
.
. I don’t know what does umask=0000 make? And is it dangerous to files or anything?