Issue with the installation of Immich and volumes
Hello, actually i'm trying to install immich on a terramaster f2-424 that is currently set up like this:
-1 SSD (Volume1) where install app
-2 HDDs (Volume2) in raid 1
I've created an immich-app in the public folder (Volume 1) and putted in a .env and .yaml file (also postgres,library and model-cache folders), in the .env file i've located my Upload Location to /Volume 2/photos where the photos are located on the HDDs, the problem is the following:
-The software is builded correctly but when i log-in in the web app i can clearly see that the database is on the Volume 1 (with only 900Gb free of the SSD) and not the 7Tb of the HDDs.
What i'm doing wrong? I did the same with Navidrome (with the folder /Volume2/Music) and work without problems.
Thank you for the help
7 Replies
:wave: Hey @Xerlan,
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. :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.(actually the dirctories point Foto because is photo in italian, language that i talk mainly because i'm italian :D)
There's a few issues here
1. These two should be completely separate paths, pointing them to the same folder will break all kinds of things
2. They should point to empty folders. You can't point these to a folder that already has files in it
3. By starting the paths with
./ you're starting them in the current folder where the compose file lives, which is on the SSD. You want to use an absolute path insteadThank you so much for the fast response and useful response!
So in the immich-app folder i should create another Data folder and point it with DB_DATA_LOCATION right?
To clarify the paths a bit: UPLOAD_LOCATION is where all the image/video files go. DB_DATA_LOCATION is where the postgres database goes
The latter is not that big and benefits from being on an SSD
Perfect, i tried just now and now the deployment of immich show up that are free 7Tb of memory, worked!
Thank you so much for the clarification
This thread has been closed. To re-open, use the button below.