Hello there,
Facing some problems, and i dont know where or how to search.

Basically, some services wont start, saying "no space left".

JellyFin:

6-rc: fatal: unable to write /run/s6-rc/state: No space left on device
s6-linux-init-shutdownd: fatal: unable to rename stage 4.new to stage 4: No space left on device
s6-supervise s6-linux-init-shutdownd: warning: unable to write supervise/death_tally: No space left on device
s6-supervise s6-linux-init-shutdownd: warning: unable to write status file: No space left on device
s6-supervise s6-linux-init-shutdownd: warning: unable to write status file: No space left on device
s6-supervise s6-linux-init-shutdownd: warning: unable to write status file: No space left on device
s6-linux-init: warning: unable to dump kernel environment to /run/s6/container_environment: No space left on device

Postgres_Immich

2026-02-08 04:12:30.573 GMT [1] LOG:  database system is shut down
sed: cannot rename /etc/postgresql/sedQLYN7T: No space left on device
sed: cannot rename /etc/postgresql/sedZQolOM: No space left on device
sed: cannot rename /etc/postgresql/sedPjmVnu: No space left on device
sed: cannot rename /etc/postgresql/sed0PtNOB: No space left on device
sed: cannot rename /etc/postgresql/sedG3ja3V: No space left on device
sed: cannot rename /etc/postgresql/sedXwgag9: No space left on device
sed: cannot rename /etc/postgresql/sedRBAngh: No space left on device
Using SSD storage

I'm not sure where to start looking.

My cache ssd has enough space.

Happy if someone can help.

Thanks.

venturanas-diagnostics-20260208-1442.zip

Docker image is close to full, but it's already quite big, so there may be something misconfigured.

Start by recreating it with same or similar size, then monitor its usage.

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file

Then:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications

Also see below if you have any custom docker networks:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks

The usual cause of filling docker.img is an application writing to a path that isn't mapped. Note that this isn't about the mappings exactly, it is whether the application itself is configured to write to a path that isn't in the mappings.