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
Failed to read upload/encoded-video/.immich: Error: ENOENT: no such file or directory, open 'upload/encoded-video/.immich'

microservices worker error: Error: Failed to read "<UPLOAD_LOCATION>/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 - Please see https://immich.app/docs/administration/system-integrity#folder-checks for more information."

at StorageService.verifyReadAccess (/usr/src/app/dist/services/storage.service.js:84:19)

at async /usr/src/app/dist/services/storage.service.js:38:21

at async /usr/src/app/dist/repositories/database.repository.js:231:27

at async /usr/src/app/node_modules/kysely/dist/cjs/kysely.js:413:20

at async DefaultConnectionProvider.provideConnection (/usr/src/app/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:12:20)

at async /usr/src/app/dist/repositories/database.repository.js:228:13

microservices worker exited with code 1

Killing api process
Failed to read upload/encoded-video/.immich: Error: ENOENT: no such file or directory, open 'upload/encoded-video/.immich'

microservices worker error: Error: Failed to read "<UPLOAD_LOCATION>/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 - Please see https://immich.app/docs/administration/system-integrity#folder-checks for more information."

at StorageService.verifyReadAccess (/usr/src/app/dist/services/storage.service.js:84:19)

at async /usr/src/app/dist/services/storage.service.js:38:21

at async /usr/src/app/dist/repositories/database.repository.js:231:27

at async /usr/src/app/node_modules/kysely/dist/cjs/kysely.js:413:20

at async DefaultConnectionProvider.provideConnection (/usr/src/app/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:12:20)

at async /usr/src/app/dist/repositories/database.repository.js:228:13

microservices worker exited with code 1

Killing api process
29 Replies
Immich
Immich3w ago
: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.
mcflyjr
mcflyjrOP3w ago
#
# WARNING: Make sure to use the docker-compose.yml of the current release:
#
# https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml
#
# The compose file on main may not be compatible with the latest release.
#

name: immich

services:
immich-server:
container_name: immich_server
image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
# extends:
# file: hwaccel.transcoding.yml
# service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding
volumes:
# Do not edit the next line. If you want to change the media storage location on your system, edit the value of UPLOAD_LOCATION in the stack.env file
- ${UPLOAD_LOCATION}:/usr/src/app/upload
- /etc/localtime:/etc/localtime:ro
env_file:
- stack.env
ports:
- '2283:2283'
depends_on:
- redis
- database
restart: always
healthcheck:
disable: false


devices:
- /dev/dri:/dev/dri


immich-machine-learning:
container_name: immich_machine_learning
# For hardware acceleration, add one of -[armnn, cuda, openvino] to the image tag.
# Example tag: ${IMMICH_VERSION:-release}-cuda
image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
# extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/ml-hardware-acceleration
# file: hwaccel.ml.yml
# service: cpu # set to one of [armnn, cuda, openvino, openvino-wsl] for accelerated inference - use the `-wsl` version for WSL2 where applicable
volumes:
- model-cache:/cache
env_file:
- stack.env
restart: always
healthcheck:
disable: false

redis:
container_name: immich_redis
image: docker.io/redis:6.2-alpine@sha256:905c4ee67b8e0aa955331960d2aa745781e6bd89afc44a8584bfd13bc890f0ae
healthcheck:
test: redis-cli ping || exit 1
restart: always

