This is working. kind of…
After adding this line to fstab the NTFS volume is mounted, but something very strange is going on.
I have following normal folder structure on the NTFS volume:
root\subfolder1\subfolder2\subfolders3
Now i can create/save in the “root” folder and “subfolders3” of the NTFS volume.
But i still cant create/save in subfolder1 and subfolder2 !! Wired!
Do i have to “take ownership” or something?
P.S Just found that in some “subfolders3” i also can’t create/save..
I will probably return to root mount NTFS volume with Dolphin…
Was some sort of .. attempted permissions applied at some point?
I mean, aside from the assigning from the original fstab line?
By default NTFS does not even have permissions the same way native linux filesystems do.
( Even from a fully functioning OS - as long as it is not encrypted you could mount a windoze “C” drive from linux and then create/edit/delete files in its ‘root’ with no extra steps or prompting. )
Never was any attempt for permissions (not even sure how to do this).
Since day one i just was using root mount with Dolphin to edit/create folders and files at NTFS volume.
Eventually i will migrate to other file system or keep mounting like root.
By the way, Thank you for helping me i really appreciate this!
So maybe did those folders get created as or ‘owned’ by root then?
You can check the permissions with something like “Properties” or in the terminal;
ls -la .
(where . expands to the current directory path, or you can input whatever path)
Adding -la to the list command will print ownership/permissions information along with the listing.
If those directories are owned by root then we have the answer.
If necessary you can set ownership with something like
sudo chown $USER:$USER file_or_path
To do it recursivley (all the way down to subsequent paths from the originating path)
sudo chown -R $USER:$USER file_or_path
Where $USER:$USER is replaced by your username like asenesky:asenesky and represents the owner and group.
To sum - please check, and if necessary augment, the ownership/permissions and observe the results while using the suggested ntfs3 fstab line.
This will ultimately be the most favorable assuming you do not need interoperability with windoze.
But a linux filesystem will definitely have permissions to be managed.
You are right!
In the folders that i can’t crate/edit shows owner “root”, the others that i can work on are owned by my user “gamer”.
This is wired because, those folders were created long time ago in Windows system..
I wil try “chown” now.
Finally problem solved!
sudo chown -R $USER:$USER file_or_path
Did the trick and now my user is the owner of the entire NTFS volume and this is solved my problems.
Is it possible that this problem occur because the folder that i was trying to use was “shared” folder in the Windows OS , may be this is put some restrictions who can and who cannot do certain operations over the content?
I want to thank everybody who spend their time trying to help me and especially CSCS, who didn’t give up in front of my obvious lack of knowledge and helped me to resolve this puzzle.
Maybe?
Though I still think it was likely the product of the previous mount/use as root interactions .. in the same way that if I mount an NTFS partition regularly, but then run sudo mkdir something that something directory will be owned by root.
Could you please show an example how to use “ntfsplus” module.
Also the above solution is working until then NTFS volume gets “dirty” and can not be mounted by Cachyos. In this case i usually end up at recovery console mode and can’t boot until i go and manually disable the mount in fstab or fix the dirty NTFS partition from Windows. Is there a way just to skip mounting the NTFS partition if it is dirty or at least to ask me what i what to do instead to go straight to recovery mode?
Yes this has always been the case.
As outlined here and elsewhere the only valid response to that would be chkdsk on windoze (or a PE/clone like Hirens).
The NTFS filesystem is a proprietary filesystem by and for windoze.
There was never any linux tool to repair NTFS.
That is until the newer “ntfsplus” module. Like its only been a handful of weeks that almost anyone has had access to it.
But we do now so ..
Just be running kernel 7+ and use ntfs on the fstab line rather than ntfs3 or ntfs-3g and make sure to have ntfsprogs-plus installed, ex;
