Read+write for ntfs internal drive

Hi there
I just found that an internal 'Windows' drive does not allow me to write to the disk, any folder.

This SSD which has only my documents and photos, was installed in the other PC running win10 and Zorin 'Core', and I was able to create folders etc. without any probs.

I have now moved that SSD to my 'Pro' Zorin pc, which dual boots with Win11, and only today noticed the problem.

Since I will still like to access the SSD when using Win11, how to make it writable from Z Pro as well as Win11.?

I assume that because it is/was to be used by Win11 and Z, that there is some permissions to be set up, rather than taking ownership.!?

This is the current fstab entry:

UUID=66AAEB3BAAEB0681 /media/E_DATA auto nosuid,nodev,nofail,x-gvfs-show 0 0

The partition is /dev/sda5

Ideas please!!
cheers CD

Is it just this one partition, or any other ones as well? And just to clarify, I'm not sure if the problem happens while you're on Zorin OS, Windows, or both.

And lastly, could you launch Disks and select the drive and partition(s), and share a screenshot?

1 Like

@doobre: You could look there how the Ownership of the Drive is set up.

Hi there, thanks for your replies.
I have restarted the pc a few times, for other reasons, and into Win11 as well, and now the problem has sorted itself out.
Even though the owner still shows as 'root', there is 'create and delete' access showing in the properties tab. So all good there.

I don't see a mention of an owner in the disks window.!

Glad it is sorted anyway, I'll keep an eye on it.
Cheers CD

It is greyed out:

But interesting that the Drive is in MBR and not GPT.

Correct, the Disks application only shows information about the drive itself.

One common issue with drives formatted in different file systems is that some information is "lost in translation", so to speak. Windows' NTFS doesn't understand the schema that Linux uses for ownership and permissions, so it can lead to this type of erratic behavior.

And the same is true for Linux's EXT4 file system, by the way, which doesn't understand the same information from NTFS files.