RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    Unable to successfully mount a share from Diskstation NAS

    Scheduled Pinned Locked Moved Help and Support
    diskstationbtrfsfstabautostart.shmount
    11 Posts 4 Posters 4.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      pyr0cide
      last edited by pyr0cide

      Hello,

      I have read a few posts on here, lq.org, ubuntu forums and /r/retropie to no avail. I have a Synology DS416j with 2 separate shares I have been trying to get just one of them mounted to use, one that is a standard share browseable via smb and cifs on MacOS and Windows, and a newly created NFS share to trying nfs mounting

      I am trying to mount my RetroPie formatted roms folder to the ~/RetroPie/roms folder on my RPi2 running fresh 4.4. Blew it away moments ago to start fresh with help.

      I am not a linux newbie, but I have not had a running retropie since 3.x, so undoubtedly there have been several big changes.

      Pi Model or other hardware: 2B, no OC
      Power Supply used: Anker Wallwart 9v, 2.4A (I have an official RPi wallplug on order)
      RetroPie Version Used: 4.4
      Built From: Premade v4.4 image from Retropie website installed with Etcher
      USB Devices connected: Edimax EW-7811Un
      Controller used: F710 not plugged in
      Error messages received: Error 95 Operation unsupported when using autostart.sh, no error with fstab, just never mounts
      Log found in /dev/shm/runcommand.log (if relevant):
      Guide used: https://github.com/RetroPie/RetroPie-Setup/wiki/Running-ROMs-from-a-Network-Share
      File: /opt/retropie/configs/all/autostart.sh
      Emulator: n/a

      Attempt 1: autostart.sh

      #sudo mount -t btrfs -o username=pi,password=raspberry //192.168.1.6:/Games/Emulator_ROMS/ /home/pi/RetroPie/roms

      I have edited /home/pi/.emulationstation/es_systems.cfg to use my own server folder names for the rom locations.

      Running sudo ./autostart.sh gives me the Error 95, Operations not support mount.cifs

      Attempts 2: /etc/fstab with nfs share

      #//192.168.1.6:/volume1/roms /home/pi/RetroPie nfs username=pi,password=raspberry,nounix,noserverino,defaults,users,auto 0 0

      sudo mount -a results in no errors but mount point doesnt have anything from NAS in it. I have tried using domain name in place of IP in both attempts with similar results.

      So not really sure where to go from here. I have not previously tried mounting from this NAS. It's FS is btrfs.

      caver01C 1 Reply Last reply Reply Quote 0
      • caver01C
        caver01 @pyr0cide
        last edited by

        @pyr0cide I have a DS414 running DSM 6.1.6-15266. I have not tried to mount via scripts at startup, but I have always used Kodi on the Pi, including my current install of Kodi via RetroPie to mount and playback media from the DS without any problems at all. Perhaps you have done the same.

        So, that said, there must be a way to make the same connection outside of Kodi at the CLI.

        I don't have direct answers, but I am curious to find out how this discussion evolves and I can maybe do a few tests.

        My 4-player cocktail style cabinet built as a custom "roadcase"

        P 1 Reply Last reply Reply Quote 0
        • P
          pyr0cide @caver01
          last edited by

          @caver01 If i was using it for media playback that would be fine and most likely would be doing similar application of mounting through Kodi. However, the only use for this pi is for retro gaming and nothing else. I have not tried mounting through kodi and pointing the roms location in the es_systems.cfg to the kodi mount point though. Might give that a go later.

          I can ping the IP address no problems, but something in the syntax of auto mounting is bad and I am at a loss as to what it would be.

          caver01C 1 Reply Last reply Reply Quote 0
          • caver01C
            caver01 @pyr0cide
            last edited by

            @pyr0cide Understood. I was merely adding that the connection is definitely possible.

            My 4-player cocktail style cabinet built as a custom "roadcase"

            1 Reply Last reply Reply Quote 1
            • jamesnjJ
              jamesnj
              last edited by

              You might want to check the man page on mount for both smb and nfs methods, they are fundamentally different. From the line above I can't tell if you are trying to mount the CIFS or NFS share. NFS doesn't use username/passwd and is generally controlled by the server via IP/hostname. Also the mount option for nfs is "-t nfs". For NFS you would use something like this:

              mount -t nfs 192.168.1.6:/Games/Emulator_ROMS /home/pi/RetroPie/roms

              Some linux distros get confused if NFSv4 if not set up properly, so I would suggest adding to the above "-o vers=3" to force NFSv3.

              CIFS is completely different.

              I hope that helps.

              P 1 Reply Last reply Reply Quote 0
              • P
                pyr0cide @jamesnj
                last edited by

                @jamesnj

                Ok, I updated the autostart.sh to this

                #auto mount NFS share
                mount -t nfs -o vers=3 192.168.1.6:/volume1/ROMS /home/pi/RetroPie/roms

                Restarted to nothing mounted. Tried mounting manually using the same command and got access denied by server while mounting. Logged into the NAS and ran exportfs -a, restarted NAS and Rpi to the same thing access denied message.

                mituM 1 Reply Last reply Reply Quote 0
                • mituM
                  mitu Global Moderator @pyr0cide
                  last edited by

                  @pyr0cide Are you sure you configured the NFS server correctly ? Also, shouldn't you run the mount command prefixed with sudo ?

                  P 1 Reply Last reply Reply Quote 0
                  • P
                    pyr0cide @mitu
                    last edited by

                    @mitu

                    I just recreated the test NFS share on my nas thinking something wasnt configured correctly. Same thing.

                    And yes, the command was run with sudo when done manually. I just didnt have that included in the last comment. The autostart.sh does not need sudo prefixed.

                    mituM 1 Reply Last reply Reply Quote 0
                    • mituM
                      mitu Global Moderator @pyr0cide
                      last edited by mitu

                      @pyr0cide Can you post the logs from the server (the dmesg portion of the mount error) and client when you run the mount operation ?

                      P 1 Reply Last reply Reply Quote 0
                      • P
                        pyr0cide @mitu
                        last edited by pyr0cide

                        @mitu

                        This is the only thing that shows up mount via dmesg

                        pi@retropie:~ $ dmesg | grep "mount"
                        [ 1.022428] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
                        [ 1.023426] devtmpfs: mounted
                        [ 2.410068] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
                        [ 3.134143] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)

                        Is this what you were requesting?

                        And the manual mount error
                        pi@retropie:~ $ sudo mount -t nfs -o vers=3 192.168.1.6:/volume1/ROMS /home/pi/RetroPie/roms
                        mount.nfs: access denied by server while mounting 192.168.1.6:/volume1/ROMS

                        NFS share on NAS
                        pyr0cide@Home-NAS:/$ sudo cat /etc/exports
                        /volume1/roms 192.168.1.*(rw,async,no_wdelay,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100)

                        EDIT: Keep in mind, I don't really care HOW it is mounted, but I don't have a SD card large enough for all the roms and since I have a near infinite storage capacity on my NAS I would much rather have it mounted in whatever way I can get at this point. But I understood that NFS is faster than SMB and CIFS which is why I wanted to try it that way first.

                        mituM 1 Reply Last reply Reply Quote 0
                        • mituM
                          mitu Global Moderator @pyr0cide
                          last edited by

                          @pyr0cide Just leave the exports on the server

                          /volume1/roms 192.168.1.*(rw,async,no_wdelay,no_root_squash)
                          

                          And make sure you use the proper case when referring to the share name, i.e. not mixing upper-case with lower-case

                           mount -t nfs -o vers=3 192.168.1.6:/volume1/roms /home/pi/RetroPie/roms
                          
                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post

                          Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                          Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.