External drives are on root permissions

[MW_J97]

@Aragorn

Reboot into Windows, run a CHKDSK.EXE on those partitions, disable Fast Boot and/or Hybrid Sleep, shut down Windows, and reboot into Manjaro again.

Okay, I’ll give it a try.

[MW_J97]

@Nachlese

… not just shut it down - it has got a feature that enables faster start up - leaving the file systems
(from the perspective of another OS)
in a “dirty” state.

Okay, I got it.

[Nachlese]

Windows assumes it is the only system - fast startup will work reliably.
But it gets in the way when the same file system is going to be accessed from within another system.
Then the file system is not “clean” - Windows preserved the state and knows about it.
The other system doesn’t …

[Aragorn]

@MW_J97

Here it’s

UUID=01D6D6DDA6146800   /mnt/Data       ntfs    defaults        0       0 
UUID=5E7E4E247E4DF575   /mnt/Fun        ntfs    defaults        0       0
6.1.44-1-MANJARO

Also, as you could have read in the tutorials I posted — specifically, the first one — your mount options in /etc/fstab are wrong.

If you want to be able to write to them as a regular user, then it should be something like this…

UUID=01D6D6DDA6146800   /mnt/Data    ntfs-3g  auto,nofail,uid=1000,gid=1000,utf8,umask=022,defaults        0       0 
UUID=5E7E4E247E4DF575   /mnt/Fun     ntfs-3g  auto,nofail,uid=1000,gid=1000,utf8,umask=022,defaults        0       0

[linux-aarhus]

@MW_J97

The drives are both NTFS and working very fine till today.

When you mount in fstab you mount as root and when you mount as root on system folder your mount is readonly.

Permissions on the mountpoint is defining what can be done with content so to avoid messing with a sysem folder always create your own dedicated structure.

e.g. device with exfat filesystem becomes readonly it the mountpoint is owned by root:root.

with ntfs it is different as ntfs can contain information about hibernation state which causes the kernel to mount readonly.

so you should reboot into Windows and ensure a clean shutdown before you attempt to write to the partition(s)

also ensure the mountpoint has the correct permissions e.g. owned by root:users as your user should be member of the users group which will ensure you can write to the device.

[MW_J97]

Thank you so much, I disabled the fast start and hybrid sleep. I didn’t notice this issue before and only today because I usually don’t shut down Windows, I reboot it and those options doesn’t affect the reboot. Yesterday was the first time to shut down windows from the day I installed dual system.

[MW_J97]

@Aragorn

UUID=01D6D6DDA6146800   /mnt/Data    ntfs-3g  auto,nofail,uid=1000,gid=1000,utf8,umask=022,defaults        0       0 
UUID=5E7E4E247E4DF575   /mnt/Fun     ntfs-3g  auto,nofail,uid=1000,gid=1000,utf8,umask=022,defaults        0       0

Thank you so much for help. The issue is in the fast start and hybrid sleep, like you both said.
Do I have to change fstab to be like this? Or as it’s working fine, I don’t change anything.

[MW_J97]

@linux-aarhus

with ntfs it is different as ntfs can contain information about hibernation state which causes the kernel to mount read-only.

Thanks for replying, this is the issue. I disabled fast startup and hybrid sleep. Is there anything I should disable, too??

[Aragorn]

@MW_J97

Thank you so much for help. The issue is in the fast start and hybrid sleep, like you both said.
Do I have to change fstab to be like this? Or as it’s working fine, I don’t change anything.

Yes, I do recommend changing your /etc/fstab into what I posted.

[MW_J97]

Thank you, I changed it.