Recommended Image for Odroid-HC2

Zitat von Caseyinka

Embarrassing i didn't find this thread myself

I'm trying to improve "search" in the forum. Currently user experience is not the best :(.

Would you be interested to act as a tester? in case yes please respond via private conversation

I am trying to get OMV5 running on an odroid-hc2. The only image I have got to work is one specifically for the hc1 or hc2. This image is OMV4 that seems to work fine. I have tried upgrading it to OMV5 several times, based on the behavior I think that it reverts to needing interaction on the terminal. The device still has the blue heartbeat led is on.

The other more general xu4 images never start the web controls. I suspect that these are looking for the initial terminal interaction.

I would like to find an OMV5 image that just works with the hc1, or hc2.

Alternatively is there a way I can configure an image on a vm to get past any of the start up problems and then create an image for the physical machine.

The image that worked downloaded with the name "OMV_4_Odroid_XU4_HC1_HC2.img.xz". This version I was not able to successfully update to OMV5.

After reading some of the other posts I retried the image named "Armbian_21.05.1_Odroidxu4_buster_legacy_4.14.222.img.xz". As I indicated in the first part of my post the web interface would not come up (I did try clearing the browser cache). The thing I forget to note that the ssh client recognizes that there is something there, but will not authenticate (used the default password).

Honestly I am not sure what kind of advice I am after. Maybe I am following the wrong instructions for the upgrades. Maybe there is a way to get into a start image that I don't know about.

Hi there.

Maybe someone could help with something that is confusing me:

I have an Odroid HC2.

I installed OMV 5 on it from here:

openmediavault - Browse Files at SourceForge.net

However, the above also suggests that there is another method - i.e. install Armbian, instead, and then install OMV on top.

I am slightly confused - is the versions that I am using not already Armbian with OMV on top?

SourceForge is not up-to-date for ARM images!

In the the post above your question, the answer was provided already

Thank you - must have been so long since I last installed OMV that I had not realised that there had been a change.

Out of interest, is there any difference between the previous method and the new one?

Am I correct in thinking that the Sourceforge version of the HC2 image was Debian that was adapted for SBC devices, whereas the new method uses Armbian, which is superior (because it has been specifically developed for SBC devices)?

I am considering reinstalling, using the new method, but will not bother if they are identical.

Thanks very much for this.

One of the reasons I was asking is, as per this thread

Problems with TVHeadend update - General - openmediavault

I am running a similar setup to another user but am having upgrading TVHeadend like they are doing.

I was wondering whether the different method of installing OMV was the cause but seems not.