Asset Offline in Trash from External Library that has Multiple Mounts
I mounted two different folders into the same volume in my docker.compose with the goal of grouping them together in the same Immich folder:
This feels like Deja Vu because I'm pretty sure this was working, all the assets were visible under /Folder/ view on the webUI, and the statistics showed 100k+ photos.
However a few days ago the external drive these folders were on kept ejecting randomly and docker couldn't mount them (unrelated power issue, just had to swap whch usb ports the drives were plugged into around)
Now, Immich only seems to be able to see Assets that exist in the LAST mount location in docker.compose, for example of the 3 folders mounted into
grouped -- both folders on A: show assets as offline, but assets from B: are working fine.
A rescan of All libraries, or individual ones, doesn’t fix/mark them as online. All the assets that are offline are stuck in Trash, and the Folder view doesn't show any of the subfolders from A: , but does show the folders in B
since I somehow managed to used a multi-folder volume before .. any ideas what might have changed or messed up with my docker to cause this all of a sudden?
https://i.vgy.me/bEtmJw.png https://i.vgy.me/iRyv04.png https://i.vgy.me/gwVz8N.png
5 Replies
:wave: Hey @shadowrs,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:I mounted two different folders into the same volume in my docker.compose with the goal of grouping them together in the same Immich folder:You can't do that They need to be independent mounts
Haha perfect ok good 👍🏼 now I know it was just luck it worked before lol
Thank you! If Immich can see each docker mount and can tell there’s conflicts like I did, a warning that this won’t work might be a good addition for users in the future
This thread has been closed. To re-open, use the button below.
Not really. For immich it's just a path. Not sure why it worked in the first place, but docker does not prevent this from happening. Mounts usually "hide" content below them.