Apps unable to read/write to files on separate internal drive (Fedora 40)

Hey, I’m new to Linux and Fedora and I’ve mostly got a functional setup (first 80% was fine but the last 20% has been a real struggle), but I’ve been having issues with certain apps being unable to properly access or save files on a mounted drive, and I’ve tried all the basic pieces of information that I can find so here I am :smiley:

ISSUE
Certain Flatpak apps like Blender (from the Flatpak repo, not the Fedora repo version, learned the hard way that version is worse) and Obsidian will fail to read and/or write files from my mounted internal drive.

  • Fedora is installed on a separate internal drive.

  • Moving data to the home folder fixes the problem but is not an adequate solution for me, Windows has no issues reading and writing to this drive and this storage drive lets me better backup and use this data across operating systems.

  • Blender can read files from the drive but will refuse to write, saying the file path ‘is not writable’

  • Obsidian will refuse to open any folder on the drive, saying “Failed to open. no permission to access folder”.

  • I’m pretty sure Bottles also has issues reading and writing data from storage but it lacks a lot of warnings and helpful information that would let me determine that.

FIXES TRIED

  • Tried using Flatseal to give Blender and Obsidian permission to all files
  • Tried using Flatseal to give Blender and Obsidian just permission for the mounted drive.
  • Tried changing the mount options for the Storage drive based on information I could find(umask=0,uid=1000,gid=1000,x-gvfs-show,x-gvfs-name=Storage%20%28Z%29).


I assume there’s likely an issue with the drive permissions, but as someone who’s new to Linux the answer isn’t obvious to me and I don’t want to blindly input terminal commands that people have suggested online without understanding why apps can’t read/write to this drive and what the requirements are.

The fact the drive and enclosed folders says “Create and Delete Files” but not provide an option to Read or Write seems like the missing link, but messing with permissions is such an easy way to break an OS and there’s no UI or OS hints as to what Fedora expects.

If someone knows what the problem is and could also explain to me why it isn’t working I would very much appreciate it.

I’ve tried a few more things since and eliminated Flatpak as the source.

  • Tried creating an override for the application to have full permissions (sudo flatpak override md.obsidian.Obsidian --filesystem=host)
  • Tried updating and repairing Flatpak (sudo flatpak repair)
  • Tried running the Obsidian AppImage rather than Flatpak, same problem.
  • Tried running Blender using their tar.xz file, same problem.

:upside_down_face:

OKAY I FOUND THE SOLUTION

The solution that worked for me is ntfsfix, apparently using one drive on multiple OSes can cause an unclean drive and require repairing.

sudo ntfsfix <device-name>

It’s weird that nothing in the OS alerted me to this malfunction but I’m extremely relieved that it’s fixed.

1 Like

To have a clean drive when shutting down windows you MUST disable fast boot within windows. Doing so ensures that the drive is left in a ‘clean’ state so it can be opened by linux.

The ntfsfix app really should not be used regularly since the cause is the way windows is shutdown and not an actual problem when windows is not using the fast boot procedure.

2 Likes

Ill keep that in mind, thanks for the explanation.

Just a quick reply for anyone who sees this in the future:

  • You MUST disable Windows Fast Boot, the OS doesn’t leave internal drives in a “”“clean”“” state when it shuts down using Fast Boot in order to make the booting process fast.
  • This needs to be done within the Windows OS (under Control Panel > Power Options)
  • This also needs to be done in the BIOS settings (press F2 / F12 when your computer boots and look for Fast Boot under Boot Options).

You may still have to use nftsfix once when you’re done with this, but you wont have to do it again afterwards.