Recover from storage template migration error
I am running a standard docker compose setup on debian (everything on my local machine), I just upgraded to the latest version.
I have played around with uploading my photos using immich-go, and I wanted to use the storage template feature.
Something must have gone wrong (maybe my laptop went to sleep in the middle of the template migration) and now I see that in the folder view, some of the data was not converted to the storage template. I also have some photos that seem to be missing in the upload folder (some of them have a valid thumbnail but cannot be downloaded, others don't even have the thumbnail and show "error loading image"). I have never touched the storage folder or db directly, only operating through the web interface or API (through immich-go).
If I look at the logs, after starting the storage template migration job, I see many errors like the one in the attached file.
The error seems related to this bug https://github.com/immich-app/immich/issues/16354 which seems to have been fixed though.
What's the best way to recover here? Both cleaning up any corrupted files, and ensuring nothing was missed (I have all the original photos, so not worried about data loss here)
3 Replies
:wave: Hey @AntonioNYC,
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:Here are my docker-compose and .env files.
Just upgraded to version 2.0.0, still having the same issue.