[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


    checked message log





    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 5.5.2 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.3
    omv-extras.org plugins source code and issue tracker - github


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

  • /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

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



    tough this time the webinterface is not starting.


    dmesg | grep error shows:


    Code
    [..] 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
    [..] 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.

  • 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.

Participate now!

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