Hi,
I’m writing this trying to understand if it’s just a must to do by user or if it’s possible to automate some config changes when needed by critical OS elements.
To be more clear, I’ll show you an example.
Some days ago I’ve updated my KDE Neon, spent the PC. Some day later, I’ve started my PC and, as updates were completed, I had some “disk writing” fails by Steam, downloading new games updates.
As my Steam games are stored on a NTFS disk (I’m on dual boot with W11), I’ve started to check what’s wrong and it seems that the disk was mounted read-only. I’ve opened my fstab file and check it but as I’ve never touched it, I wasn’t able to understand what’s going wrong.
So, I’ve started a web searching and I’ve landed on a github page about the ntfs kernel module (I’m a newbie with Linux so, please, try to accept me if I’m not super specific) and there I’ve found some commands that should enable some usergroups that will have the rights to write on disk.
I’ve tried them but nothing change.
So, after a bit of negative mood, I decided to go here and try to do a search and I’ve found a post about the change on fstab type typo about the ntfs that will not be “ntfs” but it become “ntfs3”.
I’ve tried that suggestion and everything turned working again.
So, my question is: as this issue was generated by a changed kernel requirement, is it always a must for the user to be updated with these kind of changes or at least, when the problem occur, to find a solution or is it possible to create some “automation” that automatically fix the OS config files avoiding these issues?
Is it something impossible to do? too much variables to check and adjust?