[OMV3.0.41 on Rpi] disk space issues at first run

    • OMV 3.x

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

    • [OMV3.0.41 on Rpi] disk space issues at first run

      This is my first installation attempt of OMV 3.0.41 on a Raspberry Pi 2 with 8Gb uSD card.

      Installed the image with Win32DiskImager
      Booted the RPi
      Able to get into the web interface but ran into some errors:
      • check updates gave: " Failed to read file '/tmp/bgstatusk2k7e8' (size=0)."
      • change time zone, able to save but no commit banner
      • change NTP server, able to save but no commit banner.
      So I went to CLI and ran DF -h

      Source Code

      1. Filesystem Size Used Avail Use% Mounted on
      2. /dev/root 3.2G 3.2G 0 100% /
      3. devtmpfs 483M 0 483M 0% /dev
      4. tmpfs 487M 0 487M 0% /dev/shm
      5. tmpfs 487M 6.8M 480M 2% /run
      6. tmpfs 5.0M 0 5.0M 0% /run/lock
      7. tmpfs 487M 0 487M 0% /sys/fs/cgroup
      8. /dev/mmcblk0p1 56M 21M 36M 38% /boot
      9. folder2ram 487M 744K 486M 1% /var/log
      10. folder2ram 487M 0 487M 0% /var/tmp
      11. folder2ram 487M 0 487M 0% /var/lib/openmediavault/rrd
      12. folder2ram 487M 696K 486M 1% /var/spool
      13. folder2ram 487M 4.0K 487M 1% /var/lib/monit
      14. folder2ram 487M 4.0K 487M 1% /var/lib/php5
      15. /dev/mmcblk0p3 4.1G 3.1M 3.9G 1% /media/fa36508a-b3c4-4499-b30a-711dd599422f
      Display All

      checked message log



      Shell-Script

      1. [ 8.273758] systemd[1]: Starting udev Write the /dev/root link rules...
      2. [ 8.336710] systemd[1]: Starting LSB: MD array assembly...
      3. [ 8.362231] systemd[1]: Starting LSB: Set preliminary keymap...
      4. [ 8.388309] systemd[1]: Starting LSB: Tune IDE hard disks...
      5. [ 8.439893] systemd[1]: Started udev Write the /dev/root link rules.
      6. [ 8.575327] systemd[1]: Started LSB: Tune IDE hard disks.
      7. [ 8.597638] mmcblk0: r/w command failed, status = 0x80000900
      8. [ 29.975419] systemd[1]: Failed to start LSB: Keeps folders in RAM.
      9. [ 327.264184] EXT4-fs error (device mmcblk0p2): htree_dirblock_to_tree:986: inode #5595: block 9098: comm apt-get: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=0, name_len=0
      10. [ 327.292706] EXT4-fs error (device mmcblk0p2): ext4_find_dest_de:1808: inode #20: block 8267: comm apt-get: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=0, name_len=0
      11. [ 328.082806] EXT4-fs error (device mmcblk0p2): htree_dirblock_to_tree:986: inode #1194: block 8514: comm tar: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=0, name_len=0
      12. [ 328.255627] EXT4-fs error (device mmcblk0p2): htree_dirblock_to_tree:986: inode #1363: block 8535: comm logrotate: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=0, name_len=0
      13. [ 329.333171] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:758: group 4, block bitmap and bg descriptor inconsistent: 32768 vs 343 free clusters
      14. [ 329.347540] JBD2: Spotted dirty metadata buffer (dev = mmcblk0p2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
      15. [ 330.018419] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:758: group 5, block bitmap and bg descriptor inconsistent: 32768 vs 226 free clusters
      16. [ 330.034702] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:758: group 8, block bitmap and bg descriptor inconsistent: 32768 vs 224 free clusters
      17. [ 330.049960] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:758: group 9, block bitmap and bg descriptor inconsistent: 32768 vs 172 free clusters
      18. [ 330.067156] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:758: group 12, block bitmap and bg descriptor inconsistent: 32768 vs 151 free clusters
      19. [ 330.089374] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:758: group 13, block bitmap and bg descriptor inconsistent: 32768 vs 42 free clusters
      20. [ 330.113812] JBD2: Spotted dirty metadata buffer (dev = mmcblk0p2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
      Display All

      So i seem to have some diskspace errors. The SD card has been used for testing other RPi images before, no issues detected yet. I always do low level formatting before burning the image.

      Any advice?
    • I think I forgot to delete the zeroing file. What is the output of: ls -alh /

      I will fix the image later.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • omv_trblz wrote:

      /dev/mmcblk0p3 4.1G 3.1M 3.9G 1% /media/fa36508a-b3c4-4499-b30a-711dd599422f
      The media partition is a problem that already has 4.1G
      forum-bpi.de Visit on and help us, The Germany Forum :thumbsup:
      github.com/Wolf2000Pi
      Banana Pi /Armbian 3.4.109 / Openmediavault 2.x
      Banana Pi /Armbian 4.11.5-sunxi / Openmediavault 3.0.xx (Test)
      Dell Inspiron One 2205 | Openmediavault 3.0.xx / Kernel 4.7 (Test)
    • omv_trblz wrote:

      it contains a 1.6Gb zero.dd file - should i delete it?
      Yep. New image won't have it. Uploading new image now.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!

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

    • Thanks - i installed the revised image and no more diskspace issues.

      Source Code

      1. root@raspberrypi:~# df
      2. Filesystem 1K-blocks Used Available Use% Mounted on
      3. /dev/root 3332796 1656484 1509868 53% /
      4. devtmpfs 493896 0 493896 0% /dev
      5. tmpfs 498228 0 498228 0% /dev/shm
      6. tmpfs 498228 6916 491312 2% /run
      7. tmpfs 5120 0 5120 0% /run/lock
      8. tmpfs 498228 0 498228 0% /sys/fs/cgroup
      9. /dev/mmcblk0p1 57288 21216 36072 38% /boot
      10. folder2ram 498228 476 497752 1% /var/log
      11. folder2ram 498228 0 498228 0% /var/tmp
      12. folder2ram 498228 0 498228 0% /var/lib/openmediavault/rrd
      13. folder2ram 498228 700 497528 1% /var/spool
      14. folder2ram 498228 8 498220 1% /var/lib/monit
      15. folder2ram 498228 8 498220 1% /var/lib/php5
      16. /dev/mmcblk0p3 4209389 3133 3984665 1% /media/fa36508a-b3c4-4499-b30a-711dd5994225
      17. tmpfs 99648 0 99648 0% /run/user/0
      Display All

      tough this time the webinterface is not starting.

      dmesg | grep error shows:

      Source Code

      1. [..] EXT4-fs error (device mmcblk0p2): ext4_find_dest_de:1808: inode #20: block 8267: comm apt-get: bad entry in directory: rec_len is smal ler than minimal - offset=0(0), inode=0, rec_len=0, name_len=0
      2. [..] EXT4-fs error (device mmcblk0p2): htree_dirblock_to_tree:986: inode #1194: block 8514: comm tar: bad entry in directory: rec_len is sm aller than minimal - offset=0(0), inode=0, rec_len=0, name_len=0
      top is not working either. /usr/share/terminfo is empty
    • I had a chance to try the new image (3.0.41) today, looks to work ok so far. Still getting things set up but no major issues yet.

      Getting wifi to work on boot is fixed and I've got the problematic power management to turn off during the boot sequence using rc.local.

      @ryecoaaron thank you very much for your help getting me started.
      omv 3.0.53 | RPi3 | 2 x 2TB WDRed | Startech Enclosure S3510BMU33B | Weekly Rsync
    • Update on this, system seems to be up and running (still with a few niggles) but I've completely given up on wifi. I suspect that this is an RPi3 issue and not OMV. I'd constantly get network connections dropping meaning I couldn't ssh in to troubleshoot. Without a connected screen I had to blindly use a keyboard to reboot. Since moving to a wired connection I've not had any network issues.
      omv 3.0.53 | RPi3 | 2 x 2TB WDRed | Startech Enclosure S3510BMU33B | Weekly Rsync