Jeg havde en skidt oplevelse med Mols-Linjen
Det var en forfærgelig tur.
Det var en forfærgelig tur.
I’m Danish, and I acknowledge that when I speak regular Copenhagen Danish in Norway, people have a bit of a hard time understanding me (to quote Brooklyn 99 - “[Danish] is a garbage language for garbage people”, lol). Never in a rude manner though, and we always work it out, often just switching to English.
When I try to flatten out the accent a bit, so it sounds more Norwegian, but every single word still being Danish, the understanding improves significantly (the languages are, after all, very closely related).
I have this pride in me where I only want to speak English as a last resort in Norway and Sweden. We should be able to communicate with each other (with Danish being the ‘special kid’, I know)!
So my question is: Do Norwegians appreciate the effort if a Dane speaks “Danish with a Norwegian accent”, or is it considered pretty cringe, and I should just switch to English instead?
The Troubleshooting functionality in Windows has never ever - not one single time - helped me, all the way since the 90s until now.
Microsoft has dutifully carried this user experience over to Azure where the built in Copilot without exception fails to help diagnose or solve a single issue (out of many) I’ve had so far.
So thank you Microsoft, for making sure my experience remains unchanged. 🙏
[SOLVED]
I had for some reason (probably just being ignorant) set the Minimum Free Space on the share to 1.6TB which is way past the capacity of the 500GB NVMe cache.
So naturally Unraid went straight to the Secondary storage on the 16TB HDDs.
I set the Minimum Free Space to 100GB (having ~450GB on the cache), tested an image upload, and the disks did not spin up.
Success.
--------
Hey everyone
Tbh I'm not sure if this is an Immich issue or an Unraid issue. Please bear with me.
TL:DR
When the Immich phone app syncs media to Immich on Unraid, the 16TB drives spin up instead of the photos going to 500GB NVMe cache first, and then Mover action later.
I have set up Immich with a PostgreSQL container on the side as per the instructions. Created a share called Photos with Primary storage: Cache (500GB NVMe pool) and Secondary storage: Personal (16TB HDD pool).
I'm expecting the phone to back up photos to the NVMe cache first, not spinning any drives up, and then later when the Mover action is scheduled, I expect the drives to spin up and the NVMe cache transferring to the HDDs.
But this doesn't seem to happen. Whenever my phone backs up photos to Immich on Unraid, the drives spin up, leading me to believe that there is nothing being cached, and the data going straight to spinning disks.
I probably misconfigured something, but I'm kinda clueless where to start. Is this a common issue? And more importantly, is someone able to help me with the configuration? :-)
----
EDIT: Immich environmental variables below
DB_HOSTNAME=[REDACTED IP ADDRESS]
DOCKER_MODS=imagegenius/mods:universal-redis
UMASK=022
TZ=America/Los_Angeles
HOST_HOSTNAME=Unraid
MACHINE_LEARNING_HOST=0.0.0.0
MACHINE_LEARNING_PORT=3003
MACHINE_LEARNING_WORKER_TIMEOUT=120
PUID=99
HOST_OS=Unraid
HOST_CONTAINERNAME=immich
DB_USERNAME=postgres
DB_PASSWORD=[REDACTED PASSWORD]
SERVER_PORT=8080
SERVER_HOST=0.0.0.0
MACHINE_LEARNING_WORKERS=1
PGID=100
DB_DATABASE_NAME=immich
REDIS_HOSTNAME=localhost
DB_PORT=5433
REDIS_PORT=6379
REDIS_PASSWORD=
PATH=/lsiopy/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOME=/root
LANGUAGE=en_US.UTF-8
LANG=en_US.UTF-8
TERM=xterm
S6_CMD_WAIT_FOR_SERVICES_MAXTIME=0
S6_VERBOSITY=1
S6_STAGE2_HOOK=/docker-mods
VIRTUAL_ENV=/lsiopy
IMMICH_BUILD_DATA=/app/immich/data
IMMICH_ENV=production
IMMICH_MACHINE_LEARNING_URL=http://127.0.0.1:3003
IMMICH_MEDIA_LOCATION=/photos
MACHINE_LEARNING_CACHE_FOLDER=/config/machine-learning/models
NVIDIA_DRIVER_CAPABILITIES=compute,video,utility
SHARP_FORCE_GLOBAL_LIBVIPS=true
TRANSFORMERS_CACHE=/config/machine-learning/models
UV_PYTHON=/usr/bin/python3.11
MISE_TRUSTED_CONFIG_PATHS=/app/immich/plugins/mise.toml
MISE_DATA_DIR=/buildcache/mise
NODE_OPTIONS=--max-old-space-size=8192
NODE_ENV=production