Moving from Imagegenius old compose to new one and stuck
I recently migrated my Immich Docker setup to use a new media volume path inside the container and moved away from imagegenius. Previously, my media folder was mounted as:
/mnt/tank/cloudvault/immich/photos:/photos
/mnt/tank/cloudvault/immich/photos:/photos
Now I changed it to:
/mnt/tank/cloudvault/immich/data:/data
/mnt/tank/cloudvault/immich/data:/data
and updated my
.env
.env
file accordingly:
IMMICH_MEDIA_LOCATION=/data
IMMICH_MEDIA_LOCATION=/data
I’m running Immich server version v1.137.3.
After restarting, Immich fails with errors like:
ERROR [Api:GlobalExceptionFilter] Unknown error: ENOENT: no such file or directory, access '/photos/thumbs/...
ERROR [Api:GlobalExceptionFilter] Unknown error: ENOENT: no such file or directory, access '/photos/thumbs/...
It seems Immich is still trying to access media files under
/photos
/photos
, but my volume mount is now
/data
/data
.
---
What I’ve tried:
* Verified that
/mnt/tank/cloudvault/immich/data/library
/mnt/tank/cloudvault/immich/data/library
contains all my media files. * Confirmed the volume mount maps host
/mnt/tank/cloudvault/immich/data
/mnt/tank/cloudvault/immich/data
to container
/data
/data
. * Set
IMMICH_MEDIA_LOCATION=/data
IMMICH_MEDIA_LOCATION=/data
in
.env
.env
. * Restarted the entire stack (server, database, Redis).
---
Additional context:
* The database was originally initialized when the media path was
/photos
/photos
. * I understand that Immich stores absolute file paths in the database. * I read that starting from v1.136.0, Immich supports automatic media path migration on startup.
---
Should I do anything at all? Will it automigrate that stuff?