I’m not. I provided troubleshooting steps for a common NTFS issue, then you interjected into the thread with extra commands and redundant steps involving uid and gid. We don’t even know if they are internal or external drives, but why assume these were all internal drives used with hibernation? A more likely case is they are 3 external drives formatted as NTFS back when they used a Windows PC. We’re still waiting for the original poster to clarify this for us. (Or they’re all internal in a desktop PC, still waiting on the OP.)
ntfs-3g does not need to be explicitly invoked in order to mount an NTFS file-system with “read-write” permissions.
Simply using the mount command is enough:
sudo mount /dev/nvme0n1p4 /mnt/ntfs
Yields this:
/dev/nvme0n1p4 on /mnt/ntfs type fuseblk (rw,nosuid,nodev,user_id=0,group_id=0,allow_other,blksize=4096)
I have full read-write access to my NTFS partition.
Using Dolphin file manager (as the OP did), simply clicking on the NTFS file-system yields full read-write access as well.
However, if the NTFS file-system is marked as “dirty”, it doesn’t matter what options you include in your mount command, and it doesn’t matter if you manually invoke ntfs-3g. It will still be mounted as read-only in order to protect the NTFS file-system.
Here is a similar thread for reference, in which ntfsfix was all that was needed to resolve the read-only issue:
https://archived.forum.manjaro.org/t/cant-modify-contents-on-ntfs-drives/33014
So let’s wait on the OP for clarifications. They did not yet provide the output from the previous commands which can hint to what the underlying problem is.