Upload location and Database location
My Server is workign well! but it says i only have 200 some odd gigs available. I gave it an upload location of 1TB tho! So why would it show that i only have the Bootdrive rest of storage available?
116 Replies
:wave: Hey @SorinMarkauv,
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. :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.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:may have found answer https://immich.app/docs/install/portainer Change UPLOAD_LOCATION to a folder where media (uploaded and generated) will be stored.
acctuallly the plot thickens. now that ive recreated my immich stack with the new information it still says 232gb and im not even referencing the drive it would be storing things too.
is the "Raid Immich" the 1TB one?
yup!
love the profile pic
I'm not 100% sure, but I believe the storage indicator is only for the drive where the container resides on
(which is kind of silly :3 )
so i have to deploy the container on a different drive? pretty sure i did i didn't tell it to live anywhere else besides the raid drive now
No no
You just have to ignore that storage indicator for now 😛
It'll get better, I promise!
DB_DATA_LOCATION ./srv/dev-disk-by-uuid-28d659d6-e481-487c-81db-9252e75899ec/Raid Immich
UPLOAD_LOCATION ./srv/dev-disk-by-uuid-418f5731-dd9e-429e-b33c-d53ce15157ef/ImmichBackup
its fake nws?
i won't fill up my boot contianer drive
No it won't
If you see the storage progressing, that's just other stuff on the boot drive, not Immich
looks like it still has some old files on there from when i was testing
when i made the old stack
cause i jsut remade
looks like i can jsut delete that folder.
I don't know which ones you're talking about so I can't say yes or no to that 👀
looks like it just added more data
it being what though
it even grew on OMV
the icon on the bottom
and my boot drive increased in size
right after uploading a few test pics
Well that doesn't sound right then
hang on
where would it be adding the files ? 0,o
docker inspect immich_server | grep UPLOAD_LOCATION
That should return your immich raid thingroot@JastersLegacy:/# docker inspect immich_server | grep UPLOAD_LOCATION
"UPLOAD_LOCATION=./srv/dev-disk-by-uuid-418f5731-dd9e-429e-b33c-d53ce15157ef/ImmichBackup",
root@JastersLegacy:/#
I would like to note your boot drive is 210 GiB and the immich drives (in your screenshot) is 232 GiB
So how does that work
210.45 left
232.2-9.9 i guess
That would be 220
not 210
😛
right
somethings not seeing something
clearly ive added something to the bootdrive though
cuase i uploaded those photos and got .3 more gb
and lost it in my nvme
This all sounds to me like some kind of storage configuration on OMV's end 🙃
im using portainer as a container manager
that won't matter really
Portainer is just a frontend to docker
ahhhh look at that
the volumes are pointing to docker/volumes!!!
not the share drives i told the stack!
mmm I don't think so
portainer data volume = a small volume that contains the compose/env files
immich_model-cache might be increasing in size though
That's the machine learning model
It should be about 4 to 8 GB in size
how do you inspect data size
im CD to the location
i got a clip and facial-recognition
du -hcd1 .581M ./clip
183M ./facial-recognition
764M .
764M total
looks like its reserved the rest of it
so it shouldn't be increasing
might be downloading still 🙂
so you think that my data is being stored in my raid drive still
cause of upload location (the backup spot) and the database location (my raid) being not the boot drive
All I'm saying is that your immich_server has the correct upload path given to it by you, so it will store it there
is UPload the main data storage
Also you uploaded a couple of pics or a bunch?
or is database
just 5 or so
some raw file pictures so it was about a .3 gig
Because 9.1 to 9.9 that's 800 MiB
Seems like a lot for a couple of pics
i sitll have 2.04 mib on my raid tho
but not a lot if it was downloading the ML model
aint nothing in ther
lsblk and df -hT please 😛thats a cool command!
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 931.5G 0 disk
└─md0 9:0 0 931.4G 0 raid1 /srv/dev-disk-by-uuid-28d659d6-e481-487c-81db-9252e75899ec
sdb 8:16 0 298.1G 0 disk
└─sdb1 8:17 0 298.1G 0 part /srv/dev-disk-by-uuid-418f5731-dd9e-429e-b33c-d53ce15157ef
sdc 8:32 0 931.5G 0 disk
└─md0 9:0 0 931.4G 0 raid1 /srv/dev-disk-by-uuid-28d659d6-e481-487c-81db-9252e75899ec
sdd 8:48 0 5.5T 0 disk
├─sdd1 8:49 0 16M 0 part
└─sdd2 8:50 0 5.5T 0 part /srv/dev-disk-by-uuid-82FC4BC0FC4BAD6B
sr0 11:0 1 6.1G 0 rom /srv/dev-disk-by-uuid-4273aeed00000000
nvme0n1 259:0 0 238.5G 0 disk
├─nvme0n1p1 259:1 0 512M 0 part /boot/efi
├─nvme0n1p2 259:2 0 237G 0 part /
└─nvme0n1p3 259:3 0 977M 0 part [SWAP]
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 16G 0 16G 0% /dev
tmpfs tmpfs 3.2G 3.3M 3.2G 1% /run
/dev/nvme0n1p2 ext4 233G 10G 211G 5% /
tmpfs tmpfs 16G 0 16G 0% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 16G 20K 16G 1% /tmp
/dev/nvme0n1p1 vfat 511M 148K 511M 1% /boot/efi
/dev/sdb1 ext4 293G 2.2M 293G 1% /srv/dev-disk-by-uuid-418f5731-dd9e-429e-b33c-d53ce15157ef
/dev/md0 ext4 916G 2.1M 916G 1% /srv/dev-disk-by-uuid-28d659d6-e481-487c-81db-9252e75899ec
/dev/sdd2 fuseblk 5.5T 2.4T 3.2T 43% /srv/dev-disk-by-uuid-82FC4BC0FC4BAD6B
/dev/sr0 udf 6.2G 6.2G 0 100% /srv/dev-disk-by-uuid-4273aeed00000000
overlay overlay 233G 10G 211G 5% /var/lib/docker/overlay2/952bb925f89bff1ca13bd76fe61081503a59214e7efb6872691365d9faef0b0b/merged
overlay overlay 233G 10G 211G 5% /var/lib/docker/overlay2/db53f2425a87754369d5526842a9adc0844c60ab873c34c3ddedffdc55ef158d/merged
overlay overlay 233G 10G 211G 5% /var/lib/docker/overlay2/ad13b967b157ed6f957b06779be79bd9821c013a9f717297bd7a047a43e9ad27/merged
overlay overlay 233G 10G 211G 5% /var/lib/docker/overlay2/4fa681f07fe4cb43c56b4bc6c77ebd83d800840f4ca421fff631890215671ebc/merged
overlay overlay 233G 10G 211G 5% /var/lib/docker/overlay2/2153882b0b0ec04962606b3826064c4223a36d3bec65d434bdf7e94a1e1e4c7a/merged
overlay overlay 233G 10G 211G 5% /var/lib/docker/overlay2/af816b921310e1c5d275c30813ae62301243104eee68d49696565bffe08f012d/merged
just uploaded a bunch more
its all getting stored on my boot for sure!
I used this stack creation guide https://immich.app/docs/install/portainer
i din't see this docker compose one https://immich.app/docs/install/docker-compose i have not done that
so idon't really know where my directories were made
@Mraedis still alive? no rush just making sure you are good
💀 ded bro
Just getting coffee
sr0 is a disk
like in a disk drive
I know how cd-roms work buckaroo
solid!
Alright so what I think is happening is, portainer/docker/whatever has no access to your actual drives
so it just makes up a new directory for the disk you're trying to mount
i know plex has access
but i added that volume
plex IS storing where it should?
yes!
look at that big boy in there
How'd you do that
script kitty youtubing
but it mostly comes down to portainer volumes i think
cause portainer is a container
Did you add /dev/sdd2 to plex or /dev/disk-by-uuid/...bla
it doesn't have access outside i bet
script kiddie btw
as in kid
as in child
not cat
ohh really?
lol the more you know
Yes but it should have your docker socket mounted
i added a volume here
which grants it access to the docker workings and stuff
and it grabbed this
then i mapped a bunch of stuff
Show me this for immich
/data/compose/10/srv/dev-disk-by-uuid-418f5731-dd9e-429e-b33c-d53ce15157ef/ImmichBackup
looks like its in data/compose
instead of just going to srv
maybe i dump the top stuff there and it goes to the right place?
If you can change the volume there
Change it to where it should be
Then be sure to copy all files from that data/compose thing
and use
cp -a when copying
Either that or wipe the database
because otherwise it will complain about missing filesi can change it
let me see what is in there
I wonder if the portainer compose won't bork it
looks like the backup is being held there too
but i don't see where i can change the backup
it's always in
UPLOAD_LOCATION/backupsroot@JastersLegacy:/data/compose/10/srv/dev-disk-by-uuid-418f5731-dd9e-429e-b33c-d53ce15157ef/ImmichBackup# ls
backups encoded-video library profile thumbs upload
root@JastersLegacy:/data/compose/10/srv/dev-disk-by-uuid-418f5731-dd9e-429e-b33c-d53ce15157ef/ImmichBackup#
If you want to change that you need to mount a different volume to that folder
you think i need to copy some stuff
i don't care about the data as long as it is not being held there
the uploads were all junk test
Thats why I said you need to either copy or wipe the DB
once it's initialized there are a bunch of hidden files that are checked on startup to make sure your library is OK
if you wipe the DB it will remake those on startup
i see 2 dev-disks here in the srv under 10
root@JastersLegacy:/data/compose/10/srv# ls
dev-disk-by-uuid-28d659d6-e481-487c-81db-9252e75899ec dev-disk-by-uuid-418f5731-dd9e-429e-b33c-d53ce15157ef
ok can confirm
they look like recreations of my normal uuids
but these are at the root lvl basically
im sure i said that wrong
looks like /data/compose/10/ is the "root" folder for those
think i should dump that?
that would have to recreate a lot of the whole container then
i noticed i have some others in there
i wonder which is the first stack i made
they are all bad immichs
oh dear 👀
ok deleted and deploying the container
/data/compose/xyz is just portainers way of storing container data
you can manage it like that but beware that portainer might disagree
we will see!
i was able to keep plex compose files in the plex volume i made which is nice
but because im doing this via stack i feel like verything is all wrong
yah Unhealthy
i think im gonna delete and restart with the normal container method?
👍
i wonder now if all that compose data is being stored in the raid
From your mountpoints and disks, no
it's just straight into your root partition
bin dev home initrd.img.old lost+found opt root srv usr vmlinuz.old
boot etc ImmichDatabase lib media PortainerCompose run sys var
data export initrd.img lib64 mnt proc sbin tmp vmlinuz
so taht immich database is junk?
dunno is it?
just check inside
i deleted the stack so nothing should exist
blank
is the . in front of the / in UPLOAD_LOCATION=./library important?
is that what is ruining my location of saved info?
ohh thats it isn't it
i was using a relative location 😦
👀
Yes that's what that . means
well thats the answer!
I didn't spot it at the start, sorr
y
LEARNING!!!!
its all good
No man you've been real good about this 🙂
i wan't to have this store its data in the volume i just made for it
instead of where it wants to i think
maybe i just let it be
is that somehting i can/should mess with?
id rather everything not live on the root folder
i feel like that is bad practice
You can put the DB anywhere you want, as long as it's not over the network
is that the upload location or the DB location?
where everything is gonna be stored?
So we have 2 main locations
upload = anything pictures
db_data = postgres database
cause this: is a bit confusing
Change DB_DATA_LOCATION to a folder where the database will be saved to disk.
Change UPLOAD_LOCATION to a folder where media (uploaded and generated) will be stored.
the database should ideally be on your SSD, because it will be only 5GB in size or so
even with huge libraries
cool
I have just about the same setup, without hte OMV part
DB on my root partition, seperate /data/ disk/partition for the pictures
cool
well here we go round 4!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
@Mraedis thank you sir!
!close
it's /close but ok
This thread has been closed. To re-open, use the button below.