database:
container_name: immich_postgres
image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0
environment:
POSTGRES_PASSWORD: ${DB_PASSWORD}
POSTGRES_USER: ${DB_USERNAME}
POSTGRES_DB: ${DB_DATABASE_NAME}
POSTGRES_INITDB_ARGS: '--data-checksums'
volumes:
# Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the stack.env file
- ${DB_DATA_LOCATION}:/var/lib/postgresql/data
healthcheck:
test: >-
pg_isready --dbname="$${POSTGRES_DB}" --username="$${POSTGRES_USER}" || exit 1;
Chksum="$$(psql --dbname="$${POSTGRES_DB}" --username="$${POSTGRES_USER}" --tuples-only --no-align
--command='SELECT COALESCE(SUM(checksum_failures), 0) FROM pg_stat_database')";
echo "checksum failure count is $$Chksum";
[ "$$Chksum" = '0' ] || exit 1
interval: 5m
start_interval: 30s
start_period: 5m
command: >-
postgres
-c shared_preload_libraries=vectors.so
-c 'search_path="$$user", public, vectors'
-c logging_collector=on
-c max_wal_size=2GB
-c shared_buffers=512MB
-c wal_compression=on
restart: always

volumes:
model-cache:
#
# WARNING: Make sure to use the docker-compose.yml of the current release:
#
# https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml
#
# The compose file on main may not be compatible with the latest release.
#

name: immich

services:
immich-server:
container_name: immich_server
image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
# extends:
# file: hwaccel.transcoding.yml
# service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding
volumes:
# Do not edit the next line. If you want to change the media storage location on your system, edit the value of UPLOAD_LOCATION in the stack.env file
- ${UPLOAD_LOCATION}:/usr/src/app/upload
- /etc/localtime:/etc/localtime:ro
env_file:
- stack.env
ports:
- '2283:2283'
depends_on:
- redis
- database
restart: always
healthcheck:
disable: false


devices:
- /dev/dri:/dev/dri


immich-machine-learning:
container_name: immich_machine_learning
# For hardware acceleration, add one of -[armnn, cuda, openvino] to the image tag.
# Example tag: ${IMMICH_VERSION:-release}-cuda
image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
# extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/ml-hardware-acceleration
# file: hwaccel.ml.yml
# service: cpu # set to one of [armnn, cuda, openvino, openvino-wsl] for accelerated inference - use the `-wsl` version for WSL2 where applicable
volumes:
- model-cache:/cache
env_file:
- stack.env
restart: always
healthcheck:
disable: false

redis:
container_name: immich_redis
image: docker.io/redis:6.2-alpine@sha256:905c4ee67b8e0aa955331960d2aa745781e6bd89afc44a8584bfd13bc890f0ae
healthcheck:
test: redis-cli ping || exit 1
restart: always

database:
container_name: immich_postgres
image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0
environment:
POSTGRES_PASSWORD: ${DB_PASSWORD}
POSTGRES_USER: ${DB_USERNAME}
POSTGRES_DB: ${DB_DATABASE_NAME}
POSTGRES_INITDB_ARGS: '--data-checksums'
volumes:
# Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the stack.env file
- ${DB_DATA_LOCATION}:/var/lib/postgresql/data
healthcheck:
test: >-
pg_isready --dbname="$${POSTGRES_DB}" --username="$${POSTGRES_USER}" || exit 1;
Chksum="$$(psql --dbname="$${POSTGRES_DB}" --username="$${POSTGRES_USER}" --tuples-only --no-align
--command='SELECT COALESCE(SUM(checksum_failures), 0) FROM pg_stat_database')";
echo "checksum failure count is $$Chksum";
[ "$$Chksum" = '0' ] || exit 1
interval: 5m
start_interval: 30s
start_period: 5m
command: >-
postgres
-c shared_preload_libraries=vectors.so
-c 'search_path="$$user", public, vectors'
-c logging_collector=on
-c max_wal_size=2GB
-c shared_buffers=512MB
-c wal_compression=on
restart: always

