First a forums technical remark.
We do not like images when they are not really needed. Difficult to read, impossible to use browser search functions on them, impossible to select parts of them for quoting.
What we do like is copied/pasted texts from a terminal emulator (like konsole
, or xterm
or the like), and the paste as Preformatted text: Posting code or preformatted text - Using Discourse - Discourse Meta
======
Then back to your problem.
I also asked for the output of
mount
which is still missing.
In fact I am still trying to understand what you mean with “NTFS drives are booted as read-only”. Because that is a conclusion of yours but not why you think this is so. We need the facts, not the conclusions.
In general there are two possibilities
- the file system is mounted read-only, in which case we should investigate why. And that is why I asked if they are properly removed from Windows. And that is also why I asked to show if they are mounted read-only.
- One or more users are unable to write to files on the file system and/or create new files on the file system. Then that probably is a case of ownership and permissions (as is true on every directory/file in a Unix/Linux system).
Now we have seen your /etc/fstab, we know they are mounted at boot and we can also see what (faked) ownership and permissions will be used for the directories and files on the file system.
Because you do not mention a specific user, all files there will be owned by user root
.
Because of the fmask
and dmask
options, the permissions of files will be set to rw-r--r--
and those of directories will be set to rwxr-xr-x
. I assume that you understand what this means.
So if it is a user that complains about being unable to write, that is correct.
That depends on what you want. You are the system manager.
If root
is to be the owner and all users should be able to write there, you should change the fmask=
and dmask=
accordingly.
If only a specific user has to have access to the data on those file systems, you should change the owner/group with the uid=
and gid=
options (and can then leave the fmask=
and dmask=
as they are, and please pay attention that the user him/herself can not change permissions to his/her liking as he/she can do elsewhere, because on NTFS this is impossible).
BUT, my advice in both cases would be NOT to use mount point inside /run
. That is typical a place for the system to manage things and the system manager should not poke around there.
There are by far more logical places to be used as mount points. And when one runs really out of imagination, then there is /mnt
specially created for it.
Examples.
When these data are for a specific user only, one could mount them inside that user’s home directory. May however in this case prefer mountpoints like /mnt/bigboy
and then let the user create a symbolic link from within a place in his home directory. E.g.
ln -s /mnt/bigboy /home/serioushoax/windowsdata/smallboy
(sorry for the puns).
Long story, I hope it helps. Yes, Linux has a steep learning curve. You can of course come back for more questions clarification, etc. But please show what I asked for and try to find out what your goal with those file systems is.