Posts by tannaroo

    [How-To] Fix full OS filesystem - GUI login loop


    And continue in this thread instead of the other one

    Yes I had already gone through all of those steps. In the end, I just deleted all of my backups as somehow it is going to my root drive (even though I haven't touch OMV for a while and the external drive has plenty of space!)


    My docker goes to an external drive but I noticed in /var/lib/docker/overlay2 there appears to be a whole bunch of docker files (about 1.9GB) - I presume this can be deleted from my root drive as all docker + containers are on an external hard drive?


    Also noticed these module files some of which look old - can they be deleted?


    --- /usr/lib/modules -----------------------------------------------------------

    /..

    289.1 MiB [##########] /5.10.0-0.bpo.5-amd64

    288.9 MiB [######### ] /5.10.0-0.bpo.3-amd64

    276.7 MiB [######### ] /5.9.0-0.bpo.5-amd64

    275.5 MiB [######### ] /5.8.0-0.bpo.2-amd64

    271.8 MiB [######### ] /5.6.0-0.bpo.2-amd64

    4.3 MiB [ ] /5.5.0-0.bpo.2-amd64

    4.3 MiB [ ] /5.3.0-0.bpo.2-amd64

    4.2 MiB [ ] /4.19.0-5-amd64

    Getting lots of errors that my OS drive is full. My docker is going to an external drive (not my OS drive)


    I have tried clearing cache, docker system prune, omv-firstaid. The output of df shows my OS system drive is 100% but the output of ncdu -xshows the total size of all folders about 6GB (my OS drive is 20GB), so confused / can't locate where the folder taking up space?


    EDIT: Output of du -d1 -h / 


    root@omv:/# du -d1 -h /

    4.0K /export

    0 /sys

    32K /tmp

    0 /dev

    6.9M /etc

    160K /root

    50M /run

    2.8G /usr

    du: cannot access '/proc/3237/task/3237/fd/3': No such file or directory

    du: cannot access '/proc/3237/task/3237/fdinfo/3': No such file or directory

    du: cannot access '/proc/3237/fd/4': No such file or directory

    du: cannot access '/proc/3237/fdinfo/4': No such file or directory

    du: cannot read directory '/proc/3274/task/3274/net': Invalid argument

    du: cannot read directory '/proc/3274/net': Invalid argument

    du: cannot read directory '/proc/3275/task/3275/net': Invalid argument

    du: cannot read directory '/proc/3275/net': Invalid argument

    du: cannot read directory '/proc/3276/task/3276/net': Invalid argument

    du: cannot read directory '/proc/3276/net': Invalid argument

    du: cannot read directory '/proc/3277/task/3277/net': Invalid argument

    du: cannot read directory '/proc/3277/net': Invalid argument

    du: cannot read directory '/proc/3278/task/3278/net': Invalid argument

    du: cannot read directory '/proc/3278/net': Invalid argument

    0 /proc

    8.0K /media

    4.0K /config_directory

    2.4G /var

    205M /boot

    4.0K /home

    69M /opt

    16K /sharedfolders

    4.0K /mnt

    2.9T /srv

    16K /lost+found

    2.9T /

    Today I woke up with lots of errors that my OS drive is full. I have tried clearing cache, docker system prune. The output of df shows my OS system drive is 100% but the output of du -dl -h / shows ther total size of all folders about 6GB (my OS drive is 20GB), so confused / can't locate where the folder taking up space?


    Also my docker is going to an external drive (not my OS drive)


    root@omv:~# du -d1 -h /

    4.0K /export

    0 /sys

    4.0K /tmp

    0 /dev

    6.9M /etc

    156K /root

    7.3M /run

    2.8G /usr

    du: cannot read directory '/proc/7283/task/7283/net': Invalid argument

    du: cannot read directory '/proc/7283/net': Invalid argument

    du: cannot read directory '/proc/7284/task/7284/net': Invalid argument

    du: cannot read directory '/proc/7284/net': Invalid argument

    du: cannot read directory '/proc/7285/task/7285/net': Invalid argument

    du: cannot read directory '/proc/7285/net': Invalid argument

    du: cannot read directory '/proc/7286/task/7286/net': Invalid argument

    du: cannot read directory '/proc/7286/net': Invalid argument

    du: cannot read directory '/proc/7287/task/7287/net': Invalid argument

    du: cannot read directory '/proc/7287/net': Invalid argument

    du: cannot access '/proc/7306/task/7306/fd/4': No such file or directory

    du: cannot access '/proc/7306/task/7306/fdinfo/4': No such file or directory

    du: cannot access '/proc/7306/fd/4': No such file or directory

    du: cannot access '/proc/7306/fdinfo/4': No such file or directory

    0 /proc

    8.0K /media

    4.0K /config_directory

    2.4G /var

    205M /boot

    4.0K /home

    69M /opt

    16K /sharedfolders

    4.0K /mnt

    1.8T /srv

    16K /lost+found

    1.8T /

    There is no TessDrive in fstab. So it cannot be mounted by OMV. So there cannot be shared folders on that drive.

    How do you access that drive from Windows?

    Definitely showing on OMV5, File Systems and mounted.

    I also set up TessDrive through SMB/CIFS and just access the folders through Windows Explorer. Can open/write to all documents in these subfolders no problems.


    EDIT: I just tried to mount it through the CLI but it said it cannot find that drive in /etc/fstab as you highlighted. Yet its showing on OMV5 as mounted. Is there a way to add it to fstab or do I just disconnect/reconnect the drive?

    There is something funny going on:

    root@omv:~# ls -l /srv/

    total 52

    drwxrwxrwx 2 root root 4096 Jul 21 2020 5abca6fb-5bf9-42da-8cf1-3f5e1381ff95

    drwxrwxrwx 2 root root 4096 Jul 21 2020 9b151806-f786-4611-8289-29b12d8a5756

    drwxrwxrwx 2 root root 4096 Jul 21 2020 a222ea17-b53b-42a2-8278-3a7321364d31

    drwxrwxrwx 2 root root 4096 Jul 21 2020 d97deb01-7286-4661-b6d7-520fa715fe43

    drwxr-sr-x 10 rob users 4096 Jun 3 13:25 dev-disk-by-label-Hippo

    drwxr-xr-x 9 root root 4096 May 14 14:40 dev-disk-by-label-Monkey

    drwxr-xr-x 2 root root 4096 May 14 17:08 dev-disk-by-label-TessDrive

    drwxr-xr-x 4 root root 4096 May 14 14:41 dev-disk-by-uuid-02202802-36c8-4e4e-a5a4-82cab00ceb70

    drwxr-xr-x 2 ftp nogroup 4096 Oct 22 2020 ftp

    drwxr-xr-x 3 root root 4096 Mar 27 10:25 pillar

    drwxr-xr-x 5 root root 4096 Mar 27 10:25 salt


    Hippo and TessDrive are separate drives.

    Yet when I look in Hippo, the Tess folder belongs to TessDrive (as per windows explorer) but the following shows Tess folder under the Hippo drive (when it should be under TessDrive).

    root@omv:~# cd /srv/dev-disk-by-label-Hippo/

    root@omv:/srv/dev-disk-by-label-Hippo# ls -l

    total 68

    -rw------- 1 root users 6144 Jun 2 20:24 aquota.group

    -rw------- 1 root users 8192 Jun 2 20:24 aquota.user

    drwxrwsrwx+ 10 root users 4096 Jun 2 21:00 Documentaries

    drwx------ 2 root root 16384 May 17 2020 lost+found

    drwxr-sr-x 3 rob users 4096 Jun 2 12:30 Tess

    drwxrwsrwx 5 root users 4096 Jun 2 21:00 Video

    root@omv:/srv/dev-disk-by-label-Hippo#

    Can you post your fstab?


    cat /etc/fstab

    root@omv:~# cat /etc/fstab

    # /etc/fstab: static file system information.

    #

    # Use 'blkid' to print the universally unique identifier for a

    # device; this may be used with UUID= as a more robust way to name devices

    # that works even if disks are added and removed. See fstab(5).

    #

    # <file system> <mount point> <type> <options> <dump> <pass>

    # / was on /dev/sda1 during installation

    UUID=e6208477-f2c8-4a07-b472-0fb038cffce2 / ext4 errors=remount-ro 0 1

    # swap was on /dev/sda5 during installation

    UUID=41bd6423-3994-44a7-8642-e5132de03544 none swap sw 0 0

    /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0

    # >>> [openmediavault]

    /dev/disk/by-label/Monkey /srv/dev-disk-by-label-Monkey ext4 defaults,nofail,user_xatt r,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2

    /dev/disk/by-label/Hippo /srv/dev-disk-by-label-Hippo ext4 defaults,nofail,user_xatt r,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2

    /dev/disk/by-uuid/02202802-36c8-4e4e-a5a4-82cab00ceb70 /srv/dev-disk-by-uuid-02202802-36c8-4e4e- a5a4-82cab00ceb70 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,j qfmt=vfsv0,acl 0 2

    # <<< [openmediavault]

    On Hippo you have a folder TessDrive. Any chance you are mixing up the folder TessDrive with the drive TessDirve?

    True there is a empty folder on Hippo called TessDrive (which I may have accidently created) - need to delete that. But there is also a external drive called TessDrive and that is the one I cannot connect with Resilio.

    according to the previous post, there are no subfolders on TessDrive:

    I know but through windows explorer they are definitely there (there are two subfolders) as I can see them/use them. Not sure why this is the case.

    Through OMV5, Shared Folders - they are also showing there each with read/write/execute access.

    Yes they are two separate drives (hippo and tessdrive) being connected to resilio. Hippo drive works no problem but TessDrive is connecting to resilio but not showing the subfolders and subseqently the error.


    Output as follows:


    root@omv:~# ls -l /srv

    total 52

    drwxrwxrwx 2 root root 4096 Jul 21 2020 5abca6fb-5bf9-42da-8cf1-3f5e1381ff95

    drwxrwxrwx 2 root root 4096 Jul 21 2020 9b151806-f786-4611-8289-29b12d8a5756

    drwxrwxrwx 2 root root 4096 Jul 21 2020 a222ea17-b53b-42a2-8278-3a7321364d31

    drwxrwxrwx 2 root root 4096 Jul 21 2020 d97deb01-7286-4661-b6d7-520fa715fe43

    drwxr-sr-x 12 rob users 4096 Jun 2 12:27 dev-disk-by-label-Hippo

    drwxr-xr-x 9 root root 4096 May 14 14:40 dev-disk-by-label-Monkey

    drwxr-xr-x 2 root root 4096 May 14 17:08 dev-disk-by-label-TessDrive

    drwxr-xr-x 4 root root 4096 May 14 14:41 dev-disk-by-uuid-02202802-36c8-4e4e-a5a4-82cab00ceb70

    drwxr-xr-x 2 ftp nogroup 4096 Oct 22 2020 ftp

    drwxr-xr-x 3 root root 4096 Mar 27 10:25 pillar

    drwxr-xr-x 5 root root 4096 Mar 27 10:25 salt

    Can you show what you have for the folder that is working and for the one that is not working? With the "ls -l" command?

    Not working drive


    root@omv:~# ls -l /srv/dev-disk-by-label-TessDrive

    total 0


    Working Drive:


    root@omv:~# ls -l /srv/dev-disk-by-label-Hippo

    total 76

    -rw------- 1 root users 6144 Jun 2 20:24 aquota.group

    -rw------- 1 root users 8192 Jun 2 20:24 aquota.user

    drwxrwsrwx+ 10 root users 4096 Jun 2 21:00 Documentaries

    drwx------ 2 root root 16384 May 17 2020 lost+found

    drwxr-sr-x 3 rob users 4096 Jun 2 12:30 Tess

    drwxr-sr-x 2 root users 4096 Jun 2 12:27 TessDrive

    drwxrwsrwx 5 root users 4096 Jun 2 21:00 Video

    You can also use the resetperms plugin to reset the permissions to default values,


    How did you set PGID and PUID?


    For use on OMV PUID should be 1000 (first user created in the GUI) and the PGID should be 100 (group users; every user created in the GUI of OMV is member of that group by default)

    Code
    environment:
    - PUID=1000
    - PGID=100

    did that previously (reset permissions) and using thise PUID/PGID values.