mirror of
https://github.com/rommapp/docs.git
synced 2026-04-20 01:04:29 +08:00
45 lines
2.8 KiB
Markdown
45 lines
2.8 KiB
Markdown
---
|
|
title: Troubleshooting Scanning
|
|
description: Troubleshooting issues relating to library scanning
|
|
---
|
|
|
|
### Scan is skipping all platforms/ends instantly
|
|
|
|
There are a few common reasons why a scan may end instantly/without scanning platforms
|
|
|
|
- Badly mounted library: verify that you mounted your ROMs folder at `/romm/library`
|
|
- Incorrect permissions: the app needs to read the files and folders in your library, check their permissions with `ls -lh`
|
|
- Invalid folder structure: verify that your folder structure matches the one in the [README](https://github.com/rommapp/romm#-folder-structure)
|
|
|
|
### ROMs not found for platform X, check `romm` folder structure
|
|
|
|
This is the same issue as the one above, and can be quickly solved by verifying your folder structure. RomM expects a library with a folder named `roms` in it, for example:
|
|
|
|
- `/server/media/library:/romm/library`
|
|
- `/server/media/games/roms:/romm/library/roms`
|
|
|
|
### Scan does not recognize a platform
|
|
|
|
When scanning the folders mounted in `/library/roms`, the scanner tries to match the folder name with the platform's slug in IGDB. If you notice that the scanner isn't detecting a platform, verify that the folder name matches the slug in the URL of the [platform in IGDB](https://www.igdb.com/platforms). For example, the Nintendo 64DD has the URL <https://www.igdb.com/platforms/64dd>, so the folder should be named `64dd`.
|
|
|
|
### Scan times out after ~4 hours
|
|
|
|
The background scan task times out after 4 hours, which can happen if you have a very large library. The easiest work around is to keep running scans every 4 hours, **without** checking the "Complete re-scan" option. You can also change the timeout via [environment variable](../Getting-Started/Environment-Variables.md) `SCAN_TIMEOUT`.
|
|
|
|
### Scan stops before finishing a platform
|
|
|
|
Check the logs for RomM, you should find a line that looks like `ERROR: [RomM][scan_handler][2025-04-12 11:48:55]` that explains why the scanner stopped. This can often happen due to a corrupted file or a file the [python zipfile library](https://docs.python.org/3/library/zipfile.html) cannot handle, such as old DOS zip files with backslashes instead of forward slashes.
|
|
|
|
### When scanning a very large library with many platforms it is difficult to keep track of which systems have scanned in
|
|
|
|
The easiest method is to check the logs via this command, which will list all the scanned platforms since the RomM container was started `docker logs romm 2>/dev/null|egrep 'scan_handler.*Identified as.*🎮'`
|
|
|
|
Here is an example output:
|
|
|
|
```text
|
|
$ docker logs romm 2>/dev/null|egrep 'scan_handler.*Identified as.*🎮'
|
|
INFO: [RomM][scan_handler][2025-04-12 11:37:40] Identified as PlayStation 🎮
|
|
INFO: [RomM][scan_handler][2025-04-12 14:39:32] Identified as DOS 🎮
|
|
INFO: [RomM][scan_handler][2025-04-13 12:50:42] Identified as WonderSwan 🎮
|
|
```
|