#Mount of ntfs path into /data appears in docker but files do not get written to the folder

1 messages · Page 1 of 1 (latest)

hexed quest
#

I have installed on windows server 2022 and have a 5TB drive that I want to use for immich. I followed the instructions for installation and my K: drive contains folder immich which, in turn, contains the .env and compose.yml files. I have defined the UPLOAD_LOCATION as /mnt/k/immich/library and it shows as being mounted to the /data folder in the server container. Files that are uploaded show in the container as going to /data/library/<userid>/<year>/<month>/<day>/file_that_was_uploaded however the files are NOT in the mounted folder on the K: drive.

marble pastureBOT
#

:wave: Hey @hexed quest,

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. :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.

hexed quest
#

I can only post the info as screen captures since I'm remote to the server and only access it with screen sharing.

crystal gyro
#

This means your k drive was never mounted

marble pastureBOT
hexed quest
crystal gyro
#

Sure, it might think that but it's obviously not true

#

If the files upload succesfully and are downloadable/interactable then they exist solely in the docker image

#

The easiest way to verify this is to create a file in your K: drive and see if it's visible in the container

hexed quest
crystal gyro
#

Restarting the container might properly mount it this time, but I'm thinking Windows shenanigans and I can't help much with that

#

It might have issues with the /mnt/k over K:\ for instance

hexed quest
#

Well it's using WSL2 so the /mnt/k is what is expected by Debian which is what docker is using. I've been playing with this for 14 hours now, 10 of which were wasted trying to get postgres working ( i missed the note about it requiring an ext4 volume)

#

If I didn't have 40+ TB of files on this server (storage spaces) I'd have converted to linux ages ago 🙂

#

I'll check back after I get some sleep

crystal gyro
severe trail
#

do docker inspect immich_server to verify if the path was actually mounted

#

wait, are you using docker desktop?
you should be using docker for Linux IN wsl to run on Windows

hexed quest
#

Interestingly it wanted the path to be provided using windows/dos format (including drive letter). Changing over to that allowed everything to work as designed. Something that you may want to add to the notes about installations on Windows Server.