Installing OMV6 on Armbian Bullseye

OMV6 is a legacy version of Openmediavault. While it is still possible to build OMV6, it is recommended that users build the latest version, → OMV7.

Due to the lack of the numerous Single Board Computers (SBC's) required for testing and integration, providing images for all Armbian supported SBC's, with Openmediavault (OMV) pre-installed, will not be possible. However, installing OMV6 on Armbian supported SBC's is a relatively easy task. This document is a guide for that purpose.

The purpose and intent of this guide is to provide a walk-through to get SBC users up and running as quickly and as easily as possible. This guide assumes that users have a working Windows Client for installing and executing the needed utilities. It is also assumed that Mac and Linux desktop users will be able to find, install, and use utilities equivalent to those called out in Prerequisites.

  • This guide contains links to external sources of information and software. It's best used on an Internet connected PC.
  • This is a community document and a work in progress. Input and feedback are welcome and can be sent to:

Desktop versions of Armbian

Armbian desktop versions are not supported and are used at the user's risk. If a desktop is used, SD-card backup is recommended.

OMV6 will install on most SBC devices with Armbian support and a Debian Bullseye image.

A list of images, for your particular SBC can be found in the → Armbian Archive. Find your SBC on the archive page, select it and drill down to the images page. Scroll to the bottom of the images page, looking for the latest, small, Bullseye image. (Typically the smaller sized image files are “CLI” or “Minimal”. This may be difficult to see as image names are shorted. Verify “CLI” or “Minimal” as the image is downloading.)

  • Focal, Hirsute, Jammy, other variants, and Bullseye images with desktops are not supported.

This installation process requires a wired Ethernet connection and Internet access. Typically, all that is needed to begin the installation is an Ethernet cable, an Armbian supported SBC, a power supply sufficient for the SBC model being used, and one SD-card (two are preferred for backup).

To get started, a few utilities are needed to expand, check, and work with an Armbian image.

  • To check the decompressed image, an MD5 – SHA Checksum utility is needed. This utility is portable, meaning it's not necessary to install it, but it may require support files. Simply run the executable.
  • SDformatter is a utility for formatting SD-cards, that does a trim operation on flash media to clear remnants of old files. SDformatter is installable on a Windows client.
  • h2testw_1.4 is a flash media test program. With a freshly formatted SD-card or USB thumbdrive, it writes files with known content and verifies the content in a read operation, detecting errors in the process. h2testw_1.4 downloads as a zip file. By right clicking on the zip file, and using “Extract All”, 7-Zip will expand the zip file to a folder named h2testw_1.4 The executable inside this folder is a portable application. Run the executable.
  • To burn an Armbian Bullseye image to an SD-card, USBimager is recommended. (It burns the image and verifies it in one process.) USBimager for Windows is portable, with no required installation. Extract the archive with 7zip and use the executable file (usbimager.exe)
  • PuTTY is an SSH client that will allow users to connect to their SBC, from a Windows client, and get on the command line. PuTTY is installable on a Windows client.
  • While 8GB is the minimum and will work fine, a 16GB card will provide longer life in the role of a boot drive. Users are encouraged to get two SD-cards. One is for the installation and the second is for backing up the OS installation, when configuration is complete.

For the best experience, use only high quality new SD-cards, such as Samsung or SanDisk, that are rated A1 Class 10 or better.

Important - The location for image downloads has been moved to Armbian's Archive.

  • On the The Armbian Image Archive Page, scroll down through the page. Open the folder for the appropriate model of SBC and select a Bullseye Current Minimal image. Older Bullseye images are fine. They will be updated in processes following.
  • While image names may be appended in the archive, the smaller of the available image files tend to be “Minimal” or “CLI”. Look for Minimal or CLI in the image name as it downloads. If a mistake is made, cancel the download and try again.
  • In a similar manner, directly under the downloaded image, look for a file with a sha file extension. The sha hash withing that file will be used to verify the image as noted below.

(Due to the potential for package conflicts, an image with a desktop is not supported. Lastly, Bionic, Focal, Jammy, Bookworm etc., images will not work with OMV6.)

MD5 and SHA hashes check for image corruption that may have occurred during the download.

  Beginners Note - DO NOT SKIP THIS STEP

The chance of image corruption is highest when downloading and it's pointless to build a server with flawed software. Even the slightest corruption of the image may ruin your installation and the effects may not be noticed until well after your server is built and in use. Headaches can be avoided by checking the image.

Verify the image file, for your SBC, with the MD5 & SHA checksum utility.

(Note that it's possible to “drag and drop” the image file name into the utility, on the File line. Otherwise, use the Browse button and navigate to the image file.)

Click the SHA link under “Integrity”, that's associated with the image downloaded. A text file may download or a SHA256 hash may be displayed in the browser.

Notepad can be used to temporarily store the sha256 hash, copied from Armbian's web site or paste the hash directly into the bottom “Hash” line (above) and click on verify.

With a sha-256 match, the downloaded image is verified.

Using SDFormatter, do a clean format:

(Note that SDFormatter does a trim operation on the card which cleans up remnants of deleted or previously existing files.)

In most cases, SDFormatter will detect the SD-card or thumb-drive. A volume label is not necessary, at this point, and the default options are fine.

After the SD-card format is completed, open h2testw and select your language.
Then, click on Select target

Under Computer, select the flash media previously formatted.

Select Write+Verify. (Do not check the endless verify box).

A dialog similar to the following may pop up, highlighting a 1MB difference.
Ignore it and click on OK.

Without errors” is the desired outcome. If the media tests with errors or is much smaller than is indicated by the SD-card's labeled size, don't use it.

After H2testw verifies the SD-card; do one more clean format, using SDFormatter, before flashing the card. While optional, at this point, a volume label could be applied.

Start USBImager:

Using the highlighted file selector box, select and open the compressed image to be flashed.

Using the drop down select the SD-card.
The verify box should be checked.

Click the Write button to flash the image.

USBImager will write and verify the image.

*At this point, a wired Ethernet connection is required to connect to the SBC with PuTTY and to install OMV in a later process.*

  • Insure the SBC is connect to wired Ethernet.
  • Insert the SD-card, into the SBC, and apply power.
  • Wait 3 to 5 minutes.

The IP address to use for logging into the console is available from your DHCP server. In most cases, your DHCP server will be running on your LAN's router.

(The following is an example.)

With the IP address noted, proceed to First Time Login.


If there's a problem with obtaining a DHCP assigned IP address:

  • In the event that an IP address is not issued to your SBC, check the wired Ethernet connection and reboot the device. In some cases this will mean unplugging and plugging the power supply back in. Allow time for boot up (5 minutes or so) and check the DHCP server again.
  • If an address is not issued, or if the user doesn't know how to find the ARM device's IP address on their DHCP server, connect a monitor and keyboard to watch the boot process until it completes. If the IP address is not displayed at the end of the boot cycle, login with the user root and password 1234

Unfortunately, this first time logon will start a mandatory root user password change and the addition of a non-root user. Once these processes are complete, type ip add on the command line. Note the IP address of the Ethernet interface, in the output, and proceed to First Time Login.

  • In rare instances, it may be necessary to reboot the LAN's router, followed by rebooting the SBC.

Open PuTTY and type in the OMV IP address

A PuTTY Security Alert will pop up in a first time connection.
This is normal. Ignore it and select Yes.

When the SSH window opens:
Login as: root The Armbian default password is: 1234
After logging in with the default password, you'll be required to change the root password. Follow the prompts to enter and confirm a new root password. (Remember this password.)

Armbian will prompt for additional settings:

  • The shell to be used: Beginners should use bash.
  • The creation of a non-root user, with “sudo” admin abilities: User's choice. Ctrl+C will exit user creation.

On the command line, copy and paste the following command into the SSH window:

apt-get update

When the command prompt returns copy and paste the following command into the SSH window:

apt-get upgrade -y

(This process with take a few to several minutes.)

Finally, reboot the SBC with the following command:

Some devices may require a hard power off and on. In those cases, shutdown now, would be appropriate. Remove and reconnect power.

In a few minutes, open a new PuTTY/SSH window for the installation of OMV.

*In the event that the SSH client does not respond to the IP address used for the Armbian installation, look at your DHCP server again to see if a “new” IP address has been assigned.*

Installing OMV on Armbian is very easy, thanks to Arron Murray (ryecoaaron on the OMV Forum) for providing a comprehensive installation script that's executed from a single line.

Highlight and copy the following line complete (Ctrl+C) and paste it into PuTTY's SSH window, with a right mouse click. Then hit Enter.

wget -O - | sudo bash

Once the script is running, click out of the SSH window so the script will not be interrupted. Note: Do Not Close PuTTY – that will terminate the root session. Minimizing PuTTY is OK, but it must be running.

Depending on several factors, running this script may take up to 30 minutes.

When the script is complete, the SBC will automatically reboot.

After 3 to 5 minutes, OMV can be logged in using the same IP address that was used for the SSH client, entered in a web browser address bar. The web GUI user is admin and the default password is openmediavault

Note - after the completion of the script:

In the rare event that the OMV console or SSH client does not respond to the IP address used during the installation, recheck your DHCP server to see if a “new” IP address has been assigned.

(Typically, consumer router DHCP leases last at least 24 hours. In cases where DHCP leases are very short - as it is with some versions of DD-WRT router firmware [10 minutes] - the lease issued to the SBC may time out at the end of the installation. A different address may be issued on reboot.)

We, who support the openmediavault project, hope that you’ll find your openmediavault server to be enjoyable, efficient, and easy to use.
If you found this guide to be helpful, please consider a modest donation to support the hosting costs of this server.

Venmo: ryecoaaron

The decision was made to depreciate NetworkManager in SBC's running OMV. The primary reason for this decision was to better support the installation and use of Dockers. Unfortunately, NetworkManager wrecks networking for Dockers.

First it should be noted that using a wireless interface, with a server, is not the best idea. To prevent a number of issues such as interference, bandwidth contention issues with clients, etc., a server should be connected to the wired LAN ports of a router or a network switch. However it is understood that, in some cases, wired connections may not be an option.

If your SBC is equipped with a wireless interface, by default, OMV will not show it in the GUI but it can be added.

  • An existing interface can be added as noted in the following.
  • After plugging it in, a compatible add-on USB wireless interface can be added in the same manner.

Under Network, in the Interfaces tab, click on the + Add button. From the pop up, select Wi-Fi.

In the Create window, select the drop down arrow next to the Device field.
The on-board or add-on wireless interface will be the only interface in the list. Select it.

In the SSID field, enter the SSID for the wireless network.
In the Password field, enter the WiFi encryption password.
Under IPv4, in the Method field, click on the drop down arrow and select DHCP.

Scroll down and click, Save.

At this point, the wireless interface will appear under Network, in the Interfaces window. Further configuration can be done, as needed, by clicking on the interface line and the edit button (pencil).

To further configure the SBC; refer to the Getting Started with Openmediavault 6, starting in the section titled Initial Configuration.

  • omv6/armbian_bullseye_install.txt
  • Last modified: 2024/03/29 15:13
  • by crashtest