Running ROMs from a Network Share

dyers

Can anyone confirm that they are able to run zipped roms over the network shares? I've setup a network mapping to the entire /home/pi/RetroPie folder and copied the data over scp to my windows file server. Everything shows up but only non zip roms work, i noticed the pattern and then unzipped a single file from each emulator and indeed it's the compressed files that create a problem. Has anyone else run into this? I'm using a pi3. I've tried option 1 and 2 from the guide and both have the same impact.
I do have an upgraded install so my next step is to totally start over.

Edit: adding some more details, I've checked the logs, they appear identical to working launches, some emulators just stall doing nothing, shift+x brings retroarch menu up, so it isn't hung. Other's just bomb back to the rom list.

dyers

My problem might be related to this: https://github.com/libretro/Lakka-LibreELEC/issues/115

Haris1977

@zehjrack i have the exact issue my self. Everything plays fine EXCEPT FOR mame roms..

I opened a new thread also here . Have y managed to fix it? I am out of ideas....

Haris1977

@spieddy said in Running ROMs from a Network Share:

to modify Fstab and everyting works fine

How did y do that? I am having same issue with my mame roms. All other roms are ok.

Anyone else is having problem with mame roms (not working)?

Haris1977

Well i ve finally managed to run all of my games (mame roms too) by just following option 2 (unfortunately option 1 didnt work 4 me) from here. I ve also managed to wake my nas server first (as most of the time is in "sleeping" state) , wait some time (in order for the samba to work) and then mount the samba share. Works as expected.

Thanks again for the info :-)

Guy-Sensei

@haris1977 Would you mind giving more details about how you solved this? Specifically, what is your command in fstab for option 2?
I have the same problem (see my post above from 2 months ago).

ringnutz

@guy-sensei

I had the exact same issue. It is not the fstab part that is important here but the options. Specifically one of "nounix,noserverino,defaults,users,auto". I have not deduced which one fixed it, but I am using the Autostart.sh and it works fine as follows

sudo mount -t cifs -o gid=1000,uid=1000,username=USER,password=PASS,domain=DOMAIN,nounix,noserverino,defaults,users,auto //192.168.X.X/SHARENAME /home/pi/RetroPie/roms

Note that you may not need domain above for your share.

After unmounting and remounting the share using the above arguments, I am now able to launch Mame2003 Roms just fine.

Haris1977

@guy-sensei sorry for the late answer

Mine fstab looks like this:

//192.168.X.XXX/SHARENAME /home/pi/RetroPie cifs username=XXX,password=XXX,nounix,noserverino,defaults,users,auto 0 0

proxypunk

I had serious trouble getting Samba share to work!
After hours of trying, I figured out it has something to do with the network interface not being ready, although I enabled waiting for network on boot.
Finally I ended up starting kodi before sudo mount and afterwards emulationstation in autostart.sh.
Like this:

kodi
sudo mount -t cifs -o sec=ntlm,user='username',password='password' //hostip/roms /home/pi/RetroPie/roms
emulationstation

Ofc, I gotta quit Kodi each time to get to EmulationStation. If you don't need Kodi, you could try it with sleep x (x=seconds to wait) instead.

nightmaresteam

For people using Windows 10 you need to have SMB 1.0/CIFS File Sharing Support enabled in windows features for this to work. I just enabled that and now my network share is working.

mitu

@proxypunk You could just add a sleep 8 before running emulationstation just so the mount succeeds before ES start and leave the normal mount working from fstab. If 8 seconds is not enough, you can start increasing the wait period until you get the correct number of seconds.

BlackMage

Found a solution to your save and scrapping issue. if you simply add:

,rw,file_mode=0777,dir_mode=0777

after the username and password in your autostart.sh it will give your write access and will allow you to scrap and save to the NAS

Just be sure that access permissions are set correctly on the Windows share, including all sub-folders that you wish to share or else it will still not work.

This allows you to keep saves and scraps on the network and for a setup like mine where i have multiple RetroPies in the house this allows me to create a save folder for each Pi that way we are not overwriting each others saves

EVH

Hi guys,

I need some help with running my roms from a Synology NAS.