volumes:
model-cache:
UPLOAD_LOCATION=/personalmedia/immich
DB_DATA_LOCATION=/root/postgres
IMMICH_VERSION=release
DB_PASSWORD=YEET
DB_USERNAME=postgres
DB_DATABASE_NAME=immich
UPLOAD_LOCATION=/personalmedia/immich
DB_DATA_LOCATION=/root/postgres
IMMICH_VERSION=release
DB_PASSWORD=YEET
DB_USERNAME=postgres
DB_DATABASE_NAME=immich
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
no_subtree_check,insecure,all_squash,anonuid=1001,anongid=1001,async
no_subtree_check,insecure,all_squash,anonuid=1001,anongid=1001,async
i've tried sync + async NFS; subtree_check + no_subtree_check :PES2_Shrug:
~/postgres # cd /personalmedia/immich
/personalmedia/immich # cd enc*
/personalmedia/immich/encoded-video # ls -la
total 16
drwxr-xr-x 3 1001 1001 4096 Apr 14 12:00 .
drwxrwxr-x 8 1001 1001 4096 Apr 14 10:02 ..
-rw-r--r-- 1 1001 1001 13 Apr 14 10:03 .immich
drwxr-xr-x 105 1001 1001 4096 Apr 14 11:29 8eyeet
/personalmedia/immich/encoded-video # cd ..

/personalmedia/immich/library # ls -la
total 16
drwxr-xr-x 3 1001 1001 4096 Apr 14 12:00 .
drwxrwxr-x 8 1001 1001 4096 Apr 14 10:02 ..
-rw-r--r-- 1 1001 1001 13 Apr 14 10:03 .immich
drwxr-xr-x 14 1001 1001 4096 Apr 14 10:30 admin
/personalmedia/immich/library #
~/postgres # cd /personalmedia/immich
/personalmedia/immich # cd enc*
/personalmedia/immich/encoded-video # ls -la
total 16
drwxr-xr-x 3 1001 1001 4096 Apr 14 12:00 .
drwxrwxr-x 8 1001 1001 4096 Apr 14 10:02 ..
-rw-r--r-- 1 1001 1001 13 Apr 14 10:03 .immich
drwxr-xr-x 105 1001 1001 4096 Apr 14 11:29 8eyeet
/personalmedia/immich/encoded-video # cd ..

/personalmedia/immich/library # ls -la
total 16
drwxr-xr-x 3 1001 1001 4096 Apr 14 12:00 .
drwxrwxr-x 8 1001 1001 4096 Apr 14 10:02 ..
-rw-r--r-- 1 1001 1001 13 Apr 14 10:03 .immich
drwxr-xr-x 14 1001 1001 4096 Apr 14 10:30 admin
/personalmedia/immich/library #
i noticed it still didn't look right so i went back into the fileshare host; chmoded everything; and still have no dice.
/personalmedia/immich/library # ls -la
total 16
drwxrwxr-x 3 1001 1001 4096 Apr 14 12:00 .
drwxrwxr-x 8 1001 1001 4096 Apr 14 10:02 ..
-rwxrwxr-x 1 1001 1001 13 Apr 14 10:03 .immich
drwxrwxr-x 14 1001 1001 4096 Apr 14 10:30 admin
/personalmedia/immich/library # ls -la
total 16
drwxrwxr-x 3 1001 1001 4096 Apr 14 12:00 .
drwxrwxr-x 8 1001 1001 4096 Apr 14 10:02 ..
-rwxrwxr-x 1 1001 1001 13 Apr 14 10:03 .immich
drwxrwxr-x 14 1001 1001 4096 Apr 14 10:30 admin
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
Tempest
Tempest3w ago
@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
mcflyjr
mcflyjrOP3w ago
: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
[Nest] 6 - 04/15/2025, 2:49:52 PM ERROR [Microservices:{"id":"cfa0f558-a7cc-450c-be1c-b498727fdae7","source":"upload"}] Unable to run job handler (metadataExtraction/metadata-extraction): Error: ENOENT: no such file or directory, stat 'upload/upload/e4017003-6db9-4434-905d-45f2953d5430/19/75/1975662d-143c-4be3-a9d9-2d9c7353ce95.jpg'

