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

    ROM state not saving over network

    Scheduled Pinned Locked Moved Help and Support
    savestatesmountnetwork
    5 Posts 4 Posters 846 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
      pmdci
      last edited by

      Not sure why ROM states are not saving.

      I got my ROMS located on my network server (NAS), and I am mounting it via the autostart.sh file, as documented here.

      Here is now my autostart.sh file looks like:

      sudo mount -t cifs -o username=retropie,password=********,nounix,noserverino //SERVER/Software/Games/roms/ /home/pi/RetroPie/roms/
      emulationstation #auto
      

      However when I try to save a game state, I just get a 0% on the screen and nothing else.

      I went to the shell and I tried doing some stuff on the mounted roms directory, such as mkdir something or creating a test.txt file. I could write in the shared drive as long as I ran it with the sudo command. If I don't run it with the sudo command, I get an access denied message. Maybe this is the problem?

      Any thoughts on what I might be doing wrong?


      Raspberry Pi 4, 8GB RAM
      SanDisk Ultra 64 GB microSDXC Memory Card (A1, Class 10, U1)
      Official Retropie Image for Pi 4/400
      Official Raspberry Pi 4 USBC-C power supply
      Argon ONE V2 Raspberry Pi 4 Case

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

        @pmdci said in ROM state not saving over network:

        I get an access denied message. Maybe this is the problem?

        Yes, the (normal) user is not allowed to write so you can't save there. Add uid=pi to the mount options and see if you're able to write there.

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

          @mitu

          Story of my life.... As soon as I decided to ask a question, I find the answer.

          According to the documentation (at the very end), there is a line that says I should replace my mount command with the following:

          sudo mount -t cifs -o sec=ntlmv2,username=something,rw,file_mode=0777,dir_mode=0777,password=********,nounix,noserverino //SERVER/Software/Games/roms/ /home/pi/RetroPie/roms/
          

          That solved the problem.

          I wonder however what would be the difference between this whole new line, versus your suggestion of just adding uid=pi to my previous line. Would you know?


          Raspberry Pi 4, 8GB RAM
          SanDisk Ultra 64 GB microSDXC Memory Card (A1, Class 10, U1)
          Official Retropie Image for Pi 4/400
          Official Raspberry Pi 4 USBC-C power supply
          Argon ONE V2 Raspberry Pi 4 Case

          ZangdaarrZ 1 Reply Last reply Reply Quote 0
          • ZangdaarrZ
            Zangdaarr @pmdci
            last edited by Zangdaarr

            @pmdci Late reply, but my comprehension is that uid=pi woud give rights to the user pi while what you are doing gives writting rights to everyone

            The user you used to mount the drive was not the user trying to write and this is why your states could not be saved.

            I wonder if it is possible to create a user pi on the nas and avoid this but I don't think so. What is strange is that loging directly on the raspberry using the pi user you can write over the mounted nas drive, but not once in the retropie system itself.

            S 1 Reply Last reply Reply Quote 0
            • S
              SwampyFox @Zangdaarr
              last edited by

              @Zangdaarr Another Late Reply - I came across this while trying to figure out why Hi Scores were not being saved while trying to write using ROMS on a network share. I had given the User I had created access rights, however, I believe that the rw (read/write) and the file/dir mode of 777 (read, write and execute (I believe)) is the secret sauce. Glad that this is in the User Guide...but, just overlooked by me until today.

              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.