write-access issue

  • I just set-up OMV 5 as follows:


    My NAS -- 2 x 2TB drives in external USB 3 enclosures plugged into my Raspberry Pi 4B 2Gb system running Raspberry 32-bit OS.

    Installed OVM 5


    -Created 2 file systems using the 2 x 2TB drives. Filesystems are formatted in ext4. The I mounted the file systems.


    - Added 2 shared folders using the file systems above


    - Installed UnionFilesystems plug-in

    - Added share in UnionFilesystems using the 2 shared folders as the branches


    - Added a new shared folder using the share created in UnionFilesystems


    - Started service SMB/CIFS

    - Added a new share in SMB/CIFS using the file share created with UnionFilesystems. Set public to "guests allowed".


    Mapped a network drive in my Windows 10 system using the NAS created above.

    I can't write to the root directory.



    What did I do wrong?

  • Michael-95037

    Changed the title of the thread from “Sub-directory write-access issue” to “write-access issue”.
    • Official Post

    - Installed UnionFilesystems plug-in

    - Added share in UnionFilesystems using the 2 shared folders as the branches

    RE: Mergerfs guide

    If you want to join folders maybe you should use mergerfs instead of unionfs. If you already have unionfs installed, the easiest thing is to join the two disk mounts. Eliminate the step of creating a folder on each disk.

  • OK. I've deleted ALL the shared folders. I then used UnionFilesystems to branch together to 2 Disk mounts/file systems.


    I then added it as a shared folder, with read/write access for everyone, since I can't add it into SMB/CIFS unless it's already a shared folder.


    I then added the shared folder as a share in SMB/CIFS with Public set to Only Guests.


    I'm getting the same error when I attempt to create a folder on the network drive.


    It appears there is something on the Linux side that is preventing access, but I can't figure it out.


    I also tried adding this on the Pi


    sudo chown pi:pi /dev/sda1

    sudo chmod 777 /dev/sda1

    usdo chown pi:pi /dev/sdb1

    sudo chmod 777 /dev/sdb1


    It didn't help either.

  • FIXED!!!


    Using a desktop version of Raspberry OS, I was able to see a little more. Somehow the drives became owned by root and the update field was set to owner-only. I opened a command window and gave the drives to pi using chown, set all permissions to everyone in the desktop. Rebooted and it worked. I don't know how/who/why it became owned by root, but it's fixed.


    Other strange thing was a folder called 'Lost+Found' was created. I had to sudo su and rmdir it in order to set the permissions to everyone.


    Life is good in the NOOB Linux world again.:):S:)

Participate now!

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