[mrliam]

Thanks labelwhore, that’s handy to know. I am going to be more careful when working with the roms folder from now on, so hopefully it won’t happen again.

[mrliam]

So I have found that in my case it was a directory ownership issue. I must have upset the permissions when adding roms to the folders (I do seem to recall renaming the Snes folder by accident and changing it back).

To solve the issue I ran the Retropie setup script and chose the option to ‘Reset ownership/permissions of /home/pi/Retropie/roms’.

After that I ran the ‘Start USB rom service’ option and all of my missing roms showed up on next reboot.

I am fairly new to Retropie and I am guessing that this must be a somewhat common problem if there is a dedicated script for fixing it, but searching the forums, this was the first post I found on the matter.

Hope the solution is this straightforward for everyone else having a similar issue.

[mrliam]

I too am having the same issue. I am running a fairly clean copy of Retropie v3.4 on a Raspberry Pi 2. So far the only changes I have made are to add a couple of bluetooth devices and a Udev rule for one of them.

I am attempting to load the roms from a 16Gb SanDisk USB formatted to Fat32 with less than 2Gb of data on it using Retropie’s built in copy service.

All the roms copied across for systems named A-S(Scummvm), up until it got the the Snes folder where I had a 0% success rate. The same applied to the ZXSpectrum. The files look fine to me, the folder structure has not been changed from when the copy service created them. At the moment I am at a loss as to why they don’t copy across, but I will continue to investigate when I get the chance.

[Author]

Posts