Jump to content
We're Hiring! Full Stack Developer ×

(SOLVED) No space left on device (28)


sheldz8

Recommended Posts

This is the second time today I recieved this message, I'm not sure what is causing it and resolves itself after rebooting. 

 

Attached is the diagnostics (after reboot), error when trying to login and df -h output (before reboot).

 

When this happens I can still use SSH and Plex but I can't login / access SMB shares image.thumb.png.f6cecc07f0cf12347f31eccf5b85b350.png

 

image.png.455d870323aa40372f5d5b20d9b801b0.pngunraid-server-diagnostics-20210920-1552.zipimage.thumb.png.26caf0ca85ae521b44e94cf67f703d08.png

Edited by sheldz8
Link to comment

You have filled rootfs, which is where the OS is and so it makes it impossible for the OS to work with its own files.

 

This probably means you have something writing to a path that isn't on any actual storage device. One possibility would be a docker mapping with a host path that doesn't specify a user share or disk.

Link to comment

Not related, but your appdata, domains, system shares have files on the array and are set to move files to the array.

 

Best if these shares are all on pool (cache) and set to stay on pool. Having them on the array will keep disks spunup since these files are always open, and will impact docker/VM performance due to slower array.

Link to comment
11 hours ago, trurl said:

You have filled rootfs, which is where the OS is and so it makes it impossible for the OS to work with its own files.

 

This probably means you have something writing to a path that isn't on any actual storage device. One possibility would be a docker mapping with a host path that doesn't specify a user share or disk.

Is it possible to see what caused it because my server was fine since I built it. I haven't made any changes to it in 2 months 

Link to comment
11 hours ago, trurl said:

Not related, but your appdata, domains, system shares have files on the array and are set to move files to the array.

 

Best if these shares are all on pool (cache) and set to stay on pool. Having them on the array will keep disks spunup since these files are always open, and will impact docker/VM performance due to slower array.

The last time I set these shares to only use Cache my 1TB cache pool filled up fast and the server was unusable

Link to comment
7 hours ago, sheldz8 said:

Is it possible to see what caused it because my server was fine since I built it. I haven't made any changes to it in 2 months 

 

Examine each of your dockers and make sure any host path is a user share or disk.

 

7 hours ago, sheldz8 said:

The last time I set these shares to only use Cache my 1TB cache pool filled up fast and the server was unusable

 

This also indicates some misconfiguration. These shares shouldn't take nearly that much space.

 

Get rid of that gdrive temporarily and see if you can get things working correctly including moving those shares to cache.

Link to comment
  • sheldz8 changed the title to (SOLVED) No space left on device (28)
15 hours ago, trurl said:

 

Examine each of your dockers and make sure any host path is a user share or disk.

 

 

This also indicates some misconfiguration. These shares shouldn't take nearly that much space.

 

Get rid of that gdrive temporarily and see if you can get things working correctly including moving those shares to cache.

Thanks

 

I did check the dockers and all the volumes were correct but I left my server alone for 1 day and the disk didn't fill up again so I don't know what happened.

 

I'll sort out the shares when I get time.

Edited by sheldz8
Link to comment
17 hours ago, trurl said:

 

Examine each of your dockers and make sure any host path is a user share or disk.

 

 

This also indicates some misconfiguration. These shares shouldn't take nearly that much space.

 

Get rid of that gdrive temporarily and see if you can get things working correctly including moving those shares to cache.

I found the cause it was my rclone mount i'm not sure what happened but this topic is solved

 

image.png.704c8d0991599e2315f4dd1d74650e27.png

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...