Lots of "no such file or directory" during immich-go upload

I'm using immich-go to upload a google takeout archive. During the upload, I get this:
server-1 | [Nest] 17 - 04/28/2025, 9:33:57 AM ERROR [Api:AssetMediaService~n73q0fca] Error uploading file Error: ENOENT: no such file or directory, stat 'upload/upload/c747a99d-c3e9-4ca1-9c69-0d54dc9235c5/86/08/86082c7f-a449-4f0a-b6b2-a809893ad716.jpg'
server-1 | Error: ENOENT: no such file or directory, stat 'upload/upload/c747a99d-c3e9-4ca1-9c69-0d54dc9235c5/86/08/86082c7f-a449-4f0a-b6b2-a809893ad716.jpg'
server-1 | at async Object.stat (node:internal/fs/promises:1036:18)
server-1 | at async AssetMediaService.createCopy (/usr/src/app/dist/services/asset-media.service.js:265:26)
server-1 | at async AssetMediaService.replaceAsset (/usr/src/app/dist/services/asset-media.service.js:117:33)
server-1 | at async AssetMediaController.replaceAsset (/usr/src/app/dist/controllers/asset-media.controller.js:51:29)
server-1 | [Nest] 17 - 04/28/2025, 9:33:57 AM ERROR [Api:AssetMediaService~n73q0fca] Error uploading file Error: ENOENT: no such file or directory, stat 'upload/upload/c747a99d-c3e9-4ca1-9c69-0d54dc9235c5/86/08/86082c7f-a449-4f0a-b6b2-a809893ad716.jpg'
server-1 | Error: ENOENT: no such file or directory, stat 'upload/upload/c747a99d-c3e9-4ca1-9c69-0d54dc9235c5/86/08/86082c7f-a449-4f0a-b6b2-a809893ad716.jpg'
server-1 | at async Object.stat (node:internal/fs/promises:1036:18)
server-1 | at async AssetMediaService.createCopy (/usr/src/app/dist/services/asset-media.service.js:265:26)
server-1 | at async AssetMediaService.replaceAsset (/usr/src/app/dist/services/asset-media.service.js:117:33)
server-1 | at async AssetMediaController.replaceAsset (/usr/src/app/dist/controllers/asset-media.controller.js:51:29)
(I get this error several times during uploads) I'm running using docker compose on unraid. I've tried with root and (currently) non-root. Is this caused because the migration job is in a race condition with the extract metadata job (I am using storage templates for date-based hierarchical photo structure). Ultimately, immich-go fails to upload pretty quickly. I am not sure if the above error is related to it:
│2025-04-28 09:33:58 ERR upload error file=takeout-20250427T235736Z-004:Takeout/Google Photos/Photos from 2013/IMG_20130704_161355.jpg error=AssetReplace, │
│PUT, https://photos.domain.com/api/assets/bff8408c-b327-47db-9eea-7aa921352868/original, 500 Internal Server Error │
│Failed to replace asset
│2025-04-28 09:33:58 ERR upload error file=takeout-20250427T235736Z-004:Takeout/Google Photos/Photos from 2013/IMG_20130704_161355.jpg error=AssetReplace, │
│PUT, https://photos.domain.com/api/assets/bff8408c-b327-47db-9eea-7aa921352868/original, 500 Internal Server Error │
│Failed to replace asset
Any pointers on what I am doing wrong? You can view my docker-compose.yml here: https://github.com/rcdailey/nezuko/blob/master/immich/docker-compose.yml And directory permissions:
root@Nezuko: /mnt/fast/docker/immich
$ ll
total 9668
drwxr-xr-x 6 nobody users 123 Apr 28 09:30 .
drwxrwxrwx 19 nobody users 4096 Apr 26 00:22 ..
-rw-r--r-- 1 nobody users 504 Mar 24 12:44 .env
-rw-r--r-- 1 nobody users 34523 Mar 22 11:00 LICENSE
drwx------ 21 nobody users 4096 Apr 28 09:31 db
-rw-r--r-- 1 nobody users 2756 Apr 28 09:38 docker-compose.yml
-rwxr-xr-x 1 nobody users 9842872 Mar 22 11:01 immich-go
drwxr-xr-x 5 nobody users 48 Apr 28 09:30 ml
drwxr-xr-x 2 nobody users 22 Apr 28 09:39 redis
drwxr-xr-x 4 nobody users 35 Mar 24 12:16 upload
root@Nezuko: /mnt/fast/docker/immich
$ ll
total 9668
drwxr-xr-x 6 nobody users 123 Apr 28 09:30 .
drwxrwxrwx 19 nobody users 4096 Apr 26 00:22 ..
-rw-r--r-- 1 nobody users 504 Mar 24 12:44 .env
-rw-r--r-- 1 nobody users 34523 Mar 22 11:00 LICENSE
drwx------ 21 nobody users 4096 Apr 28 09:31 db
-rw-r--r-- 1 nobody users 2756 Apr 28 09:38 docker-compose.yml
-rwxr-xr-x 1 nobody users 9842872 Mar 22 11:01 immich-go
drwxr-xr-x 5 nobody users 48 Apr 28 09:30 ml
drwxr-xr-x 2 nobody users 22 Apr 28 09:39 redis
drwxr-xr-x 4 nobody users 35 Mar 24 12:16 upload
In my case, DOCKER_UID correlates to nobody and DOCKER_GID correlates to users. I am on Unraid. .env:
DB_PASSWORD=immich
DB_USERNAME=immich
DB_DATABASE_NAME=immich
TZ=America/Chicago
DB_PASSWORD=immich
DB_USERNAME=immich
DB_DATABASE_NAME=immich
TZ=America/Chicago
If there's more info I can provide please let me know.
1 Reply
Immich
Immich9h ago
:wave: Hey @voidpointer, 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: This thread has been closed. To re-open, use the button below.

Did you find this page helpful?