I use Windows and Arch Linux. I have two NVMe drives, one with all my operating system partitions and the remaining space dedicated to an NTFS data partition, and the other completely dedicated to an NTFS data partition.
If I mount my two NTFS partitions via Dolphin, some of the folders there are locked and I can’t write any data to those folders. But, if I mount the same partitions using sudo mount ..., everything works. I have complete write access across all my data. Note: this is not the C: drive, I’m accessing data only partitions, there are no OSs stored on these partitions.
I’m using Dolphin on KDE Plasma. I have been mounting my partitions using the sidebar because they appear there. They’re not removable drives, they’re local drives/partitions, so they don’t appear in Disks & Devices.
I wonder what plasma version that is. With my plasma 6.1.5 there’s no longer a “Removable Devices” in system settings, that screen is called “Device Auto-Mount”.
Okay, so Disks & Devices has an option to show Non Removable Devices, so I mounted them there. But, the situation is the same. When KDE Plasma mounts the drives, some folders are locked and some aren’t, which again, is not the same with sudo mount ...
generally ntfs partitions do not allow ownership permission by file/folder, so maybe dolphin has confused the permissions somehow.
have you tried just changing the owner of the ntfs partitions to be your user. so they don’t have any conflicts?
when i look at any of my ntfs partitions (and all the files and folders within) they are all owned by my user, so there is no issue mounting them or accessing them.
@muizz , what filesystem driver are you specifying when you use the mount command directly? Adding the rest of that command, obfuscating any unique IDs or anything of course, might help tease apart the differences.
It used to be sudo mount /dev/nvme0nXpX /run/media/muizz/<LABEL> manually after looking at lsblk.
Now it’s sudo mount -L <LABEL> /run/media/muizz/<LABEL>
Both commands are ran after making the folder myself. Both commands mount the drive in the exact same space Dolphin reserves for the drives in its UI already.
Rather than -L, I prefer the LABEL=<label> syntax, because that’s what can be used in /etc/fstab.
For an NVMe device, usually it’s plugged in to the motherboard or a daughter card, rather than “removable”, so IMO an entry in /etc/fstab is appropriate. There, you can include the options noauto,user, and dolphin will use the entry’s mount point if you click on it. Handy also if you want to use options to set the file permissions.
This itself involves another headache, the whitespace characters. \040 doesn’t work, even though Dolphin can clearly interpret it as a spacebar, and \134x20 which was generated by genfstab definitely doesn’t work. FYI, those folders are autogenerated by KDE when you try to mount the drives.
However, just using fstab and mounting with defaults and not using noauto,user,... worked. I distinctly remember not being able to log into Arch one time because of that (maybe the \134x20 character instead) which is why I have been mounting it manually, but KDE Plasma/Dolphin can’t do that.
Yes, mounting them with sudo IS a bit different from mounting them as your user – which is what the automount tool is doing.
Also, using the /run/ directory when manually mounting them on the command line may be part of the problem. Isn’t /run a sort of temporary and ‘ephemeral’ location that gets recreated for each new login session? Manually mounting on the command line there with sudo might be a problem area perhaps?
If using a permanent mount via fstab, try using a ‘normal’ location.
On my neon and Kubuntu systems, automount stuff goes to /media/username/some-dir so I put my permanently mounted stuff to /media/some-dir for some consistency.
I’ve observed another difference between (naively) mounting an NTFS partition from the command line, and using the KDE Disks&Devices tray icon:
From the command line, my system (gentoo x86_64) defaults to the fuseblk based ntfs3g implementation; whereas when mounting via Disks&Devices, the ntfs3 kernel filesystem module is used.
For me in a certain use case this actually turned out to be a real issue, since I encounter a kernel bug in ntfs3. … OK I can’t post links here, it’s #219473 on bugzilla <dot> kernel <dot> org
How can I configure the KDE Disks&Devices thing for specific filesystem driver preferences, and/or to honor the same fs driver search order as a simple mount command?
