Immich-server incredible slow, can`t upload pictures and container crashes

My Immich Server is incredible slow. I can`t really upload any pictures anymore. If takes like 15-30 mins to upload a single picture and then the server usually dies and I have to restart the container. The Background task for creating thumbnails is broken too. Thumbnail generations aborts with error. If I restart it by hand, it usually runs smoothly but slow. But it still does have problem to load all the thumbnails. A lot of my thumbnails are blured or have "Error while loading the picture" Last time the container died so hard, that I could ne stop/kill or even remove it. Since the container did not responded. Even a restart of the docker daemon did not helped. I had to fully restart the complete server to kill it and restart it. Just now I tried to access the generall settings and got this error:
Failed to get storage (500)

Stacktrace
Error: Error: 500
at Object.ze [as ok] (http://homeserver:2283/_app/immutable/chunks/B8x4AGLb.js:1:5430)
at async U (http://homeserver:2283/_app/immutable/chunks/BANhuybm.js:1:847)
at async _r (http://homeserver:2283/_app/immutable/nodes/35.CdWh6-8D.js:1:2919)
at async $e (http://homeserver:2283/_app/immutable/chunks/OxX4rFMK.js:1:15886)
Failed to get storage (500)

Stacktrace
Error: Error: 500
at Object.ze [as ok] (http://homeserver:2283/_app/immutable/chunks/B8x4AGLb.js:1:5430)
at async U (http://homeserver:2283/_app/immutable/chunks/BANhuybm.js:1:847)
at async _r (http://homeserver:2283/_app/immutable/nodes/35.CdWh6-8D.js:1:2919)
at async $e (http://homeserver:2283/_app/immutable/chunks/OxX4rFMK.js:1:15886)
I use immich in docker on an ubuntu home server. Everything is freshly up to date. Database is on the locally SSD. Data (Pictures/Thumbs etc) are on a connected NAS Any ideas how to fix that? Or is it a storage problem? The NAS is working completly normal for me
11 Replies
Immich
Immich3w ago
:wave: Hey @Introser, 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. :blue_square: 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.
Zeus
Zeus3w ago
What is the system specs of the Ubuntu server? It sounds more like your NAS might have a terrible connection or just not working properly. How is it mounted?
Mraedis
Mraedis3w ago
Please post compose and env and I pray you don't have nested mounts
Introser
IntroserOP3w ago
Its a beelink mini pc. Kinda potent. Beelink Mini PC EQ12 Office Mini Computer, 12th Gen Intel Alder Lake-N100 Prozessor (bis zu 3.40GHz), 16GB DDR5 500GB SSD and its not at all under load. Usually only a up to 10-20% load. NAS is a WD My Cloud EX2 Ultra. I know, shame on me. But it is doing its job and not under load too. I can freely work with it and I dont see any bad connection etc.
Zeus
Zeus3w ago
I suspect that a standalone hard drive “NAS” is unable to sustain the IOPS required for immich Are you using samba or what? To test you can try using a local mount directly on the Ubuntu server
Introser
IntroserOP3w ago
I mount it via
mount -t cifs -o
mount -t cifs -o
(Samba) The database is on the internal SSD. ONLY the pictures/thumbnails etc are on the NAS
Zeus
Zeus3w ago
I would try with local storage to test. That seems like the cause of these issues Yes I understand that but you’re having all these issues with the thumbs etc
Introser
IntroserOP3w ago
and it worked flawless for like a year
Mraedis
Mraedis3w ago
Not saying the hardware is bad, but that's the thing with everything that's broken it all worked until it didn't From the specs it should work fine, but like zeus said just try it locally to eliminate other factors
Introser
IntroserOP3w ago
It was the NAS. One drive was dead, even though the NAS displayed it as healthy. The other one had really bad SMART values and is probly close to dead. Rebuilded the array and it works like a charm now. Tests before rebuilding showed incredible speeds of around 5-10 kb/s on the NAS 😄 thanks @Mraedis @Zeus
Immich
Immich3w ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?