EXFAT Disk suddenly readonly, root has write access

1st Official Post

    Hey folks,


    my oms shares suddenly stopped working and while troubleshooting with root via ssh on my omv machine, i can still edit files. I checked permissions, only root has write access. Checking the mount options it looks like that:
    /dev/sdb1 on /srv/dev-disk-by-uuid-5034-83D0 type exfat (rw,relatime,fmask=0022,dmask=0022,iocharset=utf8,errors=remount-ro)

    Seems like fmask and dmask 0022 is causing root only. What did happen and how can i fix that?


    Greetings

    Andre

    exfat does not carry linux permissions as it is not a linux native filesystem. The same is true of ntfs. Using filesystems that do not allow for linux permissions on a linux machine normally are only root writeable.


    Please don't fight saying it used to work. If it did, you were very lucky, it was proably a random fluke, and I can't explain why it did, but if you want linux to operate fully and correctly with your drives, they must be a linux filesystem so those non-root permissions can be set.


    Best advice is to copy the data off the drive. wipe it, make a linux filesystem and copy the data back.

    Edited 2 times, last by BernH: fix typo ().

    I was able to gain write access from Windows to an exFAT drive shared from my OMV server (an Intel i5, not a raspberry pi) by following this guide:

    Adding Support for exFAT on the Raspberry Pi
    Learn how to utilize exFat with Raspbian.
    pimylifeup.com

    I installed the "exfat-fuse" package and then, in the /etc/fstab file, edited the entry for my exFAT drive to use the mount options in that guide: defaults,auto,umask=000,users,rw 0 0



    EDIT: Modifying fstab is only a temporary solution due to:

    Quote

    As mentioned before in the FAQ openmediavault takes full control of some services, making it difficult to intervene configuration files. Changes manually added to configuration files will eventually overwritten at some stage by the openmediavault system.

    For a permanent solution follow these instructions from the OMV documentation.

    • Official Post
    Quote from omv4nas

    I was able to gain write access from Windows to an exFAT drive shared from my OMV server (an Intel i5, not a raspberry pi) by following this guide:

    Adding Support for exFAT on the Raspberry Pi Learn how to utilize exFat with Raspbian. pimylifeup.com

    I installed the "exfat-fuse" package and then, in the /etc/fstab file, edited the entry for my exFAT drive to use the mount options in that guide: defaults,auto,umask=000,users,rw 0 0

    exFAT is not supported in OMV, and NTFS is only supported for interim data copying purposes. https://docs.openmediavault.or…/storage/filesystems.html

    Forget about Windows file systems on a Linux system, they will only give you problems.

    I am having a similar issue, but the volumes on my server run a mix of EXT4 and BTRFS. One of my volumes I can still create files / folders to the root directory but existing subfolders I cannot write to. The other remaining 5 volumes on the server I cannot write to at all. Reading from all 6 volumes isn't any problem whatsoever. I'm not sure what caused the write issues. Up until recently, I was able to sync files across to the server from my laptop using Krusader to any volume I wished with no issues. Now, there's nothing apart from the one volume I mentioned earlier in this post. Any helpful advice is welcome! Thanks!


    P.S. I've attempted write tests to the server using a variety of OS's including an iPhone 8 using OwlFiles! No bueno!


    Technical info: Server runs OMV7.1; Laptop runs AntiX 23.1; another laptop using Win 11

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login