Error: ENOENT: no such file or directory, stat 'upload/upload/e4017003-6db9-4434-905d-45f2953d5430/19/75/1975662d-143c-4be3-a9d9-2d9c7353ce95.jpg'

at async Object.stat (node:internal/fs/promises:1036:18)

at async Promise.all (index 1)

at async MetadataService.handleMetadataExtraction (/usr/src/app/dist/services/metadata.service.js:129:35)

at async JobService.onJobStart (/usr/src/app/dist/services/job.service.js:156:28)

at async EventRepository.onEvent (/usr/src/app/dist/repositories/event.repository.js:126:13)

at async Worker.processJob (/usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:394:28)

at async Worker.retryIfFailed (/usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:581:24)

[Nest] 6 - 04/15/2025, 2:49:53 PM WARN [Microservices:Error: File not found - /usr/src/app/upload/upload/e4017003-6db9-4434-905d-45f2953d5430/19/75/1975662d-143c-4be3-a9d9-2d9c7353ce95.jpg

at ReadTask._ExifToolTask_parser (/usr/src/app/node_modules/exiftool-vendored/dist/ExifToolTask.js:76:71)

at ReadTask.parser (/usr/src/app/node_modules/exiftool-vendored/dist/ExifToolTask.js:47:167)

at ReadTask._Task_resolve (/usr/src/app/node_modules/batch-cluster/dist/Task.js:146:40)] Error reading exif data (upload/upload/e4017003-6db9-4434-905d-45f2953d5430/19/75/1975662d-143c-4be3-a9d9-2d9c7353ce95.jpg): Error: File not found - /usr/src/app/upload/upload/e4017003-6db9-4434-905d-45f2953d5430/19/75/1975662d-143c-4be3-a9d9-2d9c7353ce95.jpg

[Nest] 6 - 04/15/2025, 2:49:53 PM WARN [Microservices:StorageRepository] File upload/upload/e4017003-6db9-4434-905d-45f2953d5430/46/1f/461f541f-e3dc-43b0-8e6d-5d85f7d67ceb.jpg does not exist.
[Nest] 6 - 04/15/2025, 2:49:52 PM ERROR [Microservices:{"id":"cfa0f558-a7cc-450c-be1c-b498727fdae7","source":"upload"}] Unable to run job handler (metadataExtraction/metadata-extraction): Error: ENOENT: no such file or directory, stat 'upload/upload/e4017003-6db9-4434-905d-45f2953d5430/19/75/1975662d-143c-4be3-a9d9-2d9c7353ce95.jpg'

Error: ENOENT: no such file or directory, stat 'upload/upload/e4017003-6db9-4434-905d-45f2953d5430/19/75/1975662d-143c-4be3-a9d9-2d9c7353ce95.jpg'

at async Object.stat (node:internal/fs/promises:1036:18)

at async Promise.all (index 1)

at async MetadataService.handleMetadataExtraction (/usr/src/app/dist/services/metadata.service.js:129:35)

at async JobService.onJobStart (/usr/src/app/dist/services/job.service.js:156:28)

at async EventRepository.onEvent (/usr/src/app/dist/repositories/event.repository.js:126:13)

at async Worker.processJob (/usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:394:28)

at async Worker.retryIfFailed (/usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:581:24)

[Nest] 6 - 04/15/2025, 2:49:53 PM WARN [Microservices:Error: File not found - /usr/src/app/upload/upload/e4017003-6db9-4434-905d-45f2953d5430/19/75/1975662d-143c-4be3-a9d9-2d9c7353ce95.jpg

at ReadTask._ExifToolTask_parser (/usr/src/app/node_modules/exiftool-vendored/dist/ExifToolTask.js:76:71)

at ReadTask.parser (/usr/src/app/node_modules/exiftool-vendored/dist/ExifToolTask.js:47:167)

at ReadTask._Task_resolve (/usr/src/app/node_modules/batch-cluster/dist/Task.js:146:40)] Error reading exif data (upload/upload/e4017003-6db9-4434-905d-45f2953d5430/19/75/1975662d-143c-4be3-a9d9-2d9c7353ce95.jpg): Error: File not found - /usr/src/app/upload/upload/e4017003-6db9-4434-905d-45f2953d5430/19/75/1975662d-143c-4be3-a9d9-2d9c7353ce95.jpg

