Failed to read upload/encoded-video/.immich: Error: ENOENT: no such file or directory, open 'upload/
I've rebuilt Immich so many times now; and this error still keeps returning.
Using Portainer + docker compose in an LXC; with an NFS mounted.
I've nuked the /root/postgres folder on host; I've touched; deleted; restored the entire Immich folder; moved it to backup; started fresh; and the error still keeps returning. Latest version v1.131.3
29 Replies
:wave: Hey @mcflyjr,
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. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: 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.
I can see all the files in docker; i can navigate them; I've verified no permissions are messed up on the NFS host; everythings all-squashed to their respective user on the share side; and all the files show the proper owners and permissions
i've tried sync + async NFS; subtree_check + no_subtree_check
:PES2_Shrug:
i noticed it still didn't look right so i went back into the fileshare host; chmoded everything; and still have no dice.
i guess it was 733 vs 755 but still; I'm outta ideas. GUIDs + UIDS look good; perms look good; even opened up further.
the docker lxc obv sees it; it's there.
This happened right after a fresh install; deleting the old volumes + containers; deploying the stack fresh; and clearing out /root/postgres entirely
@mcflyjr docker in an LXC is not supported, so this is outside of a supported immich installation. Weird quirks are known to happen with docker in an LXC
:aPES4_HmmmMath: that would explain all the weird quirks i have with Immich I guess.
I'm getting roughly the exact same problems with docker deployed in a VM + my NFS mounted via fstab
brand new ubuntu 22.10 VM -> install docker + portainer.
redeploy the previously posted compose + .env -> setup immich; and then try to backup again.
half the photos work; half don't.

Does that file exist on disk?
yup
Can you show it please using ls -l as well as exiftool?
and i can open it and it works via my PC client; lemme get you the ls -la

errything i've looked at shows the correct all_squashed 1001
Can you find the file within the immich container as well? And read it? You can use something like md5sum to read the file
hmm... no; i can't i think. 1 second while i reorient myself
hm


but it sees other folders

Not sure, but something with your mounts is def broken or wrong
It’s not an immich issue
It’s strange to me that those show as root owned in immich container. I assume it should show 1001
:pain6: i just dont understand why; i can even create files and folders no problems from within the console
And where do they show up?
I suspect your mount isn’t even being used if I had to guess
huh; not in my NFS share
You have to be very careful with NFS mounts and docker as you can get a race condition between the docker daemon and the NFS client
Yeah so you’re not using NFS at all. It’s just locally stored underneath the NFS mount
:aPES_Sob: i thought i was being eloquent. mounting my NFS share with fstab to the directory; then telling docker to save to that directory
gotta triple check whats going on there then
yea; like... if i touch the folder inside the docker VM; it makes it on the NFS share
but not immichh
Well as long as immich first starts with NFS up it will notice if it’s gone in the future
it made weenie jr hut no problem; im bout to be headed to super weeny hut

if it's mounted as an NFS share on a host..... do i still need to specify it's an NFS share when mounting the docker volume?
UPLOAD_LOCATION=/personalmedia/immich
ive just been using thatt
cause personalmedia was a working NFS share i though
No, you don’t need to tell docker
You might want to get a fresh install working locally first, then move it to NFS. At least then immich will know if files are missing
Like just start it up to create the folders. Then shut down and move the folders to NFS. On next start it will confirm the .immich files are there
I've had it working with my NFS server before; it's just.... always had weird quirks.
used to time out regularly; then I fixed that; and it caused my machine learning to break and no longer be able to read the encoded-video/.immich file
I use NFS and never had any issues but I do delay the docker daemon start by a minute, and I have monitoring checks to make sure it has the mount
so at a loss on this problem; the only one to really throw a fuss on this NFS share; it's been working.
I can't even get it to create folders on a fresh deployment to this NFS share via docker
that's the fstab
:what: i deleted all old volumes; rm -rfed root/postgres; repulled the latest yaml and made sure i have the right versions everywhere.
and now it's deploying the folders on a fresh deployment
I'm gonna go cry into the wall; iunno how tf or wtf. I may have done a dummy and only updated the immich version + ignored a redis or postgres update and borked things silently. hopefully things stay working this go around
my only logical explanation is it created bad volumes with the bad NFS mount; and it wasnt til i removed those that finally worked with NFS. but i got nothing.
errything seems to be working as should be; ML and keyword search; thumb generation
:CatSus: