After Updating the OMV OS BOOT Disk is FULL

  • I have used OMV 5 for a while - Seems that every time I update something happens :)


    I have Updated everything that came up in the list but after I saw that the SSD which has the OS OMV 5 on it is now full. I dont want to play around or start tinkering until I've found out why this has happened. Please could someone help me out with what this could be and how to fix it without losing any of my data?


    I use the server for all my Media and Docker. The only program that isnt on the Docker is Plex Media Server which is on a stand alone Windows 10 mini server which I have mapped to run with the OMV server


    Im thinking it maybe the updates made by OMV and that the old versions are still on the drive but this would mean over 100GB data has been stored for no reason


    Many thanks


    Please see the attached screenshot


  • DNUKaen

    Changed the title of the thread from “After Updating the OMV OS Disk is FULL” to “After Updating the OMV OS BOOT Disk is FULL”.
  • I have followed that and have it in terminal mac - Honestly dont know what Im looking for. Ill put up in here for u to see


    ```

    Filesystem 1K-blocks Used Available Use% Mounted on

    udev 8146020 0 8146020 0% /dev

    tmpfs 1634288 175920 1458368 11% /run

    /dev/sde1 222836468 222820084 0 100% /

    tmpfs 8171424 0 8171424 0% /dev/shm

    tmpfs 5120 0 5120 0% /run/lock

    tmpfs 8171424 0 8171424 0% /sys/fs/cgroup

    tmpfs 8171424 20 8171404 1% /tmp

    /dev/sdc1 3844609856 105002308 3739591164 3% /srv/dev-disk-by-uuid-24509e99-2d3f-4a2c-9a26-5af0d492b1fd

    /dev/sdb1 13563526284 1992650556 11570859344 15% /srv/dev-disk-by-uuid-b0233da0-ed28-400c-bdb4-17d6b575b727

    /dev/sda1 11625432492 10868062876 757353232 94% /srv/dev-disk-by-uuid-314586d2-129e-476d-b9e3-dc0a8220a579

    Media:65a8a932-6051-476f-8a94-9721f97fff88 29033568632 12965715740 16067803740 45% /srv/65a8a932-6051-476f-8a94-9721f97fff88

    overlay 222836468 222820084 0 100% /var/lib/docker/overlay2/304a53cfac5135748e88ab3f796680b5fb77cf79c57266c7eee8dfc8f254e272/merged

    overlay 222836468 222820084 0 100% /var/lib/docker/overlay2/4129587b67f4b252bc2cb6615b25696197d93cbca56f292792b4a11bd57aa6bd/merged

    overlay 222836468 222820084 0 100% /var/lib/docker/overlay2/dc36d92a6838a258743f94a054db9dc7e50457f5da6169a5964f9eafc645e21a/merged

    overlay 222836468 222820084 0 100% /var/lib/docker/overlay2/20853ade46a913565d89573c83d2caa57f474ff7ed4e0cee3bbb5240e8688849/merged

    overlay 222836468 222820084 0 100% /var/lib/docker/overlay2/5aa009f583ff3a8e089bd131fdddde8f539232cc781f2f291372d8fa319f42bc/merged

    overlay 222836468 222820084 0 100% /var/lib/docker/overlay2/e54a9ca2ce940842f26ebbd107ecee527125d7de3644ced19b3bde54729020cc/merged

    overlay 222836468 222820084 0 100% /var/lib/docker/overlay2/8d85ffd4c2230e0d29c21c8f01838741b4e5a5b87148f268246bf7c090caad62/merged

    root@OMV5-Daniel:~# cd /

    root@OMV5-Daniel:/# du -xhd1

    4.0K ./mnt

    48K ./root

    129M ./opt

    8.0K ./media

    1.7M ./srv

    4.0K ./export

    166M ./boot

    4.0K ./home

    6.7M ./etc

    2.6G ./usr

    16K ./lost+found

    du -ahxd1 | sort -hr | head -n 10

    210G ./var

    213G .

    root@OMV5-Daniel:/# du -ahxd1 | sort -hr | head -n 10

    cd ./var

    cd213G .

    210G ./var

    2.6G ./usr

    166M ./boot

    129M ./opt

    6.7M ./etc

    1.7M ./srv

    48K ./root

    16K ./lost+found

    8.0K ./media

    root@OMV5-Daniel:/# cd ./var

    root@OMV5-Daniel:/var# cd var

    -bash: cd: var: No such file or directory

    root@OMV5-Daniel:/var# cd /var

    root@OMV5-Daniel:/var# ls -al

    total 44

    drwxr-xr-x 11 root root 4096 May 16 16:59 .

    drwxrwxr-x 19 root root 4096 Aug 4 22:18 ..

    drwxr-xr-x 2 root root 4096 Aug 7 07:38 backups

    drwxr-xr-x 10 root root 4096 May 8 02:06 cache

    drwxr-xr-x 35 root root 4096 May 8 16:23 lib

    drwxrwsr-x 2 root staff 4096 Jul 10 2020 local

    lrwxrwxrwx 1 root root 9 May 8 01:47 lock -> /run/lock

    drwxr-xr-x 13 root root 4096 Aug 5 00:00 log

    drwxrwsr-x 3 root mail 4096 May 16 16:59 mail

    lrwxrwxrwx 1 root root 4 May 8 01:47 run -> /run

    drwxr-xr-x 7 root root 4096 May 8 01:47 spool

    drwxrwxrwt 5 root root 4096 Aug 7 07:39 tmp

    drwxr-xr-x 4 root root 4096 May 8 01:47 www```

  • It looks like docker is probably storing container data on your OS drive.. and I'm guessing with the amount of media you have, you have a large Plex (or Emby or Jellyfin) collection, maybe with video thumbnails enabled... that is filling up your drive.


    What is the output of


    Code
     docker info | grep Root

    Air Conditioners are a lot like PC's... They work great until you open Windows.


  • I have a huge Plex Lib but thought using a separate server with Plex Media Server on it that that data wud be stored there?


    How wud I find out the docker info? Through root?

  • I have a huge Plex Lib but thought using a separate server with Plex Media Server on it that that data wud be stored there?


    How wud I find out the docker info? Through root?

    What do you mean a separate server? Are you using docker on OMV to serve plex?


    Post the output of that command I put in my post.

    Air Conditioners are a lot like PC's... They work great until you open Windows.


  • ```

    root@OMV5-Daniel:~# docker info | grep Root

    Docker Root Dir: /var/lib/docker```


    I have PMS on a separate server but run docker and store all the Media on the OMV server

  • I cd into /var and did the du command and terminal just scrolled and ran for about 30s but looked like docker overlays were the main thing scrolling. Mainly ./lib/docker/overlay2/ files. I've tried to add all the files terminal spat out in a TextEdit file but its way to big to upload here


    Any idea how to firstly stop this happening anymore & then removing these files from the Boot Drive in OMV

  • I cd into /var and did the du command and terminal just scrolled and ran for about 30s but looked like docker overlays were the main thing scrolling. Mainly ./lib/docker/overlay2/ files. I've tried to add all the files terminal spat out in a TextEdit file but its way to big to upload here


    Any idea how to firstly stop this happening anymore & then removing these files from the Boot Drive in OMV

    If this is happening over and over, it is something you are doing wrong. Like I said, the likelihood it is docker related seems pretty high.

    Air Conditioners are a lot like PC's... They work great until you open Windows.


  • I cd into /var and did the du command and terminal just scrolled and ran for about 30s

    You need to run the complete du command.


    cd /var

    du -ahxd1 | sort -hr | head -n 10


    Than cd in the largest folder and run the complete du command again.

    Read again what is written in the how-to.

  • Maybe it is Portainer downloading all versions of an image.

    But could also be a log file.

    Or something new 8|

    Log file is a possibility.., but even a bunch of images would still be in /var/lib/docker


    200 some odd gigs of logs would be flat out incredible.

    Air Conditioners are a lot like PC's... They work great until you open Windows.


  • Well the problem I have now is I cant log into OMV. I put in my details and it just cycles round to the login page. I think its time for a check of my backups and change OS

  • Well the problem I have now is I cant log into OMV. I put in my details and it just cycles round to the login page

    This is because of your OS filesystem being full.


    Why don't you just check what is filling your OS drive? Then you can free some space and solve the root issue.

    There are some common root causes mentioned in the How-To and also here in this thread.

    But if you don't tell us, what is filling your drive, there is no way we can help you.

  • Well the problem I have now is I cant log into OMV. I put in my details and it just cycles round to the login page. I think its time for a check of my backups and change OS

    You can do that I guess, but you have something set up incorrectly. Guess what's going to happen when you go to another OS and you set it up incorrectly?


    I guess the choice is yours, fix the problem or move on. You've been told multiple times what directories to check.

    Air Conditioners are a lot like PC's... They work great until you open Windows.


  • Im new to all of this and this is why Im asking in the forum and not trying to do it myself and make more mistakes. I will look into what is wrong today as I have no distractions (KIDS) and hopefully I can find the cause and resolve it


    Thanks for the help & apologises for the stupidity

  • I have done this which I dont know if its correct but Im sure someone will tell me


    root@OMV5-Daniel:/var# du -ahxd1 | sort -hr | head -n 10

    210G .

    209G ./lib

    651M ./cache

    129M ./log

    6.6M ./www

    476K ./backups

    120K ./spool

    28K ./tmp

    8.0K ./mail

    4.0K ./local

    root@OMV5-Daniel:/var# ./lib

    -bash: ./lib: Is a directory

    root@OMV5-Daniel:/var# cd lib

    root@OMV5-Daniel:/var/lib# du -ahxd1 | sort -hr | head -n 10

    209G ./docker

    209G .

    129M ./containerd

    121M ./apt

    25M ./dpkg

    22M ./rrdcached

    2.2M ./samba

    604K ./usbutils

    460K ./smartmontools

    396K ./systemd

    root@OMV5-Daniel:/var/lib#

    root@OMV5-Daniel:/var/lib# du -ahxd1 | sort -hr | head -n 10

    209G ./docker

    209G .

    129M ./containerd

    121M ./apt

    25M ./dpkg

    22M ./rrdcached

    2.2M ./samba

    604K ./usbutils

    460K ./smartmontools

    396K ./systemd

    root@OMV5-Daniel:/var/lib# cd docker

    root@OMV5-Daniel:/var/lib/docker# du -ahxd1 | sort -hr | head -n 10

    209G .

    208G ./overlay2

    912M ./containers

    249M ./image

    4.1M ./volumes

    120K ./network

    88K ./buildkit

    16K ./plugins

    4.0K ./trust

    4.0K ./tmp

    root@OMV5-Daniel:/var/lib/docker# cd overlay2

    root@OMV5-Daniel:/var/lib/docker/overlay2# du -ahxd1 | sort -hr | head -n 10

    208G .

    438M ./038de665c3c665091508602ddc46bc9dfece98b0ffa7092bb22697851db1b26b

    432M ./178e22aafe625409cc8b29dda4bf382422a4e686355e5b9c3f1917d742e20b66

    431M ./bbe95ed1a415342f89e2690bede84e4771221e60dbde30c02d22bff159070d1c

    431M ./9993987c9d5fe461faaebc07a76bd2e5e6641a54d4f5d226d4610fb3310ae8ce

    431M ./5cbf481ce48b8284f68f93be8f5e32a5c1c7ad33ba2a093cc55ad3c030eba0eb

    431M ./42f703d0c2063a441bfbb6c5627932cec9fdfbd907dde2a986070fd27d5905ef

    431M ./113b7feb93ffd54c338c1b6d3ed4c4d3b4cd2755c43afbdb731c0bf71f9d5491

    425M ./e2dd16b6f8b0be9758f1acea1a1f2f77bb425693ffefe96392490b8c380be30e

    425M ./c750eb7fd30490b4b19eb755326d3944b9a6216b3475fff61efdfb6828fa76d2

    root@OMV5-Daniel:/var/lib/docker/overlay2#


    So what I can see is that its a problem in the Docker folder & that there are loads of 432Mb files in there

  • KM0201 I found this quote you wrote for someone in July '19 for a similar question with Docker filling up - will this work for me?


    137-34a6ffd7cb09572b6a2ab33f352a69f1657537a9.pngOnline
    KM0201
    Moderator

    Reactions Received509Posts3,560

    1. Create your container folder ("Containers") in the webUI. This will store your containers on one of your data drives (which are presumably much larger than 8gig)


    2. SSH your server and get root access


    3. Stop docker service: systemctl stop docker


    4. Move the docker folder to Containers folder: mv /var/lib/docker /sharedfolders/Containers


    5. Create a link between the two: ln -s /sharedfolders/Containers /var/lib/docker


    6. Start docker service: systemctl start docker


    Problem solved.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!