April 6, 20242 yr Hey everyone, out of the blue I have a Problem with some Docker Containers. I was updating some plugins in Homeassistant and needed to restart the service (inside the Container) but it never came back up. So I decided to restart the Container itself and even it shos "running" in Unraid, it is not reachable via Web Interface. The log tells me "OSError: [Errno 28] No space left on device: '/config/home-assistant.log.fault'". So, because the Container itself does not collect any Data (not that much) and I have still plenty of Space (324 GB free in the array) I suspected a permissions Problem and ran Tools/NewPerms on all Disks but that did not help. I even rebooted the Unraid System but no luck. Paperless tells me: "sqlite3.OperationalError: unable to open database file" Jellyfin: "Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 14: 'unable to open database file'." Audiobookshelf: "Error: ENOSPC: no space left on device, open '/metadata/logs/crash_logs.txt'" I have no clue whats going on here or where to start investigating. homeserver-diagnostics-20240406-1921.zip
April 7, 20242 yr Author So I've searched and tried a little more but nothing helped. The Docker vDisk Size is set to the 20GB default and my Containers are only using 11.9GB in total. Even if I increase this to 30GB nothing changes. Ive also tried to delete some containers and recreated it from the "previous Apps" Section but they still complain about not enough disk space.
April 7, 20242 yr Author I've deleted the /mnt/user/system/docker/docker.img via Settings and recreated one single container -> same Problem. I'm really out of Ideas here. Something is totally screwed up.
April 7, 20242 yr Community Expert This is very strange, everything looks normal to me in the diags, try creating a new docker image but on a new share, create a new share called docker for example, just to test.
April 7, 20242 yr Community Expert Solution 15 hours ago, ErrPunktErr said: "OSError: [Errno 28] No space left on device: '/config/home-assistant.log.fault'" Your appdata share is set to 200GB min free space, both of your drives are below that at 114 and 188 respectively so anything trying to write to appdata will encounter a "disk full" error. I.e. it was never the Docker image. Edited April 7, 20242 yr by Kilrah
April 7, 20242 yr Author 20 minutes ago, Kilrah said: Your appdata share is set to 200GB min free space, both of your drives are below that at 114 and 188 respectively so anything trying to write to appdata will encounter a "disk full" error. Thats it. Thank You. I'v temporary set the limit down to 100GB and recreating all Containers now. Is there a reason why the limit counts on the single Disks and not on the Array Size? Beacause thats what I was thinking. Also Thank You @JorgeB for your Answer.
April 7, 20242 yr Community Expert Just now, ErrPunktErr said: Is there a reason why the limit counts on the single Disks and not on the Array Size? The point of min free space is to prevent a single disk from becoming too full and force a switch to the next disk when said min free space is reached. Of course if no other disk fits the bill then you get "no space left".
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.