Immich database not recognized after update — container starts slowly, photos missing
Hi everyone,
I ran into a problem with the database after updating Immich from version 1.130.x to 1.132.x.
I'm currently on version 1.133.1, but the issue persists.
The issue:
The immich_postgres container takes a very long time to start. Once it finally starts, Immich does not detect any existing data in the database and prompts me to upload photos as if it were a clean install.
I'm using the image:
docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0
Has anyone encountered a similar issue? Maybe there's a solution mentioned in other threads?
Thanks in advance.
11 Replies
:wave: Hey @hankhill0428,
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. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: 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.@hankhill0428 logs please, and you can't upgrade to a new version and then roll back to the old postgres image
Did you read the breaking changes at all?
Hey. Here are the logs from immich_postgres. Unfortunately, they are not very informative, which is why I didn’t post them earlier:
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-05-25 19:48:32.792 UTC [1] LOG: redirecting log output to logging collector process
2025-05-25 19:48:32.792 UTC [1] HINT: Future log output will appear in directory "log".
As for rolling back to an older Postgres image — I didn’t do that intentionally.
I updated all Immich containers via Portainer using Recreate -> Re-pull image.
Everything worked fine right after the update, but the next morning I noticed the database was stuck in the “starting” status.
After restarting the container, it became “healthy”, but the data was gone.
But the breaking changes....?
Which is arguably the most important part
Also, arw you using portainer business?
No, I didn’t read it — thanks for pointing it out.
Yes, I see that the breaking changes happened in version 1.133.0, but my database became inaccessible already on version 1.132.x.
In any case, I’ll try to follow the migration guide now. Thanks!
My Portainer is CE.
What is your env like? Specially db data loc
immich_postgres:
- DB image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0
- DB data location: relative path
./postgres mounted as ${DB_DATA_LOCATION}:/var/lib/postgresql/data
→ On the host, this resolves to /volume1/docker/immich/postgres (compose is in /volume1/docker/immich)
- DB_VECTOR_EXTENSION is not set
- IMMICH_VERSION is set to releaseOK so could you check your portainer server's /data folder, specifically the compose folder for immich stack
There might be a v1 v2... Folder in there
Can you post the full env and compose please?
@Mraedis @bo0tzz
I did a grep search on the Postgres databases and ended up finding only databases no larger than 120 megabytes (my library is significantly bigger). Therefore, I had to start a new scan (I store the photo files independently from Immich). Thank you very much for your time and your help.
To be clear the library is not stored in postgres, so any database dump will of course be much smaller than all the files you have in Immich