I did not know that I was supposed to answer no to this at all. @rugyada said
But I didn’t know that answering yes would be a problem, so I did it to proceed thinking this wasn’t a problem.
I installed ntfs and lib64ntfs now, and this doesn’t allow me to open the “Liam’s Gameplay” HDD from Dolphin, I still get the original error. This discussion is getting really difficult to follow along for me, so forgive me if it should be obvious what I should do next, but I’m not really sure what I should be trying now.
Somehow I still remain a little bit sceptical about the possibility of changing ownership on ntfs files just by simple mount and chown. But I really am curious. What should happen? Which user at the ntfs access control side corresponds to random user from Linux side?
Oh danggit! Now nobody is going to test and I will have to find the possible error messages myself… Bummer! (but perhaps hilarity could ensue? tempting!)
I wish I knew how that should work. Kernel.org gives something haphazard and links to linux-ntfs.org, which seems to be hijacked by some company and mainly sells stuff. Because of course they do.
It is absolutely vital that I do not damage or lose access to the files on my “Liam’s Gameplay” HDD, and I can’t copy the files off it for backup. So I’d like to be certain there are no risks before changing ownership.
This is all making me wish I just set the HDD to ext4 in the first place, lol.
It’s that time of night again though sorry, so I’ll have to hop off and continue this tomorrow.
The following does not really help here, but rather verifies that OMLx works as intended. After realising that the system naturally, normally and magically recognises what is going on device-vise, I could do this:
[root@computer user]# truncate -s 10M tenebrae.temporalis
[root@computer user]# ls -l tenebrae.temporalis
-rw-r--r-- 1 root root 10485760 Feb 20 09:03 tenebrae.temporalis
[root@computer user]# losetup -f
/dev/loop0
[root@computer user]# losetup /dev/loop0 tenebrae.temporalis
[root@computer user]# mkfs.ntfs /dev/loop0
The partition start sector was not specified for /dev/loop0 and it could not be obtained automatically. It has been set to 0.
The number of sectors per track was not specified for /dev/loop0 and it could not be obtained automatically. It has been set to 0.
The number of heads was not specified for /dev/loop0 and it could not be obtained automatically. It has been set to 0.
Cluster size has been automatically set to 4096 bytes.
To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set.
Windows will not be able to boot from this device.
Initializing device with zeroes: 100% - Done.
Creating NTFS volume structures.
mkntfs completed successfully. Have a nice day.
[root@computer user]#
At this point Dolphin indicated new device, which was mounted. (So this is a one-click test.)
[user@computer ~]$ df /dev/loop0
Filesystem Size Used Avail Use% Mounted on
/dev/loop0 10M 2.5M 7.6M 25% /media/user/6BFBAFFD6D308508
[user@computer ~]$ cd /media/user/6BFBAFFD6D308508/
[user@computer 6BFBAFFD6D308508]$ ls -la
total 8
drwxrwxrwx 1 user user 4096 Feb 20 09:04 .
drwxr-x---+ 3 root root 4096 Feb 20 09:05 ..
[user@computer 6BFBAFFD6D308508]$ touch test
[user@computer 6BFBAFFD6D308508]$ mkdir testdir
[user@computer 6BFBAFFD6D308508]$ ls -la
total 8
drwxrwxrwx 1 user user 4096 Feb 20 09:07 .
drwxr-x---+ 3 root root 4096 Feb 20 09:05 ..
-rw-rw-r-- 1 user user 0 Feb 20 09:07 test
drwxrwxr-x 1 user user 0 Feb 20 09:07 testdir
[user@computer 6BFBAFFD6D308508]$ cd testdir/
[user@computer testdir]$ echo "OMLx rules!" > veritas.txt
[user@computer testdir]$ cat veritas.txt
OMLx rules!
[user@computer testdir]$
That was fun. So far 39 days being relatively pleased with this system and not planning to move away.
I suspect that this problem has to be solved from inside windows.
In one of the partitions I have windows7, not modern 11, so I can’t give you exact instructions, plus I’m going from memory.
Look for System > Disk Management, Partition Manager, Disks, or something similar and find the screen that shows the disk(s) with the partitions more or less as seen in Partiton Manager or GParted.
There should be an “Update” item (I see it on the right in a drop-down menu).
If I remember correctly I had clicked on the offending disk or partition before clicking Update but I can’t say for sure.
If windows and OM are on different disks, and you run dual boot from OM, I would recommend booting windows directly without going through OM’s grub (or any other possible Linux)
I’m a bit lost in this thread, so I may have missed you reporting wether you tried to “Update the disks status” from inside Windoze.
The only thing I did in Windows was test if the drive could be accessed. I just double-checked, and I can both read and write data on the HDD when it’s attached to the Windows 10 laptop.
I didn’t get to come on here and continue with the thread today, sorry. And I’m very busy tomorrow, so I’ll have to come back in a couple of days time.
What about “REAL SHUTDOWN” on Windows system instead of “system hibernation”. I know that Windows 10 (11 maybe too) by default are using quick shutdown / startup settings which can cause a trouble with accessing NTFS volumes under Linux. I think it is worth trying to do normal shutdown with this disk connected under Windows.
Second guess would be to try filesystem scan and repair under windows on that drive.
When I have first tried OM ROME and I was configuring my internal drives with ntfs partitions in fstab, I had similar problems with read only mounted partitions. I have changed UID of my user to 1000 (instead of 1001) and I have installed and configured ntfs-3g instead of default kernel ntfs. After that they started to mount as read and write:
Is that assuming I’m dual-booting Windows, or does Windows shutdown even affect the drive across different devices? Because my Linux desktop PC does not and never has had Windows on it. I only have Windows 10 on my laptop.
I didn’t translate my way through that whole topic, I only went as far as the message I quoted from it.
