rom folder on network not mounted at start #network

Stargrove1

Yes this option is set, I did follow the guide https://retropie.org.uk/docs/Running-ROMs-from-a-Network-Share/ telling to activate it

mitu

After you mount the driver - manually - do all your ROM folder appear correctly ?
Can you post your entry from /etc/fstab ?

Stargrove1

I used a new image whithout roms installed, when mounting manually, I checked with ls /RetroPie/roms/amiga and I saw the roms from my network, no matter if autostart or fstab method

fstab entry (copied and modified from the guide):
//mynas/Multimedia/Spiele/Retropie/roms cifs username=xxx,password=xxx,nounix,noserverino,defaults,users,auto 0 0

mitu

@Stargrove1 Are you sure it's the correct /etc/fstab entry ? You're missing the mountpoint (2nd position), which should be /home/pi/RetroPie/roms.

Stargrove1

Sorry, my mistake, it has to be:

//mynas/Multimedia/Spiele/Retropie/roms /home/pi/RetroPie/roms cifs username=xxx,password=xxx,nounix,noserverino,defaults,users,auto 0 0

Stargrove1

Entry in the autostart.sh is:
sudo mount -t cifs -o username=xxx,password=xxx,nounix,noserverino //mynas/Multimedia/Spiele/Retropie/roms /home/pi/RetroPie/roms

mitu

The /etc/fstab entry seems fine. Can you try adding x-systemd.automount to the mount options and reboot to see if it's auto-mounted on start ?

Stargrove1

When changing to

//mynas/Multimedia/Spiele/Retropie/roms /home/pi/RetroPie/roms cifs username=xxx,password=xxx,nounix,noserverino,defaults,users,auto,x-systemd.automount 0 0

no roms available, I tried to do sudo mount -a, the output is

/sbin/mount.cifs: invalid option -- 't'

Usage:  mount.cifs <remotetarget> <dir> -o <options>

Mount the remote target, specified as a UNC name, to a local directory.```

mitu

@Stargrove1 I don't get that error if I test with a local address. What version of RetroPie are you using (see https://retropie.org.uk/forum/topic/3/read-this-first) ?

Stargrove1

Version states 4.4.11

mitu

Sorry, can't figure out why this doesn't work. Try looking in the dmesg output after the boot or adding a larger timeout before ES starts in autostart.sh.

Stargrove1

Thank you very much for the help, I will continue setting up the Retropie with local roms and try again with a spare Pi to get the network solution running.

Stargrove1

Today I tried again with a new reflashed image on my pi zero w, I just added Wifi and autostart.sh entry and it worked fine. Guess I will just start over with my pi 3 to get the actual system running from network.

Thank you for your support