#All photos before august first 2025 are blurs and inaccessible

1 messages · Page 1 of 1 (latest)

upbeat pawn
#

I got an unusual issue.
All images before August the first seem to be blurs now and the images themselves are inaccessible.

The images themselves still exist in the uploads folder (as well as the thumbs folder) but they seem inaccessible.

I already tried running migration to migrate things to the latest folder structure and regenerating thumbs.

I am running Immich on Truenas scale using the community docker using the new storage configuration.
Currently running V1.143.0

Does anyone have any suggestions on how to fix this.

When I check the logs of the container I see messages such as this:


2025-09-28 09:19:51.304294+00:00Error: ENOENT: no such file or directory, access 'upload/thumbs/2fae13df-2fef-4772-9141-71965271d713/d6/5d/d65ddd74-7d65-4447-86fe-16754a3e28a5-thumbnail.webp'

2025-09-28 09:19:51.304318+00:00at async access (node:internal/fs/promises:606:10)

2025-09-28 09:19:51.304340+00:00at async sendFile (/usr/src/app/server/dist/utils/file.js:49:9)

2025-09-28 09:19:51.304360+00:00at async AssetMediaController.viewAsset (/usr/src/app/server/dist/controllers/asset-media.controller.js:60:13) ```

 But when I go into the docker shell itself and navigate to the data folder I can clearly see the files being there. (I added a symlink to see if that would resolve it).


Figuring that it may be that the database for the older images points to uploads/bla bla bla while that is in /data/uploads I tried creating a symlink in the pwd to uploads, thumbs etc 

But nothing seems to work. Any advice on how to restore immich to a working state?
image.png
crisp craneBOT
#

:wave: Hey @upbeat pawn,

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

#

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.

mint musk
#

#truenas message

#

This is probably what you need to run to fix it

#

inside immich server shell

upbeat pawn
#

Updated to latest release V1.143.1.
Nothing in release notes, FAQ, Github
I am on local IP (no reverse proxy)
I did try an incognito window.

upbeat pawn
mint musk
#

The issue was probably there before you updated given your description this is a migration issue that happened some TrueNAS versions ago

upbeat pawn
#

Yeah, I just did not notice because all recent images did work

mint musk
#

Yeah new uploads were not affected

#

Glad it fixed it
Have a good day!

#

You can /close the ticket

upbeat pawn
#

You as well. Thanks once again