[Bug] Can't scan any ROMs #1571
Comments
|
Delete your entire container and start over. It only makes the MySQL/mariadb user on first build. In your last screenshot it looks like its info was changed since first built You need to prune any existing or left over containers from romm Also feel free to come to the discord and make a support thread |
|
yes i've nuked the entire thing, containers / volumes / all directories a couple of times but still nothing improving. db container 
romm container 
A scan produces the same results 
Also i just noticed that, although the setup screens had a green tick next to steamgrid for metadata, the dropdown at the top of the scan page does not include it. Does that mean nothing is being used for the search, or..? |
|
I wonder if you just have your folders linked one too deep for the library in your compose media/crispy/NAS_4TB_1/media/games/batocera Try that without the /roms after Sorry on my phone Also you will definitely need an IGDB for auto meta data matching. It's free to get |
Agreed, I think it's this line:
I think the directory you mount needs to include the roms folder, so try:
|
|
ok, changing the path resulted in some action, thank you! 
Have to say that's very counterintuitive and should probably be more accurately explained in the readme. The way it's expressed at the moment suggests my original path would work fine, but obviously not. My next issue is exclusions and the config.yml. As you can see from the screenshot above, I have a load of consoles that I'm not using (for example, 'Arcadia', which has a single 'rom' that is actually an '_info.txt') 
..and also a console called 'Stfolder', which is just a syncthing folder 
I've tried to add as many exclusions to my config.yml as possible, both through the UI and directly editing it, but it seems hard to get some things to 'stick and, despite doing a complete scan, all the unwanted files and folders are still appearing in the UI This is my config.yml. Can you suggest where I'm going wrong? This is the UI exclusions 
|
|
I'm glad you got your roms are now scanning. It was definitely how the folder was mounted I haven't really messed with the exclusions myself I'll ask if another tech support from the discord can check this for you. |
thank you! |
|
The config.yml can be powerful but also confusing. First of all, do you still want the the console to appear? If the answer is no then you will add it here:
You would have to manually remove the platform from RomM but when you next scan it will not be seen. The next exclusion rules are single files FOUND within a platform, so for example if you had a file named manual.pdf
You would add the .pdf extension in there, so if I scanned and found files within SNES platform, and that platform had gamename.pdf, it will not include those in the scans. The final exclusion rule is the multi-file which is applied to subfolders.
Using my example again ,if I have a subfolder in there named manuals, I would add manuals to the exclude matched folder names location. Hope this clear things up for you. The UI and config.yml are the exact same thing, they talk directly to each other. EDIT: Cursed github formatting. |
gantoine
added
bug
RomM version
3.7.3
Describe the bug
Unable to find or match any roms
Expected behavior
roms to be matched.
I used romm when @zurdi15 very first announced it and it used to work great. Then some changes were made and my instance broke and I never bothered fixing it and haven't looked at it for over a year. I wanted to start using it again and I see a lot of stuff has been updated, so I've just tried to get it running again and I'm having a hell of time trying to get it to see any of my roms.
Firstly, this is my compose:
My rom library is used by batocera and follows their folder structure. I followed the batocera example and made a config.yaml and that lives at -
/home/crispy/docker/romm/config/config:/romm/configas per my compose.Not sure if I've messed something up with that config, but you can take a look here: https://pastebin.com/UjUjQ2j4
Sidenote: I had my previous IGDB credentials in the compose and thought maybe they had expired and that was causing any lookups to fail, but visiting the twitch dev applications page it seems you can't save or create anything in your applications. The 'Save' button is greyed out:
Seems to be an ongoing issue, actually - twitchdev/issues#634
.. so I signed up to steamgrid and used their api key instead (i have no idea what steamgrid is or if it's any good, but it's in the romm docs, so..)
Romm starts up as normal, but when trying a scan i get this for every single possible console:
Checking the container logs i see this:
Checking the mariadb container i can also see this, which is probably less than ideal I guess:
So i'm kind of stuck now. I see the message about verifying that the folder structure is correct, and i've checked it repeatedly.
/media/crispy/NAS_4TB_1/media/games/batocera/romsdoes indeed lead to my roms:Any ideas? I'd love to make romm work again, but this is verging on making me give up.
The text was updated successfully, but these errors were encountered: