#Immutable chunks error
1 messages · Page 1 of 1 (latest)
:wave: Hey @eternal nexus,
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
.
References
- Container Logs:
docker compose logsdocs - Container Status:
docker ps -adocs - 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...
- :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
- :ballot_box_with_check: read applicable release notes.
- :ballot_box_with_check: reviewed the FAQs for known issues.
- :ballot_box_with_check: reviewed Github for known issues.
- :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
- :ballot_box_with_check: uploaded the relevant information (see below).
- :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 -landdf -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:
This is most likely a caching issue
Try in an incognito tab and then if that doesn't work, then restarting your reverse proxy
Incognito it gives a 502 as well. Have restarted the proxy too. I have noticed the main immich app container constantly restarts when doing docker ps. Would you like the logs?
Starting microservices worker
[Nest] 6 - 08/04/2025, 12:21:27 PM LOG [Microservices:EventRepository] Initialized websocket server
[Nest] 6 - 08/04/2025, 12:21:27 PM LOG [Microservices:DatabaseRepository] targetLists=1, current=1 for clip_index of 8 rows
[Nest] 6 - 08/04/2025, 12:21:27 PM LOG [Microservices:DatabaseRepository] targetLists=1, current=1 for face_index of 5 rows
[Nest] 6 - 08/04/2025, 12:21:27 PM LOG [Microservices:StorageService] Verifying system mount folder checks, current state: {"mountChecks":{"thumbs":true,"upload":true,"backups":true,"library":true,"profile":true,"encoded-video":true}}
[Nest] 6 - 08/04/2025, 12:21:27 PM ERROR [Microservices:StorageService] Failed to read (/data/encoded-video/.immich): Error: ENOENT: no such file or directory, open '/data/encoded-video/.immich'
microservices worker error: Error: Failed to read: "<UPLOAD_LOCATION>/encoded-video/.immich (/data/encoded-video/.immich) - Please see https://immich.app/docs/administration/system-integrity#folder-checks for more information.", stack: Error: Failed to read: "<UPLOAD_LOCATION>/encoded-video/.immich (/data/encoded-video/.immich) - Please see https://immich.app/docs/administration/system-integrity#folder-checks for more information."
at StorageService.verifyReadAccess (/usr/src/app/server/dist/services/storage.service.js:127:19)
at async /usr/src/app/server/dist/services/storage.service.js:56:21
at async /usr/src/app/server/dist/repositories/database.repository.js:379:27
at async /usr/src/app/server/node_modules/kysely/dist/cjs/kysely.js:535:20
at async DefaultConnectionProvider.provideConnection (/usr/src/app/server/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:12:20)
at async /usr/src/app/server/dist/repositories/database.repository.js:376:13
microservices worker exited with code 1
Killing api process
Initializing Immich v1.137.3
Detected CPU Cores: 2
Starting api worker
Starting microservices worker
docker-admin@docker-template:~$
I'd also like to mention this happens on a fresh instance as well with everything set to default
This means that either A) the permissions aren't correct at the upload location or B) The upload location is no longer where it's expected to be.
Basically immich is trying to read a file from the upload folder and it can't find it, so it's failing to start
Even if i set this on a new install this happens
it worked fine previously
when it worked the upload location was the share and would populate the default folders
I'm just saying that's what that error means. Immich writes a hidden . file to each of the top level directories. When it boots and can't find that file, it will fail to start. How it became missing, or is no longer readable I am unsure of.
A new isntall means wiping your postgres database, is that what you mean?
a fresh VM more or less from scratch
if I leave everything default and don't change anything, it happens
thats why at first i thought it'd be a network share issue, then i tried on a fresh VM and leaving everything default, it stil happens
I would suggest (Not using a fresh vm) and just creating a new folder on the vm in your home directory (immich-test) or something. Put the default docker compose and env in there and attempt to just start it. Post the logs after. It would be a failed to write error if it won't boot on first run, it will fail to write the hidden files
let me try that
If that actually fails to work then it's some larger issue with permissions
So yes. Then it's an issue of, you had an existing installation, the mount became unavailable, and is still unavailable from immich's perspective so it's failing to start
if you try a sudo mount -a and try and restart immich what happens?
I've done mount -a and even write to the file location
can*
but it still hangs to start
Something with permissions is happening then. Can you see the .immich file in the encode-video folder from the host that will run immich?
ls -a /media/photos/upload/encoded-video
the mount just has the text file i wrote
Need to figure out what happened to the files then I guess, that's the real mystery
Hopefully you have a backup you can restore from if the files can't be located for some reason
They just disappear?
the mount is persistnt per the fstab so the mount doesnt disappear
so all data is still there, its just when i restore or rebuilf the vm with this share it freaks out
Is it possible that the share is unavailable until some time in the future? By the time it is available immich has already tried to start?
nope, always present
gort it up and going now though, recreated the folders and touched a .immich file in all dirs and works now
And you can shut it down and restart the VM successfully?