#thumbs and encoded video end up in wrong folder

1 messages · Page 1 of 1 (latest)

dusty mirage
#

for some reason the thumbs and encoded videos end up in the default location (upload location) instead of the locations ive specified in the compose and .env.

my docker compose contains these 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 .env file
      - ${UPLOAD_LOCATION}:/data
      - ${THUMB_LOCATION}:/data/thumbs
      - ${ENCODED_VIDEO_LOCATION}:/data/encoded-video
      - /etc/localtime:/etc/localtime:ro```

and my .env contain these:
```# The location where your uploaded files are stored
UPLOAD_LOCATION=/mnt/user/photos

# The location where your database files are stored. Network shares are not supported for the database
DB_DATA_LOCATION=/mnt/cache/appdata/postgresql/data

# The location where thumbnails are stored
THUMB_LOCATION=/mnt/cache/appdata/immich/thumbs

# The location where encoded videos are stored
ENCODED_VIDEO_LOCATION=/mnt/cache/appdata/immich/encoded-video```

and as you can see in the attached screenshot the directories (thumbs and encoded-videos) exist where it should.

and both folders has the .immich file (created by immich itself upon first start of immich after setting up the volumes), as you can see by the attached screenshot.


any suggestions on why this is happening?
tawdry jungleBOT
#

:wave: Hey @dusty mirage,

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. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: read applicable release notes.
  3. :blue_square: reviewed the FAQs for known issues.
  4. :blue_square: reviewed Github for known issues.
  5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: 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.

viral crown
#

@dusty mirage did you also edit the compose?

dusty mirage
#

yes, as i showed a snippet of in the beginning of my post here.

#

but i can post it again if needed

viral crown
#

Right right

#

If your files still end up in the other location it simply means they aren't mounted

dusty mirage
viral crown
#

Since the syntax is correct, I can only assume the folder permissions are wrong

dusty mirage
viral crown
#

I have no idea what the permissions are supposed to be on Unraid 👀

#

Check out #unraid perhaps

dusty mirage
#

thats the default user:group that works with "everything else", but guess ill check over there then

viral crown
#

You recreated the containers since changing this right?

dusty mirage
#

not sure what you mean by recreated, but i shut everything down and started it up again. and the DB was wiped.

#

well, i wiped the DB. did the change, booted up again

#

(though wiping the DB was not because of this but because the password change went bad)

viral crown
#

If it's a docker container you need to recreate it (compose up) and not start/stop

dusty mirage
#

Oh ok, but what happens now when it has started saving stuff there if I do a compose up? Imported everything earlier today so it’s a lot of thumbs and videos being created at the moment

#

Will everything move over automatically or do I need to manually move stuff?