Cant write or delete on newly attached drive in KDE-Plasma

[Eadwine Rose]

Please click the checkmark of the post that holds the solution to mark the topic solved proper, so people will get guided to the solution, thanks :)

[m_pav]

First thing I do when setting up a dual boot machine with Windows is to disable Fast Startup. Honestly, with a NVME SSD this setting is totally unnecessary and it is the exact reason for the issue you're experiencing, and I have found a SATA SSD to be much the same, only a little slower. With this setting disabled, it will make no difference if you have 10 folders open when you shutdown or exit, all "open handles" to the folders will be lost as the windows system shuts down, and it's those open handles that are causing you the problems.

On a professionally maintained Windows 10 system, even one that is 3-4 years old, the gains at startup are simply pushed to the opposite end as Windows compresses the contents of the open sessions into a hibernation file on the root of C:, with the only exception being crappy antivirus and/or security packages. I challenge anyone to prove me wrong because compression and writing to storage takes longer than reading and decompressing to RAM.

Follow the steps below in Windows to disable the setting.
1) Settings -> Power and Sleep Settings -> Additional Power Settings -> Chose what the Power buttons do -> Change settings that are currently unavailable -> Uncheck Fast Startup and reboot 2x to allow the cache to clear properly.

Some BIOSs' need to have their implementation of Fast Boot disabled too, but I generally disable that as well while disabling Secure Boot.

Furthermore I see you're using the stock Debian kernel, that is a benefit in your case because for the time being, the Debain kernel loads the ntfs-3g driver, not the Paragon ntfs3 driver, as do most other kernels like the Liquorix and Xanmod. The ntfs3 driver has more features and as such, it can read NTFS permissions, however, because Windows uses a different starting UID value for its user accounts, this will translate to a padlock indicator being displayed in all Windows user profile folders in C:\Users\<username> folders, even after a clean shutdown.

In such an instance, the KDE root actions servicemenu would suffice to give you the R/W permissions you desire, but for the sake of those that might visit this thread in the future who prefer to use the Liquorix or Xanmod kernels and do not wish to always operate as root on Windows filesystems, simply do the following and reboot.

Code: Select all

sudo rmmod ntfs3 && echo blacklist ntfs3 | sudo tee /etc/modprobe.d/blacklist-ntfs3.conf

--Edited to remove errors--

[Wal]

Excellent explanation thanks!

[sunrat]

On a professionally maintained Windows 10 system, even one that is 3-4 years old, the gains at startup are simply pushed to the opposite end as Windows compresses the contents of the open sessions into a hibernation file on the root of C:,

I tested this once. Fast Startup improved startup time by 2 seconds, but shutdown was 10 seconds longer!
Windows Fast Startup is snake oil.

[FullScale4Me]

Some BIOSs' need to have their implementation of Fast Boot disabled too, but I generally disable that as well while disabling Secure Boot.

A miss-named feature IMHO. It should be 'Fast Post' as it occurs before any boot-up commences.

There have been a few cases in this forum where the WiFi card was not initialized due to this being disabled. Oddly in some of those, it still worked fine in Winblows.

Fast Boot set to 'Enabled', 'Automatic', or 'Thorough' fixed those reported issues.

[grelos]

I am facing the same problem but I am not on dual boot with win. I am running Mx 23.3 with KDE and lately my non-system HDDs are mounted read-only. What is strange is that when I check permissions in Dolphin it says "user" and not "root" but in fact I cannot write on them.
The cumbersome workaround is to change permissions in Dolphin, log-out and log-in again. It seems these permissions are changed when I shutdown the system overnight.

[Eadwine Rose]

@grelos Please start your own thread.

[Kermit the Frog]

... seems these permissions are changed when I shutdown the system overnight...

If it's ntfs the permissions / ownership won't be saved. So, when they're unmounted, mount them like this, manually:


i.e.

sudo mount /dev/sdc3 -t ntfs-3g -o permissions /media/yourusername/Somedirectory


... "Then" chown :

sudo chown -R yourusername:yourusername /media/yourusername/Somedirectory