Pinned RPi and other SBC/armbian images

    • OMV 5.x (beta)
    • RPi and other SBC/armbian images

      The RPi and SBC/Armbian images on sourceforge have been deleted. Please using the Raspbian Buster Lite or the proper Armbian image and follow the guide here to install OMV - forum.openmediavault.org/index…-Armbian-Supported-SBC-s/
      omv 5.2.3 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.0
      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 ().

    • Dear @ryecoaaron,

      I, as many others were sad to see the development and fights between certain users, which led to the original images being gone from SF.
      Anyway, what this guide for the RPI does not consider is the changes/optimizations that were specifically targeted the RPI images, as given from this now defunct link
      OMV4_for_Raspberries

      Do you have any idea or backup of the things/patches that were done to these images, to make them "better" suited than just default rasbian+OMV install script?
      I recall stuff being implemented like flash2memory etc.

      Thanks
    • mcmanuf wrote:

      I, as many others were sad to see the development and fights between certain users, which led to the original images being gone from SF.
      The images were deleted because they were difficult to support, didn't work well on the RPi4, and used an unsupported Armbian userland with Raspbian kernel. I used to maintain OMV RPi images. So, it isn't that I couldn't create the image. By using the raspbian buster lite image and running a script to install everything, I don't have to maintain an image and users always get the latest OMV. The install script also works on any system as well. Hopefully this yields a much better setup. So, I don't understand why anyone is sad that the images are gone.

      mcmanuf wrote:

      Do you have any idea or backup of the things/patches that were done to these images, to make them "better" suited than just default rasbian+OMV install script?
      That link contained files necessary to adapt the armbian userland to the RPi. They are not needed when using Raspbian Lite. The old armbian-based RPi image basically ran the armbian-config code to install OMV. My install script uses all of the optimizations from that script and more. I actually helped the author with those optimizations and the omv code on how to set them. Please try the script before getting paranoid that the RPi experience will get worse.
      omv 5.2.3 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.0
      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!
    • When I say "sad" this is what I mean:
      As a normal end user, that was the usual way of doing this, ie. last couple of years, by downloading relevant image, plug and play, update system. Thats it.

      I have spend close to 5 hours, trying to understand and read all what has happened in the mean time, as I am about to change from Odroid HC1 to RPI4 - 4GB. And also understanding the install script etc. etc.

      Anyway, thanks for the explanation, which was much needed in between all the FUD going on, and I appreciate your answers, as would many others probably which are in the same "situation".

      By the way
      "Please try the script before getting paranoid that the RPi experience will get worse."
      Name calling is really unnecessary, as I have some valid points in my post, which I have not seen answered anywhere before your reply to me. You yourself have directly said "I dont care about RPI". So when the only maintainer of the RPI images, and who does care, leaves the forums, there is naturally a concern, I would not call that paranoid.
    • mcmanuf wrote:

      As a normal end user, that was the usual way of doing this, ie. last couple of years, by downloading relevant image, plug and play, update system. Thats it.
      Because writing an image and then running one command from the command line is difficult?

      mcmanuf wrote:

      By the way
      "Please try the script before getting paranoid that the RPi experience will get worse."
      Name calling is really unnecessary
      Paranoid is not name calling. It is a state of mind. Sorry if that offended. I just want people to have a little faith that the script will do good things and try it before worrying that everything might be bad.

      mcmanuf wrote:

      You yourself have directly said "I dont care about RPI". So when the only maintainer of the RPI images, and who does care, leaves the forums, there is naturally a concern, I would not call that paranoid.
      Yes, I have said that because it is very difficult and time consuming supporting the typical RPi user. Plus, the image has been terrible on the RPi4 causing even more headaches. I also said I don't care about the RPi mostly before the RPi4 was released.

      And please don't tell me I don't care about something. I dedicate way more time to OMV than just about anyone and definitely more than the previous RPi image maintainer (who hated the RPi as well). Like I said, I maintained the RPi image long before the Armbian image existed. Why would I buy RPis (I have six and many other arm boards), write the script, and do so much testing on the RPi?? I also write plugins and test arm boards I don't use.

      mcmanuf wrote:

      I have spend close to 5 hours, trying to understand and read all what has happened in the mean time, as I am about to change from Odroid HC1 to RPI4 - 4GB. And also understanding the install script etc. etc.
      Why are you changing? The HC1 is a good board. And crashtest wrote the guide around the install script to make it easy to understand. If there is something missing, we can probably add it.
      omv 5.2.3 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.0
      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:

      mcmanuf wrote:

      As a normal end user, that was the usual way of doing this, ie. last couple of years, by downloading relevant image, plug and play, update system. Thats it.
      Because writing an image and then running one command from the command line is difficult?

      [ No not really. More because of all the uncertainties surrounding the new way of installing OMV compared to the old "image way" with OMV baked in. Let me give you some examples:
      - The script suddenly stops working, because of some dependencies, servers down, servers change etc. etc. This has actually already happened some days ago, and you have adjusted the script accordingly. But maybe you were on vacation, or lets say, you dont have time. Then new users will have no way og getting up and running quick, and could wait days or weeks.
      - Additional things that needs to be done, which were previously not needed. Fx docker ethernet setup etc.
      - Due to OMV and Rasbian images gets updated over time things do break. Package incompatibility etc. Or OMV Raspian new way of doing implementing things which breaks others functionality.
      - Something else I have not thought of..

      A suggestion, could be that a snapshot of latest working Rasbian with lateast working OMV5, could be updated every, lets say every 6~9 months, and put on SF. So there will always be something "offline" to get up and running, but this should not be the main source of installing OMV5, only backup solution. So there is always a backup, when someone suggests the rasbian + script way does not work for whatever reason -> have you tried the offline image, could be the first question.
      Anyway, I will try to make this image for myself, so I at least have an working offline backup if ever needed for any reason. This backup will be barebone+all rasbian+OMV5 updates as of date ]

      mcmanuf wrote:

      By the way
      "Please try the script before getting paranoid that the RPi experience will get worse."
      Name calling is really unnecessary
      Paranoid is not name calling. It is a state of mind. Sorry if that offended. I just want people to have a little faith that the script will do good things and try it before worrying that everything might be bad.

      [ I saw it as a offence to a relevant concern I had. Anyway apology accepted and appreciated :thumbup: ]


      mcmanuf wrote:

      You yourself have directly said "I dont care about RPI". So when the only maintainer of the RPI images, and who does care, leaves the forums, there is naturally a concern, I would not call that paranoid.
      Yes, I have said that because it is very difficult and time consuming supporting the typical RPi user. Plus, the image has been terrible on the RPi4 causing even more headaches. I also said I don't care about the RPi mostly before the RPi4 was released.
      And please don't tell me I don't care about something. I dedicate way more time to OMV than just about anyone and definitely more than the previous RPi image maintainer (who hated the RPi as well). Like I said, I maintained the RPi image long before the Armbian image existed. Why would I buy RPis (I have six and many other arm boards), write the script, and do so much testing on the RPi?? I also write plugins and test arm boards I don't use.

      [ I was not putting any opinions in your shoes. Again as a layman, I was expressing my concerns, as I love Openmediavault, and was afraid RPI users would be left alone after the recent spat, and your previous comment about RPI, albeit I now understand that was before RPI4 days. As your are the main driver for OMV, off course your huge effort is well appreciated and revered, and should be by all users and moderators :thumbup: ]


      mcmanuf wrote:

      I have spend close to 5 hours, trying to understand and read all what has happened in the mean time, as I am about to change from Odroid HC1 to RPI4 - 4GB. And also understanding the install script etc. etc.
      Why are you changing? The HC1 is a good board. And crashtest wrote the guide around the install script to make it easy to understand. If there is something missing, we can probably add it.

      [ I have actually been very happy with my Odroid HC1 the last 1,5year or so, and if it had one simple design change, it would still have been perfect.
      1) The usb2 external port would have been perfect if it was a usb3 port. Then I could have installed a usb3 hub, and attach multiple hdd, with USB3 interface, and enjoy the higher speeds. Now I am limited to only 1x harddisk with usb3 speeds. So now the board have the 2x usb3 interfaces being reserved to the gigabit and the internal sata port. So all attached hdd's are limited to usb2 speeds, on the external usb2 port.
      2) Whereas not as big a problem 1), the 2GB ram might be a issue for me, I am not sure. I have around 5 docker containers running, and it seems that I use around ~500MB SWAP (according to HTOP). However I have not been able to decipher if the swap is using the SD card or not (thereby reducing lifetime), or if its ZRAM or something else entirely, RAM management in linux is a bit complex for me to understand. Also I am not understanding if I am using the whole 2GB ram currently, as the bar in HTOP are 45% green, approx 10% blue, and approx 45% yellow. But it is completely filled with colors.

      Again your effort is extremely appreciated, and hope I have been able to shed some light as a "normal" SBC user enjoying OMV. Not as a person opposing change. I believe this thread will serve well for people like me, who returns to the forums after have being away for some time, to see changes have been done in the meantime :thumbup: ]




    • mcmanuf wrote:

      So when the only maintainer of the RPI images, and who does care, leaves the forums, there is naturally a concern, I would not call that paranoid.
      The notion that the previous maintainer cared about the R-PI is amusing. If fact, he was infamous for belittling users for simply buying an R-PI when they posted problems on the forum. His serial rants on the R-PI's "propriety hardware", what a piece of crap it was, etc., etc., are the stuff of infamy. Any long time forum contributor knows this. 'Nuff said on that.
      ________________________________________________

      From the support perspective, the image and script approach is far better than using pre-built images. Setting aside the obvious benefit of having a fully up-to-date installation at the end of the script:
      A very large part of this forums support is answering SBC questions, yet, because of past plug and play images, most users didn't know how to get on the command line and never bother to learn. There's no reason to until, of course, something goes wrong. At that point, when forum contributors ask basic questions or pass instructs on how to proceed, most users have no idea of what to do. And this comes at the worst possible time, when there's a problem.

      The scripted approach exposes users to utilities needed for server maintenance like using an SSH client, along with getting on the command line and executing commands. The installation is the opportune time to teach these basic topics in that users are *motivated* to get a server up and running. The net result is a more educated user that is familiar with basic concepts and, with a bit of success from reading a document under their belt, they may be willing to read a bit more.

      This is a good thing for all concerned.
    • mcmanuf wrote:

      Let me give you some examples:
      - The script suddenly stops working, because of some dependencies, servers down, servers change etc. etc. This has actually already happened some days ago, and you have adjusted the script accordingly. But maybe you were on vacation, or lets say, you dont have time. Then new users will have no way og getting up and running quick, and could wait days or weeks.
      - Additional things that needs to be done, which were previously not needed. Fx docker ethernet setup etc.
      - Due to OMV and Rasbian images gets updated over time things do break. Package incompatibility etc. Or OMV Raspian new way of doing implementing things which breaks others functionality.
      - Something else I have not thought of..
      Valid points but the old image was vulnerable as well. One of things it did in the 30 mins you had to wait on first startup was fully update the system. Any package changes (debian, armbian, omv, etc) could have broken things as well.

      I am working on the docker ethernet issue.

      And I should be able keep up with OMV and raspbian updates. Having people download the script from github allows me to make tweaks/changes/fixes and people get them right away.

      If I created an image, no one would use the script and people would want images for all of the popular ARM boards putting me right back in the same place of having to build and maintain images.
      omv 5.2.3 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.0
      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!

      Post by gregwa ().

      This post was deleted by ryecoaaron: dupe ().