docs: document TrueNAS cross-dataset artwork issue#96
Merged
Conversation
RomM can't link ROMs to their artwork when the library and resources volumes live on different ZFS datasets, even with correct permissions and art downloading fine. Add a troubleshooting entry with the fix. Generated-By: PostHog Code Task-Id: f91b5297-525b-418d-9e5d-ec18e94360ec
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a TrueNAS troubleshooting entry for a case surfaced in the Discord
#truenaschannel: covers/artwork download successfully (visible on disk) but never render in the UI.The root cause is that RomM can't link ROMs to their artwork when the Library and resources volumes live on different ZFS datasets, even with correct permissions on both. This commonly happens when ROMs are on a game/media dataset while resources point at a Docker-specific dataset.
The fix: keep library and resources on the same dataset. Includes working/non-working
docker-composevolume examples, and notes the DB and config file can safely stay on a separate Docker dataset.Created with PostHog Code