System partition full (newbie)

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • System partition full (newbie)

      Hi, I have a rock64 with 4gb ram and 32gb emmc with OMV 4. I noticed one of the system partition is almost full, namely /dev/mmcblk0p2. I only have 1 docker container running (I had 2 but I uninstalled one to free up some space) and I already cleared system logs.

      Source Code

      1. root@rock64:~# df -h
      2. Filesystem Size Used Avail Use% Mounted on
      3. udev 2.0G 0 2.0G 0% /dev
      4. tmpfs 393M 5.8M 387M 2% /run
      5. /dev/mmcblk0p2 7.4G 6.7G 134M 99% /
      6. tmpfs 2.0G 0 2.0G 0% /dev/shm
      7. tmpfs 5.0M 8.0K 5.0M 1% /run/lock
      8. tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
      9. tmpfs 2.0G 4.0K 2.0G 1% /tmp
      10. /dev/mmcblk0p1 58M 39M 17M 70% /boot
      11. /dev/sda1 2.7T 1.9T 885G 68% /srv/dev-disk-by-label-ELEMENTS
      12. /dev/sdb1 3.6T 3.0T 655G 83% /srv/dev-disk-by-id-ata-WDC_WD40EFRX-68N32N0_WD-WCC7K5CFTP6C-part1
      13. /dev/zram0 49M 9.0M 36M 20% /var/log
      14. folder2ram 2.0G 13M 2.0G 1% /var/log.hdd
      15. folder2ram 2.0G 11M 2.0G 1% /var/tmp
      16. folder2ram 2.0G 896K 2.0G 1% /var/lib/openmediavault/rrd
      17. folder2ram 2.0G 20K 2.0G 1% /var/spool
      18. folder2ram 2.0G 13M 2.0G 1% /var/lib/rrdcached
      19. folder2ram 2.0G 12K 2.0G 1% /var/lib/monit
      20. folder2ram 2.0G 4.0K 2.0G 1% /var/lib/php
      21. folder2ram 2.0G 4.0K 2.0G 1% /var/lib/netatalk/CNID
      22. folder2ram 2.0G 524K 2.0G 1% /var/cache/samba
      23. shm 64M 0 64M 0% /var/lib/docker/containers/a8a1098f123578c1be465f73546d4a6e54bada77f3886d1045e92b614685a73e/mounts/shm
      24. tmpfs 393M 0 393M 0% /run/user/0
      Display All

      Help please :) . Also, I have a 32gb emmc, why is my system partition only 7.4gb?
    • Source Code

      1. root@rock64:~# du -d1 -h /
      2. 38M /boot
      3. 13M /bin
      4. 0 /dev
      5. 11M /etc
      6. 0 /export
      7. 15M /home
      8. 016M /media
      9. 0 /mnt
      10. 0 /opt
      11. du: cannot read directory '/proc/3586/task/3586/net': Invalid argument
      12. du: cannot read directory '/proc/3586/net': Invalid argument
      13. du: cannot read directory '/proc/3587/task/3587/net': Invalid argument
      14. du: cannot read directory '/proc/3587/net': Invalid argument
      15. du: cannot access '/proc/3588/task/3588/fd/3': No such file or directory
      16. du: cannot access '/proc/3588/task/3588/fdinfo/3': No such file or directory
      17. du: cannot access '/proc/3588/fdinfo/4': No such file or directory
      18. 0 /proc
      19. 11M /root
      20. 5.8M /run
      21. 14M /sbin
      22. 0 /selinux
      23. 4.8T /sharedfolders
      24. 4.8T /srv
      25. 0 /sys
      26. 1.2G /usr
      27. 1.2G /var
      28. 216K /scripts
      29. 9.6T /
      Display All
    • FabrizioMaurizio wrote:

      I have a 32gb emmc, why is my system partition only 7.4gb?
      To allow you to use the last partition for data storage as explained at the download page: sourceforge.net/projects/openm…ngle%20Board%20Computers/

      An OMV install is pretty fine with less than 4GB so those 8GB we limit the OS partition too are some sort of safety headroom. If you put your dockers on the OS drive on a SD card be prepared that the card might die pretty soon (flashmemory plugin won't help here at all).
    • I booted with my drives disconnected.


      Source Code

      1. root@rock64:~# du -d1 -h /
      2. 38M /boot
      3. 13M /bin
      4. 0 /dev
      5. 11M /etc
      6. 0 /export
      7. 15M /home
      8. 116M /lib
      9. 0 /media
      10. 0 /mnt
      11. 0 /opt
      12. du: cannot read directory '/proc/3014/task/3014/net': Invalid argument
      13. du: cannot read directory '/proc/3014/net': Invalid argument
      14. du: cannot read directory '/proc/3015/task/3015/net': Invalid argument
      15. du: cannot read directory '/proc/3015/net': Invalid argument
      16. du: cannot access '/proc/3038/task/3038/fd/3': No such file or directory
      17. du: cannot access '/proc/3038/task/3038/fdinfo/3': No such file or directory
      18. du: cannot access '/proc/3038/fd/4': No such file or directory
      19. du: cannot access '/proc/3038/fdinfo/4': No such file or directory
      20. 0 /proc
      21. 11M /root
      22. 5.8M /run
      23. 14M /sbin
      24. 0 /selinux
      25. 5.2G /sharedfolders
      26. 4.0K /srv
      27. 0 /sys
      28. 4.0K /tmp
      29. 1.2G /usr
      30. 1.2G /var
      31. 216K /scripts
      Display All
      Looks like there is some stuff in sharedfolders. Can I simply delete it? I checked and it's old stuff I don't need.
    • KM0201 wrote:

      Sharedfolders is where your OMV folders are stored. Nothing there should be on your SDcard (unless you've done something really unique with your setup)
      It's as easy as loosing connection to a drive (which on majority of SBC is quite easy). One user proposed to use different mount options to prevent this from happening but @votdev voted against since OMV itself is prepared for this. Unfortunately this does not apply to each and every OMV add-on as we can see here or on other occassions since this issue pops up every other month...
    • tkaiser wrote:

      FabrizioMaurizio wrote:

      I have a 32gb emmc, why is my system partition only 7.4gb?
      To allow you to use the last partition for data storage as explained at the download page: sourceforge.net/projects/openm…ngle%20Board%20Computers/
      An OMV install is pretty fine with less than 4GB so those 8GB we limit the OS partition too are some sort of safety headroom. If you put your dockers on the OS drive on a SD card be prepared that the card might die pretty soon (flashmemory plugin won't help here at all).
      Not sure I understand how this should be setup. Should I format the remaining emmc storage with mkfs.btrfs /dev/mmcblk0p3 and then install the docker containers into that partition or should I use a different sd card completely (I have an empty sd card slot)?
    • Looks like I have another issue to deal with :( . The nas becomes unreachable some minutes after it has booted. I cannot access the gui nor ssh and from the router's gui it appears like it's disconnected. I though this was caused by the low free space but I guess not. The only way to reach it again is to force a reboot by holding the power button on the board, but shortly after it reboots it becomes unreachable again.
    • You could try to clean the rootfs by removing the SD card and delete (or save) the contents of /sharedfolders folder on the SD car, using some linux computer. Possibly a windows computer, with a SD card reader that you booted from a USB stick with Ubuntu Linux on it.

      Or boot from a SD card and delete the contents of /sharedfolders folder on emmc.
      OMV 4, 7 x ODROID HC2, 1 x ODROID HC1, 5 x 12TB, 1 x 8TB, 1 x 2TB SSHD, 1 x 500GB SSD, GbE, WiFi mesh
    • nevermind, I just did a fresh install. All seams to be working for now.

      edit.

      It looks like it wasn't working after all. It was better than before but not fully fixed. I'm trying a new thing now. I found this post where other users were having the same issue and I checked the system log and I had the same error they had.

      Source Code

      1. Jun 10 00:23:21 rock64 kernel: [ 50.374370] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
      2. Jun 10 00:23:21 rock64 kernel: [ 50.374386] xhci-hcd xhci-hcd.9.auto: @00000000f2cc24b0 00000000 00000000 1b000000 01078001
      So, as they suggested I blacklisted uasp and the error disappeared and so far I haven't had any freezes. Will report back if this changes.

      What I fail to understand is why is this happening. I bought this adapter (3 of them actually) because it has the jms578 which is known to be a good chip. I flashed the latest firmware from odroid and all seemed to be working fine but apparently it wasn't. I also have a usb to dual sata adapter with the jms561u that someone reported working with the rock64. Well it does work but I get the same error as above unless i blacklist uasp (also hdparm can't recognize if a disk is active or in standby).

      Other than the chip and the firmware, what else should one look for when buying this things? @tkaiser @Adoby

      The post was edited 2 times, last by FabrizioMaurizio ().

    • FabrizioMaurizio wrote:

      I found this post where other users were having the same issue and I checked the system log and I had the same error they had
      I got the ERROR Transfer event for disabled endpoint or incorrect stream ring as a result of underpowering: Building OMV automatically for a bunch of different ARM dev boards.

      This is unrelated to your original problem (your disk disappearing from the bus and then some plugin/container filling the rootfs) and also unrelated to other issues and especially UAS. Are the adapters really JMS578 (check lsusb output)? Does the same happen with disks that have an own power brick?
    • The disk "disappearing" was my fault because I accidentally bumped into the cable and it got disconnected while downloading.

      tkaiser wrote:

      I got the ERROR Transfer event for disabled endpoint or incorrect stream ring as a result of underpowering:
      I'm using a dedicated 4A power brick (that should be more than enough power) for the hard drive and the original pine64 3A power brick for the rock64. I get that error every time I boot the system up (but not with uasp blacklisted).
      The issue I'm having is that the nas becomes unreachable when the hard drive is under heavy load (sometimes i mux videos from and into the drive while downloading multiple files at the same time) and I have to force a reboot. What could cause this?


      tkaiser wrote:

      Are the adapters really JMS578 (check lsusb output)?

      They should be the real deal.

      Source Code

      1. root@rock64:~# lsusb
      2. Bus 005 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp.
      3. Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
      4. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      5. Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
      6. Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp.
      7. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      8. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    • FabrizioMaurizio wrote:

      I get that error every time I boot the system up (but not with uasp blacklisted).
      Me too on every RK3328 device (Rock64 and also Renegade). The adapter you're using works the same as the Rock64 SATA cable so the additional '4A' you provide are only there to feed the 12V rail of connected 3.5" disks. As such undervoltage (voltage on the 5V rail provided by the board dropping below 4.xV) might still be the culprit since the USB-to-SATA bridge and the drive's controller need a voltage high enough provided by the SBC. And with some drives even just 4.75 lead to drive resets which manifest themselves (and are confused with) UAS errors.

      The post was edited 1 time, last by tkaiser ().

    • Users Online 4

      4 Guests