Despite following the guide, I can't get any of my systems or games to appear in RetroPie. I've tried putting a line in autostart.sh which didn't work and I've tried using fstab to no avail :(

I'm running a pre-made image of the latest build - RetroPie 4.4 on a Raspberry Pi 3B+ connected to my home network via ethernet. My Synology NAS is running on IP 10.0.0.10 and has a "Media" cifs share with guest access.

The line I've added to autostart.sh is:

`sudo mount -t cifs -o username=xxxxx,password=xxxxx //10.0.0.10/Media/RetroPie/roms /home/pi/RetroPie/roms

If I try "sudo mount -a" I don't get any errors, but I still don't see what the issue is. I've even tried using the hostname of the server e.g. "SYNOLOGY" in the path and it doesn't work.

Help!

mitu

@evh If the share name is Media, then the mount command is not correct. You can't mount arbitrary folders inside a share, you should mount the share itself.
My advice is to create a different share and name it RetroPie-Roms, then follow the docs and add the share to the /etc/fstab file to be auto-mounted to /home/pi/RetroPie/roms. Restart and see if the share is correctly mounted, then restart Emulationstation and see if the ROMs from the share appear in the list.

EVH

@mitu said in Running ROMs from a Network Share:

@evh If the share name is Media, then the mount command is not correct. You can't mount arbitrary folders inside a share, you should mount the share itself.
My advice is to create a different share and name it RetroPie-Roms, then follow the docs and add the share to the /etc/fstab file to be auto-mounted to /home/pi/RetroPie/roms. Restart and see if the share is correctly mounted, then restart Emulationstation and see if the ROMs from the share appear in the list.

Makes sense, I'll try it later and update.

The docs suggest that the path can contain folders... which I wrongly assumed would work.

sudo mount -t cifs -o username=something,password=something **//REMOTEHOST/path/to/roms** /home/pi/RetroPie/roms

EVH

Well, I can confirm it still doesn’t work.

Mounting a cifs share called RetroPie and having all the usual folders inside didn’t work.

I even tried appending the path to 10.0.0.10/volume 1/RetroPie/roms thinking that maybe I needed the volume name but I couldn’t get it working.

I’m almost about to give up which is a shame because I’ve got a NAS full of roms that I want to use and only a 16GB SD card :(

mitu

@evh Is the remote share mounted if you issue the command manually ? Does mount -a works after you set up the fstab ? Is there an error when you run the mount command ?

EVH

@mitu said in Running ROMs from a Network Share:

@evh Is the remote share mounted if you issue the command manually ? Does mount -a works after you set up the fstab ? Is there an error when you run the mount command ?

I gave up on cifs and finally got it working through NFS. Not sure which is better, but I was able to mount my folder inside the Media share i.e. 10.0.0.10/Media/RetroPie/roms which is good as it means less "what is this retropie thing" questions from the other half :D

qrayg

Just in case someone comes into this topic and none of the posts in this thread or the wiki solves their issues (like what happened to me). Here's how I got mine working. I'm using an ASUS RT-AC86U router with a Network Place (Samba) Share on a Raspberry Pi 3 B running RetroPie 4.4.x:

Mount:
sudo mount -t cifs -o username=xxx,password=xxx,vers=1.0 //server/path/to/roms /home/pi/RetroPie/roms

Notice the vers=1.0. That was the only thing that would make the mount work for me. I found that option on a Linux support forum.

Permissions:
sudo chown -R pi /home/pi/RetroPie/roms

I tried every variation of sec, file_mode, and dir_mode, but no matter what I did my gamelist.xml, save states, battery saves, etc. would not get created or updated. After chowning the newly mounted shared rom folder, everything worked like a charm.

bolski

@ringnutz said in Running ROMs from a Network Share:

@guy-sensei

I had the exact same issue. It is not the fstab part that is important here but the options. Specifically one of "nounix,noserverino,defaults,users,auto". I have not deduced which one fixed it, but I am using the Autostart.sh and it works fine as follows

sudo mount -t cifs -o gid=1000,uid=1000,username=USER,password=PASS,domain=DOMAIN,nounix,noserverino,defaults,users,auto //192.168.X.X/SHARENAME /home/pi/RetroPie/roms

Note that you may not need domain above for your share.

After unmounting and remounting the share using the above arguments, I am now able to launch Mame2003 Roms just fine.

I know this is old, but thank you! This worked! Those extra options at the end allowed me to play Mame from my NFS file share, whereas before, everything BUT Mame worked.