This one is fixed now.

Did a chkdsk on Windows and repaired the drive.

All working now.

@mitu said in Trying to mount roms folder from a Synology NAS using NFS:

kind of was. You have a menu in the RetroPie system which is titled Show IP, which does exactly that - displays the network address of your RetroPie system.
Glad you got it sorted out in the end.

Well I didn't know it ! Thanks for letting me know :)

I realize you have resolved the issue, but I thought I might contribute something.

A lot of people don't realize that the quality of the MicroSD card makes a big difference for running Raspberry Pi operating systems. High-speed is important, with a minimum of Class 10 (I know, newer/faster standards now exist) always being recommended. However, the endurance of the card (or the number of writes/re-writes it can handle) is just as important. There are "high endurance" or "industrial grade" MicroSD cards available that should do a better job than run-of-the-mill MicroSDs with Class 10 ratings and will have a longer life-span.

MicroSD cards were meant for storage, for photos and the like. Running an OS from a MicroSD card causes a lot of heat due to random reads/writes happening almost constantly. For the most part, they weren't designed for this purpose and the extra wear and tear can cause early failure.

Of course, running your OS from a real SSD would be best but that's tricky to get working right on a Pi4 (and probably not worth doing on anything older).

@code_dredd said in Issues when mounting more than just ROMs over NFS:

It seems NFSv3 didn't really fix the issue and ran into others (e.g., weird user IDs on remapping). I've gone back to NFSv4 and increased the number of NFS servers/processes from the default of 4 up to 5 to see if that helps.

It didn't help.

@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.

@muldjord said in Skyscraper not writing to mounted emulationstation NAS folder:

@beatbox32 Everything looks good, including your mount. Did you remember to re-generate the gamelists from the RetroPie Skyscraper script? Scraping the data simply add it to the Skyscraper cache located at /home/pi/.skyscraper/cache (which is also a symbolic link if you installed Skyscraper from the RetroPie script). But you need to re-genereate the gamelists for it to create the necessary ES gamelist.xml files and artwork files in the /home/pi/.emulationstation/downloaded_media/ platform folders.

Remember to push space for each platform when generating the gamelists to select them.

EDIT: Skyscraper also checks if gamelist.xml is writable before it starts. It won't run unless it is.

Boom! Now it's working. Many thanks for the education on how the cache system works. I think I had a few missteps along the way where I was mounting the media folders as root and not the pi user, running into write issues initially. Once I resolved that, I apparently forgot to re-generate the gamelist.

All good now. Thanks again!

-beatbox32

@mitu thx

Thanks. This helps a lot.

I removed the Windows features for old SMB, rebooted, tried mapping with IP and it worked. Thanks!

@johnnytwolegs It entirely depends on your network setup.

If you NAS is connected to the internet, then I guess it's a matter of configuring the firewall to allow access to the CIFS ports and making sure that file sharing is enabled for the internet interface. If you have a router in-between, you might need to forward the CIFS ports from the network interface to your NAS box.

Again, a configuration I strongly suggest against, since it exposes your NAS to the internet.

@mitu Thanks a lot with that final touch works !!!
Thanks a lot for your help !
Br

That's not going to work, it's how CIFS/SMB works. You can't mount a host, just a share. Sure, the file browser shows you the available shares, but even on Windows (using Map Drive) you can't do that.
Maybe there's another solution with an intermediary program that reads the shares and mounts them separately so you can see them side-by-side, but underneath mount will still only map each shared folder.

@mitu
After reinstalling everything seems to work fine. Will test for a few days now. Thanks for the assistance.

@BuZz I feel like an idiot. Thanks for the help

You can get a set of verified mount options from the docs. Try it - in your /etc/fstab file - and see if work with those options.

@DarkkMatter the retropie system is created from the $HOME/RetroPie/retropiemenu folder - make sure you copied it to the USB along with the roms, splashscreen, BIOS folders. If in doubt, you can re-install the retropiemenu package from the RetroPie-Setup script and it will be re-created in the correct location.

very nice, saving for further reference. Thanks

@Link You can create a folder for the ROMs on the /media/usb0 partition, copy the contents of /home/pi/RetroPie/roms to it, then symlink /home/pi/RetroPie/roms to the folder on the HDD. Make sure you create a back of /home/pi/RetroPie/roms first, just in case.

Or you can bind mount the folder over /home/pie/RetroPie/roms with something like

mount -o bind /media/usb0/<Folder_name> /home/pi/RetroPie/roms

@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