[Nest] 6 - 04/15/2025, 2:49:53 PM WARN [Microservices:StorageRepository] File upload/upload/e4017003-6db9-4434-905d-45f2953d5430/46/1f/461f541f-e3dc-43b0-8e6d-5d85f7d67ceb.jpg does not exist.
brand new ubuntu 22.10 VM -> install docker + portainer. redeploy the previously posted compose + .env -> setup immich; and then try to backup again.
mcflyjr
mcflyjrOP3w ago
half the photos work; half don't.
No description
Zeus
Zeus3w ago
Does that file exist on disk?
mcflyjr
mcflyjrOP3w ago
yup
Zeus
Zeus3w ago
Can you show it please using ls -l as well as exiftool?
mcflyjr
mcflyjrOP3w ago
and i can open it and it works via my PC client; lemme get you the ls -la
No description
mcflyjr
mcflyjrOP3w ago
errything i've looked at shows the correct all_squashed 1001
Zeus
Zeus3w ago
Can you find the file within the immich container as well? And read it? You can use something like md5sum to read the file
mcflyjr
mcflyjrOP3w ago
root@dockervm:/personalmedia/immich/upload/e4017003-6db9-4434-905d-45f2953d5430/46/1f# ls -la
total 6656
drwxr-xr-x 2 1001 1001 4096 Apr 15 14:49 .
drwxr-xr-x 11 1001 1001 4096 Apr 15 14:50 ..
-rw-r--r-- 1 1001 1001 6805333 Apr 15 14:49 461f541f-e3dc-43b0-8e6d-5d85f7d67ceb.jpg
root@dockervm:/personalmedia/immich/upload/e4017003-6db9-4434-905d-45f2953d5430/46/1f# ls -la
total 6656
drwxr-xr-x 2 1001 1001 4096 Apr 15 14:49 .
drwxr-xr-x 11 1001 1001 4096 Apr 15 14:50 ..
-rw-r--r-- 1 1001 1001 6805333 Apr 15 14:49 461f541f-e3dc-43b0-8e6d-5d85f7d67ceb.jpg
hmm... no; i can't i think. 1 second while i reorient myself
mcflyjr
mcflyjrOP3w ago
hm
No description
mcflyjr
mcflyjrOP3w ago
No description
mcflyjr
mcflyjrOP3w ago
but it sees other folders
mcflyjr
mcflyjrOP3w ago
No description
Zeus
Zeus3w ago
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
mcflyjr
mcflyjrOP3w ago
:pain6: i just dont understand why; i can even create files and folders no problems from within the console
Zeus
Zeus3w ago
And where do they show up? I suspect your mount isn’t even being used if I had to guess
mcflyjr
mcflyjrOP3w ago
huh; not in my NFS share
Zeus
Zeus3w ago
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
mcflyjr
mcflyjrOP3w ago
: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
Zeus
Zeus3w ago
Well as long as immich first starts with NFS up it will notice if it’s gone in the future
mcflyjr
mcflyjrOP3w ago
it made weenie jr hut no problem; im bout to be headed to super weeny hut
No description
mcflyjr
mcflyjrOP3w ago
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
Zeus
Zeus3w ago
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
mcflyjr
mcflyjrOP3w ago
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
Zeus
Zeus3w ago
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
mcflyjr
mcflyjrOP3w ago
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
IP:/export/personalmedia /personalmedia nfs defaults,auto,rw,timeo=600 0 0
IP:/export/personalmedia /personalmedia nfs defaults,auto,rw,timeo=600 0 0
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:

Did you find this page helpful?