Beiträge von Tinkerisk

Zitat von Komet

So the “amd64” and “i386” part of the file names has nothing to do with what hardware it should used on?

openmediavault_4.1.3-amd64.iso

openmediavault_3.0.36-i386.iso

It has, amd64 is for 64-Bit processors (from Intel OR from AMD). Assuming you are using the core i7 processor in your signature, the amd64 is the right version.

IF IT DOESN'T WORK: Another way to do your installtion could be to install latest 3.0xx first (amd64) and upgrade to 4.1.x from there (this worked flawless in my case).

1) Install OMV 3.0.xx as you could find in the manual above
2) Login to CLI, user: root, pwd: as entered before (use puTTY)
3) apt-get update
4) apt-get upgrade
5) omv-release-upgrade
6) omv-initsystem (this is only for NEW installations since a pop-up window from OMV 3.0.xx requested it before maybe because I had not yet attached the data drives)

Restart your System and Login via WebGui

Zitat von Komet

Looking back at the downloads page is the newest version of Openmediavault for Intel 3.0.36 from Sept 2016?

Latest release for download is 4.1.3 from 30.3.2018 and amd64 is correct. You might end with 4.1.4 after successful install and update via OMV WebGui.

If you don't know how to install: Getting Started with Openmediavault

Zitat von ryecoaaron

Why the link to omv-initsystem? I know it should be done on a new install.

Because it worked (and didn't break anything at least on my install). The normal procedure didn't work, so I suceeded that way.

http://openmediavault.readthed…?highlight=omv-initsystem

Zitat von ryecoaaron

You shouldn't have to do the initsystem part on an upgrade. I never do.

Right, maybe better not to do with a system in production. Therefore I added the note.

What I did ...

> update the list of available packages and their versions
apt-get update

> install newer versions of the packages already available
apt-get upgrade

... and now ...

> install OMV 4.0
omv-release-upgrade

> intitialize OMV
omv-initsystem

Here we go.

NOTE: This was an immediate installation of OMV 3.xx and direct upgrade to 4.0 since the normal procedure for 4.0 didn't work flawless. So be aware to disable all plug-ins before like mentioned by others before.

Zitat von TOMillr

Thanks, going to give that a try. But what happens when I try to permanently install OMV? Do I still need the usb stick to boot from?
I've come across a blog post about booting Ubuntu on a basically identical Apollo-Lake-based mini-pc. Apparently booting linux only works on those devices, when using the rEFInd Boot Manager.

Is there a way to manually included the rEFInd boot manager with the OMV or Debian iso so that I can boot the install medium, clean swipe Windows 10 of the HDD and get OMV to boot from the eMMC storage?

I'm not familiar with that h/w and the UEFI of it. For OMV, you need to have a boot drive and the (or one) data drive/s. What you could do is, to add 2x USB3.0/SATA drives to the connectors having the data storage (maybe with s/w RAID1 let's say). The internal 64GB could be (not sure if possible) the system boot disk (if you're willing to waste by far the most of the 64GB for the OS). Keep the data drives away for the first time. What you need in that case is only one USB-Stick for installation (assuming, you can address the eMMC like any other drive).

First try could be: (it shouldn't erase anything on your System)

- Setup your UEFI to boot from USB first
- Prepare USB stick (FAT32) with the UNetBootIn (simulates a boot media with the downloaded OMV iso)
- Format a thumb drive (ext4) as the future boot media (to keep on one USB3.0 connector)
- Plug in both sticks, power on, installation sequence should start
- Select the USB thumb drive as the system drive during install
- when finished, shut down, remove USB stick (not the thumb drive) and power on
- if everything went right, you should be capable to browse to the OMVs web interface.
- Shut down, connect data drives, re-power and include them to the OMV environment (Mount, Format, ...)

Another possible way could be: (you'll loose any data on the eMMC if it can be addressed, see comment below)

- Setup your UEFI to boot order 1) USB stick, 2) eMMC
- Prepare USB stick (FAT32) with UNetBootIn (simulates a boot media with the downloaded OMV iso)
- Plug in the USB stick, power on, installation sequence should start
- Select the eMMC as the system drive during install (eMMC might be formatted before to ext4 with a live boot Linux formatter like GParted live)
- when finished, shut down, remove USB stick and power on
- if everything worked well, you should be capable to browse to the relevant IP to start the web interface of OMV.
- Shut down, connect data drives, re-power and include them to the OMV environment.

Please be aware, that is only assumed how it could be established since I don't know your h/w in detail.

If it works well, please let us know.

Alles anzeigen

Try UNetBootIn for OMV 3.0.94 instead of etcher. You'll need 2 sticks, one temporarily for installation itself and to keep as the OMV boot media.

Using the "old" Docker one worked for me.