Hello everybody,

I am stuck with this issue and idk whats going on

for example if i try to spin up every container i get this error

one week ago the server crashed totally and had these error logs (sorry

if is small and only a screen from mobile)

I still have space left on all shares and drives and i have really no idea whats going on..

any help would be really appreciated

i attach the diagnostics

thanks

homedata-diagnostics-20260610-1600.zip

"/mnt/user/claude-workspace" would be a path to a share called "claude-workspace", but you apparently haven't created/configured that share yet.

You also have a container that keeps restarting in a loop. Might want to investigate that.

Edited June 10Jun 10 by Kilrah

19 hours ago, Kilrah said:

"/mnt/user/claude-workspace" would be a path to a share called "claude-workspace", but you apparently haven't created/configured that share yet.

You also have a container that keeps restarting in a loop. Might want to investigate that.

I do not know to which container you are referring to, but the no space left is everywhere, example:

root@HomeData:/mnt/user/appdata# ls
DiskSpeed/      adguard-2/         crowdsec/         immich_public_proxy/  pgadmin4/        sonarr-1/              traefik/
HandBrake/      authentik/         debian-bookworm/  jdownloader2/         postgre_alpine/  steam-headless/        vaultwarden/
P3R-OpenRGB/    bazarr/            faster-whisper/   kopia/                prowlarr/        syslog-10.5.1.128.log  wireshark/
Stirling-PDF/   bbergle-jellyfin/  homarr/           overleaf/             qbittorrent/     tailscale/
actual-server/  cloudflared/       immich/           paperless-ai/         radarr-1/        tailscale_one/
adguard/        cloudflareddns/    immich_postgres/  paperless-ngx/        redis/           test_write
root@HomeData:/mnt/user/appdata# mkdir test
mkdir: cannot create directory ‘test’: No space left on device
root@HomeData:/mnt/user/appdata# touch a
touch: cannot touch 'a': No space left on device
root@HomeData:/mnt/user/appdata# 

please help im so stuck

thanks

There appears to be a container constantly restating; see if you can find which one by looking at their uptimes, disable that container, reboot to clear the logs, then post new diags after array start

I think I managed to find the restarting container (was restarting because the logs were full of "no space left")

let me know... thank you all

homedata-diagnostics-20260612-1431.zip

Your cache pool has a min free space of 200GB set but only has 191GB free, so anything trying to write to it is gonna be "out of space".

Pool level min free space should be set as a last resort should the share level min free spaces fail to prevent it from filling up completely, so typically lower than those. With share min free spaces set staggered in order of importance.

Edited June 12Jun 12 by Kilrah