New approach for Raspberry Pi OMV images

    • mcgyver83 wrote:

      Why you say "ARMv6 Raspbian vs. ARMv7 'original' Debian now"? Rpi2 has an ARMv7 cpu, now I'm running OMV3 on a rpi2 so you are saying that below the line "my OMV" is running using Raspbian ARMv6 version?
      All Raspbian packages are built for ARMv6 (that's the whole reason Raspbian exists since back in 2012 upstream Debian already stopped supporting older architectures than ARMv7 so RPi folks had to build an own repo and rebuild all packages to be able to provide a Debian for the old single core ARMv6 Raspberries). The older OMV images for RPi (prior to mid July) relied on Raspbian so regardless which CPU type you use (RPi 3 and RPi 2B V1.1 use even 64-bit ARMv8 CPU cores) with Raspbian you always end up with code 'optimized' for ARMv6.

      Some stuff (eg. the stupid sysbench pseudo benchmark) could benefit a lot when built optimized for ARMv8 but with this use case here (NAS, that means IO and network bound) the differences are negligible (the RPi folks chose pretty good compiler flags so sometimes or even often a Raspbian ARMv6 binary can run faster than one built for Debian Jessie ARMv7)

      mcgyver83 wrote:

      At the end there isn't a way to keep configurations and apply them to a fresh "OMV for RPI" image?
      AFAIK not.
    • tkaiser wrote:

      mcgyver83 wrote:

      Why you say "ARMv6 Raspbian vs. ARMv7 'original' Debian now"? Rpi2 has an ARMv7 cpu, now I'm running OMV3 on a rpi2 so you are saying that below the line "my OMV" is running using Raspbian ARMv6 version?
      All Raspbian packages are built for ARMv6 (that's the whole reason Raspbian exists since back in 2012 upstream Debian already stopped supporting older architectures than ARMv7 so RPi folks had to build an own repo and rebuild all packages to be able to provide a Debian for the old single core ARMv6 Raspberries). The older OMV images for RPi (prior to mid July) relied on Raspbian so regardless which CPU type you use (RPi 3 and RPi 2B V1.1 use even 64-bit ARMv8 CPU cores) with Raspbian you always end up with code 'optimized' for ARMv6.
      Some stuff (eg. the stupid sysbench pseudo benchmark) could benefit a lot when built optimized for ARMv8 but with this use case here (NAS, that means IO and network bound) the differences are negligible (the RPi folks chose pretty good compiler flags so sometimes or even often a Raspbian ARMv6 binary can run faster than one built for Debian Jessie ARMv7)

      mcgyver83 wrote:

      At the end there isn't a way to keep configurations and apply them to a fresh "OMV for RPI" image?
      AFAIK not.
      Ok thanks.
      So starting from scratch with OMV images from the first page (like this one) should be better to run OMV with rpi2, at last to have "healt" information.
      Using these new images also gain ARMv7 packages instead of "ARMv6 running over ARMv7 architecture", isn't it?
    • kuleen wrote:

      thanks tkaiser. I will re image the card and start over, this time with patience :). Will let you know the outcome.
      Today I tried with patience of over 20 mins and omv3 got properly setup on RPI3 model b. As you said it is not a good NAS solution (and I agree with you) but it is working good as media server with Plex plugin. I am able to stream 1080p videos through it. Thanks for your help to wait for atleast 20 mins for initial setup.

      sudo raspimon now gives me following output (yay) :
      Time Temp CPU fake/real Health state Vcore
      02:50:22: 72.0'C 1200/1200 MHz 0000000000000000000 1.2625V
      02:50:27: 72.0'C 1200/1200 MHz 0000000000000000000 1.2625V
      02:50:32: 72.0'C 1200/1200 MHz 0000000000000000000 1.2625V
      02:50:38: 72.0'C 1200/1200 MHz 0000000000000000000 1.2625V
      02:50:43: 72.0'C 1200/1200 MHz 0000000000000000000 1.2625V
      02:50:48: 72.0'C 1200/1200 MHz 0000000000000000000 1.2625V
      02:50:53: 73.1'C 1200/1200 MHz 0000000000000000000 1.2625V
      02:50:58: 70.9'C 1200/1200 MHz 0000000000000000000 1.2625V
      02:51:03: 72.0'C 1200/1200 MHz 0000000000000000000 1.2625V
      02:51:08: 72.5'C 1200/1200 MHz 0000000000000000000 1.2625V
    • kuleen wrote:

      02:50:53: 73.1'C 1200/1200 MHz 0000000000000000000 1.2625V
      For the RPi being idle the temperature is way too high and in case the board is pretty active (then temperature could be reasonable) the voltage the CPU cores are fed with is too low (with a good Micro USB cable you should see +1.3V on an RPi 3 under load)
    • lex wrote:

      do i have any advantage / disadvantage switch to your Arabian image when it comes to performance?
      Maybe a little since the packages are compiled for the right cpu. I doubt you would notice any difference though.

      lex wrote:

      can I upgrade my old OMV3 raspian installation to OMV4 someday?
      Raspbian would need a stretch version. No idea if they do yet or not. That would probably be a good reason to switch to the armbian based image.
      omv 4.1.11 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      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!
    • ryecoaaron wrote:

      Maybe a little since the packages are compiled for the right cpu. I doubt you would notice any difference though.
      There are differences especially when not running synthetic benchmarks (real-world applications). But that's not due to ARMv6 vs. ARMv7 compiler settings (in fact Raspbian guys did a really good job to optimize their ARMv6 builds as much as possible, I checked several binaries already where Raspbian binary is faster than Debian armhf counterpart) but due to the more important stuff like cpufreq governor tuning and IO scheduler and priority settings.

      Not directly comparable but that's the old Rasbian based OMV image for Raspberries tested with a pretty fast SSD:
      [IMG:http://kaiser-edv.de/tmp/lGtv38/Bildschirmfoto%202017-04-04%20um%2011.30.12.png]
      And these are comparison numbers of DietPi (Raspbian based) and the new image made with a 2.5" HDD: New approach for Raspberry Pi OMV images

      HDD vs SSD strangely makes a difference since different bottlenecks add up so the new image combined with the same SSD as in the first test above will show superiour or equal numbers in every area. But that doesn't matter that much since Raspberries are too slow anyway (and if people look only at backup times, then good luck for them when they realize that restore times are important, do the math yourself how long it takes to pull 500GB off an Raspberry Pi at lousy speeds around 5MB/s compared to 50MB/s with a good ARM board, that's few hours vs. a whole day).

      Current Raspbian is based on Stretch already so maybe the usual way upgrading to OMV4 works. It's easy to test (with a cloned SD card before) so I really wonder why affected users ask questions instead of providing insights :)
    • I tried the OMV_3_0_88_RaspberryPi_2_3_4.9.41.img.xz image on a 16 GB microSD card.
      Once the gui was usable I started configuring OMV.
      With standard images I had out of the box the "boot" partition and also a partition with home folder for users.
      Now with the "image for rpi" I have no "device" to be chosen when I create my first user and I have to create the user without home folder.
      How can I setup this "data" partition?

      I try to explain this in a different way: with the standard image in webGui there you can create shared folder (as example) using a "device" that is the EXT4 microSd partition.
      Now I have not "drive" in shared folder webGui but via ssh / is 8GB (not exactly 8).
      I installed raspi-config to expand it (I'm using 16GB card) but it says "mmcblk0p2 is not the last partition. Don't know how to expand".

      Why?

      I miss also "standard" user home files, like .profile, .bashrc and so on

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

    • @mcgyver83 - If you read the very first post in this thread I think you will find the answer. In summary, the root partition is resized to 7.3GB and the remaining space on SD card is filled by another partition that just needs to be formatted/initialised.

      • The image resizes the rootfs automagically to ~7.3GB on first boot and creates a 3rd partition using the remaining space of the SD card you need to initialize manually if you want to use it for OMV shares ('mkfs.ext4|mkfs.btrfs /dev/mmcblk0p3')
    • Ok, sorry, I miss it..
      But how can I initialize it without removing microSD? From webGui I cannot create new filesystem, no devices appear in dropdown list.
      Is it possible to expand root partition to use the entire free space?
      And last: is it possible to enable home folder for users? In the webGui page I haven't any device in dropdown list

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

    • 1. to initialise the filesystem you need to do this from the CLI (e.g. putty on windows or terminal on mac) over a SSH connection - unless you have the device connected to a monitor via HDMI. The command to create the new partition as ext4:

      sudo mkfs.ext4 /dev/mmcblk0p3

      2. Expanding the size of the root partition is possible but tricky/risky. If you are not familiar with linux and CLI, I would not recommend.

      3. I'm sure it is easy to setup users with home folder but i wouldn't use the SD as the home folder. Other folks on this forum will be better at explaining how to do this. I would search the forum and then post a new question about setting up users with home folders...

      Good luck!

      Update: I see you have a RPi and have used raspi-config to try to expand the root partition. The reason it is not working is that there is an unformatted partition that you need to delete (from CLI) first. If you really want to delete the 3rd partition and expand then use the fdisk command. be careful!!!
    • mcgyver83 wrote:

      just a question? Why the out of the box system has a root partition and another one not initialized instead of having the full microSD used by root partition?
      Because some people wanted to use the unused space for data that could use in the omv web interface. People not running plex on their RPi will probably never use more than 2 GB on the SD card.

      mcgyver83 wrote:

      Why isn't recommended to use microSD as home folder?
      It isn't possible to set that from the omv web interface. If you are using the SD card for data, using it for the home folder really isn't any different.
      omv 4.1.11 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      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!
    • Hi,
      after a couple of week of usage mny omv with rpi2 runs fine.

      After enabling email monitoring I receive this mail each day:
      run-parts: /etc/cron.daily/monitor-raspi-health exited with return code 1This is my /var/log folder files list

      Source Code

      1. -rw-r--r-- 1 root root 26K Oct 29 11:18 alternatives.log
      2. drwxr-xr-x 2 root root 80 Jun 12 14:29 apt
      3. -rw-r--r-- 1 root root 34K Nov 5 15:17 armhwinfo.log
      4. -rw-r----- 1 root adm 688K Nov 6 10:35 auth.log
      5. -rw-r--r-- 1 root root 58K Jun 12 14:28 bootstrap.log
      6. -rw------- 1 root utmp 7.2K Oct 28 22:24 btmp
      7. drwxr-xr-x 2 root root 80 Oct 30 07:47 cron-apt
      8. -rw-r----- 1 root adm 4.9M Nov 6 10:34 daemon.log
      9. -rw-r----- 1 root adm 31K Nov 6 10:30 debug
      10. -rw-r----- 1 root adm 31 Jun 12 14:25 dmesg
      11. -rw-r--r-- 1 root root 589K Nov 6 09:44 dpkg.log
      12. -rw-r--r-- 1 root root 24K Oct 29 18:17 faillog
      13. -rw-r--r-- 1 root root 760 Jun 12 15:43 fontconfig.log
      14. drwxr-xr-x 2 root root 80 Jun 12 14:25 fsck
      15. drwxr-xr-x 2 root root 40 Oct 29 14:27 jdownloader
      16. -rw-r----- 1 root adm 4.9M Nov 6 05:07 kern.log
      17. -rw-rw-r-- 1 root utmp 287K Nov 6 10:34 lastlog
      18. drwx------ 2 root root 200 Nov 6 00:19 letsencrypt
      19. -rw-r----- 1 root adm 227 Nov 5 20:17 mail.err
      20. -rw-r----- 1 root adm 8.0K Nov 6 08:18 mail.info
      21. -rw-r----- 1 root adm 8.0K Nov 6 08:18 mail.log
      22. -rw-r----- 1 root adm 468 Nov 5 20:17 mail.warn
      23. -rw-r----- 1 root adm 3.0M Nov 6 08:18 messages
      24. -rw-r--r-- 1 minidlna minidlna 36K Nov 6 04:29 minidlna.log
      25. -rw-r----- 1 root adm 0 Jun 12 15:44 monit.log
      26. -rw-r--r-- 1 root root 0 Oct 31 07:43 netatalk.log
      27. drwxr-xr-x 2 root adm 180 Oct 30 07:47 nginx
      28. drwxr-xr-x 2 ntp ntp 40 Jul 22 2016 ntpstats
      29. drwxr-xr-x 2 root root 60 Oct 28 18:54 openmediavault
      30. -rw------- 1 root root 435 Nov 5 15:17 php5-fpm.log
      31. drwxr-xr-x 2 root root 120 Oct 30 07:47 proftpd
      32. -rw-r--r-- 1 root root 641 Oct 31 12:32 raspihealth.log
      33. -rw-r----- 1 root adm 61K Nov 6 00:56 rsync.log
      34. drwxr-x--- 3 root adm 200 Oct 30 07:47 samba
      35. -rw-r----- 1 root adm 97K Nov 6 10:35 syslog
      36. drwxr-xr-x 2 root root 40 Sep 27 2014 sysstat
      37. -rw-r--r-- 1 root root 63K Nov 6 09:42 tallylog
      38. drwxr-x--- 2 root adm 100 Oct 31 07:42 unattended-upgrades
      39. -rw-r----- 1 root adm 7.3K Nov 6 08:18 user.log
      40. -rw-r----- 1 root adm 34K Oct 29 18:02 wakealarm.log
      41. drwxr-xr-x 2 root root 40 Dec 4 2014 watchdog
      42. -rw-rw-r-- 1 root utmp 57K Nov 6 10:34 wtmp
      Display All
      Some files have owner group root,others admm, others utmp... is it right?
    • mcgyver83 wrote:

      run-parts: /etc/cron.daily/monitor-raspi-health exited with return code 1
      Seems you're not using latest image? Can you please compare raw.githubusercontent.com/Thom…aily/monitor-raspi-health with /etc/cron.daily/monitor-raspi-health in your installation? The problem has been reported ages ago and should be fixed (adding last line with 'exit 0').
    • tkaiser wrote:

      Seems you're not using latest image? Can you please compare raw.githubusercontent.com/Thom…aily/monitor-raspi-health with /etc/cron.daily/monitor-raspi-health in your installation? The problem has been reported ages ago and should be fixed (adding last line with 'exit 0').
      If I check the current image here : sourceforge.net/projects/openm…/Raspberry%20Pi%20images/
      OMV_3_0_88_RaspberryPi_2_3_4.9.41.img.xz


      There is not "exit 0" at the end of this file. That's why I got this same problem when I've reset my sdcard with this image (and now it's in production). Is there another location where to find a RPi image ? When we click on Download link from the OMV website, it's going to this link...? This is why I'm sometimes lost about the "latest image" :p

      Is there something else to check we are using a good image ? ARMbian instead of Raspbian based image ?

      Thx for not bashing the noobs ;) :p
    • @tkaiser - I have a rock64 on the way (in transit from China). I was hoping you could give some advice in terms of of a stable image/build to use with it. I have seen ayufan-rock64 stuff on GitHub and I see that there is a release with OMV installed. Is this a good starting point?

      Also interested to know if/when rock64 will be supported by armbian so that you (hopefully) can do one of your OMV images.

      Any thoughts/suggestions to get me started would be appreciated!

      PS looking forward to smashing (with hammer) my Bananapi M2U :)
    • jata1 wrote:

      I was hoping you could give some advice in terms of of a stable image/build to use with it
      Why again off-topic here since I already answered it where it belongs to: forum.openmediavault.org/index.php/Thread/20301 (I moved your last request over there to. Use ayufan's image for now, we took care that it exactly behaves the same from an 'OMV support' point of view -- even armbianmonitor -m / -u works there. No idea when Armbian images will be ready, waiting for feedback from other devs)
    • Users Online 4

      4 Guests