I’m about to move away from Google, and I am redoing my self-hosting setup.

Right now, I’m running unRAID and Virtual DSM (Docker).

However, one thing that somehow bothers me, is, that all DSM files reside on a virtual disk, which is passed to the Docker container.

To access these files, I created a share synology, exported it via SMB in unRAID, and used mount -t nfs 172.17.0.2:/volume1/homes/xxx /mnt/user/synology to mount the files from the DSM docker container onto the share. This way I can access them via SMB from within the LAN.

My idea was to have a share in unRAID, and have that mounted into DSM. So exactly the opposite of what I’m doing now. This however works only partially. The mounted share only shows up in File Station, but not in Synology Drive. I went so far to ssh into DSM and tried to mount the share manually AND using mount --bind to mount it inside the users home folder, but without luck. When doing so, Synology Drive wouldn’t let me interact at all. Not even when mounting it onto a sub-dir within the users home-directory.

Did anyone else have this same crazy idea and managed to solve it?

  • RotaryKeyboard@lemmy.sdf.orgEnglish
    1·
    1 year ago

    I fully admit I’m not the most talented linux person, but you say that you created an smb share on Unraid, but you mounted it as if it were an NFS share. Is that just a typo, or could that be the root of your problem? I could imagine Synology Drive not letting you interact with files in the mounted folder if the permissions and ownership weren’t set up right.

    • adONis@lemmy.worldOPEnglish
      2·
      1 year ago

      Regarding the SMB-share, let my try to clarify. Let’s say you have 3 machines. 192.168.1.10/20/30. On machine 10 a folder synology which has a network folder mounted onto it from machine 20 mount -t nfs 192.168.1.20:/some/folder synology.

      Now you want to access that folder on machine 30. Here you can’t use mount -t nfs but MUST use mount -t cifs instead, because you cannot forward a mounted share. However, this is not the problem, it’s just a description of my current setup.

      Regarding the ownership. Your point is very valid, but I ruled that out already. I did a so-called bind-mount within Synology with the exact user permissions as in the users home folder, but this didn’t work. FYI: a bind-mount is where you have two folders /foo (with many sub-folders and files) and /bar (empty). If you do mount --bind /foo /bar, then the system thinks that bar is a real folder with the subfolders and files (from foo, including their permissions).