#Upload location and Database location

1 messages Β· Page 1 of 1 (latest)

boreal hearth
#

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?

dusk bearBOT
#

:wave: Hey @boreal hearth,

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.

dusk bearBOT
boreal hearth
#

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.

light rune
#

is the "Raid Immich" the 1TB one?

boreal hearth
#

yup!

#

love the profile pic

light rune
#

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 )

boreal hearth
#

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

light rune
#

No no

#

You just have to ignore that storage indicator for now πŸ˜›

#

It'll get better, I promise!

boreal hearth
#

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

light rune
#

No it won't

#

If you see the storage progressing, that's just other stuff on the boot drive, not Immich

boreal hearth
#

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.

light rune
#

I don't know which ones you're talking about so I can't say yes or no to that πŸ‘€

boreal hearth
#

looks like it just added more data

light rune
#

it being what though

boreal hearth
#

it even grew on OMV

#

the icon on the bottom

#

and my boot drive increased in size

#

right after uploading a few test pics

light rune
#

Well that doesn't sound right then

#

hang on

boreal hearth
#

where would it be adding the files ? 0,o

light rune
#

docker inspect immich_server | grep UPLOAD_LOCATION

#

That should return your immich raid thing

boreal hearth
#

root@JastersLegacy:/# docker inspect immich_server | grep UPLOAD_LOCATION
"UPLOAD_LOCATION=./srv/dev-disk-by-uuid-418f5731-dd9e-429e-b33c-d53ce15157ef/ImmichBackup",
root@JastersLegacy:/#

light rune
#

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

boreal hearth
#

210.45 left

#

232.2-9.9 i guess

light rune
#

That would be 220

#

not 210

#

πŸ˜›

boreal hearth
#

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

light rune
#

This all sounds to me like some kind of storage configuration on OMV's end πŸ™ƒ

boreal hearth
#

im using portainer as a container manager

light rune
#

that won't matter really

#

Portainer is just a frontend to docker

boreal hearth
#

ahhhh look at that

#

the volumes are pointing to docker/volumes!!!

#

not the share drives i told the stack!

light rune
#

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

boreal hearth
#

how do you inspect data size

#

im CD to the location

#

i got a clip and facial-recognition

light rune
#

du -hcd1 .

boreal hearth
#

581M ./clip
183M ./facial-recognition
764M .
764M total

#

looks like its reserved the rest of it

#

so it shouldn't be increasing

light rune
#

might be downloading still πŸ™‚

boreal hearth
#

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

light rune
#

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

boreal hearth
#

is UPload the main data storage

light rune
#

Also you uploaded a couple of pics or a bunch?

boreal hearth
#

or is database

#

just 5 or so

#

some raw file pictures so it was about a .3 gig

light rune
#

Because 9.1 to 9.9 that's 800 MiB

#

Seems like a lot for a couple of pics

boreal hearth
#

i sitll have 2.04 mib on my raid tho

light rune
#

but not a lot if it was downloading the ML model

boreal hearth
#

aint nothing in ther

light rune
#

lsblk and df -hT please πŸ˜›

boreal hearth
#

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!

#

so idon't really know where my directories were made

#

@light rune still alive? no rush just making sure you are good

light rune
#

πŸ’€ ded bro

#

Just getting coffee

boreal hearth
#

sr0 is a disk

#

like in a disk drive

light rune
#

I know how cd-roms work buckaroo

boreal hearth
#

solid!

light rune
#

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

boreal hearth
#

i know plex has access

#

but i added that volume

light rune
#

plex IS storing where it should?

boreal hearth
#

yes!

#

look at that big boy in there

light rune
#

How'd you do that

boreal hearth
#

script kitty youtubing

#

but it mostly comes down to portainer volumes i think

#

cause portainer is a container

light rune
#

Did you add /dev/sdd2 to plex or /dev/disk-by-uuid/...bla

boreal hearth
#

it doesn't have access outside i bet

light rune
#

as in kid

#

as in child

#

not cat

boreal hearth
#

ohh really?

#

lol the more you know

light rune
boreal hearth
#

i added a volume here

light rune
#

which grants it access to the docker workings and stuff

boreal hearth
#

and it grabbed this

#

then i mapped a bunch of stuff

light rune
boreal hearth
#

/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?

light rune
#

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 files

boreal hearth
#

i can change it

#

let me see what is in there

light rune
#

I wonder if the portainer compose won't bork it

boreal hearth
#

looks like the backup is being held there too

#

but i don't see where i can change the backup

light rune
#

it's always in UPLOAD_LOCATION/backups

boreal hearth
#

root@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#

light rune
#

If you want to change that you need to mount a different volume to that folder

boreal hearth
#

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

light rune
#

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

boreal hearth
#

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

light rune
#

looks like /data/compose/10/ is the "root" folder for those

boreal hearth
#

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

light rune
#

oh dear πŸ‘€

boreal hearth
#

ok deleted and deploying the container

light rune
#

/data/compose/xyz is just portainers way of storing container data

#

you can manage it like that but beware that portainer might disagree

boreal hearth
#

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?

light rune
#

πŸ‘

boreal hearth
#

i wonder now if all that compose data is being stored in the raid

light rune
#

From your mountpoints and disks, no

#

it's just straight into your root partition

boreal hearth
#

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?

light rune
#

dunno is it?

#

just check inside

boreal hearth
#

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 😦

light rune
#

πŸ‘€

#

Yes that's what that . means

boreal hearth
#

well thats the answer!

light rune
#

I didn't spot it at the start, sorr

#

y

boreal hearth
#

LEARNING!!!!

#

its all good

light rune
#

No man you've been real good about this πŸ™‚

boreal hearth
#

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

light rune
#

You can put the DB anywhere you want, as long as it's not over the network

boreal hearth
#

is that the upload location or the DB location?

#

where everything is gonna be stored?

light rune
#

So we have 2 main locations

#

upload = anything pictures

#

db_data = postgres database

boreal hearth
#

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.

light rune
#

the database should ideally be on your SSD, because it will be only 5GB in size or so

#

even with huge libraries

boreal hearth
#

cool

light rune
#

I have just about the same setup, without hte OMV part

#

DB on my root partition, seperate /data/ disk/partition for the pictures

boreal hearth
#

cool

#

well here we go round 4!!!

#

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

#

@light rune thank you sir!

#

!close

light rune
#

it's /close but ok