Alternate Install - OMV6 on a Raspberry PI

On rare occasions, the “Current Image”, downloaded by the Raspberry PI imager, may have a minor flaw associated with it which may cause issues with an OMV build. Finding and fixing an OS release flaw, along with pushing out a new image, may take some time. In such an event, this alternate build process might be useful as a workaround. It uses a fixed, older, and well tested image that is fully updated to the lasted packages as part of the build process.

The purpose and intent of this guide is to provide a walk-through to get Raspberry Pi users (hereafter referred to as an “R-PI”) 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 is a community document and a work in progress. Input and feedback are welcome and can be sent to:

OMV6 will install on R-PI models 2B and higher. However, in practical terms, the performance of the model 2B is marginal.

  • Desktop versions of Raspberry PI OS are NOT supported. (Use the Raspberry PI OSlite” version only.)
  • Legacy Raspberry PI's

R-PI models earlier than the 2B and the R-PI Zero have not been tested and are not supported. They are far too slow to run a NAS application. Please do not post on OMV's forum, expecting support for these models.

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

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

  • Raspberry PI OS images are compressed with a .zip extension. Users will need a utility like 7-Zip to decompress the image. 7-Zip is installable on a Windows client.
  • 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 a Raspberry PI OS 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 SD-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 Release Note
This build guide uses the Raspberry PI OS 2022-01-28 64bit image. Download the image → here
The SHA256 check sum is: d694d2838018cf0d152fe81031dba83182cee79f785c033844b520d222ac12f5
This image will build in accordance with this guide and the build will be a fully updated Raspberry PI OS install when complete.

After downloading the Raspbian OS Lite zip archive, run a SHA hash to check for file corruption that may have occurred during the download. The Raspberry PI project provides a SHA-256 hash check number for the downloaded Zip archive file.


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 zip archive.

Verify the downloaded Zip file with the MD5 & SHA checksum utility. Note that it's possible to “drag and drop” the file name into the utility, on the File line. Otherwise, use the Browse button and navigate to the zip file.

With the previously noted down SHA-256 hash, or by referencing the Raspberry PI OS Raspberry PI OS Web page, compare the utility's result with the SHA-256 hash provided on the download page. For this particular example it's: 008d7377b8c8b853a6663448a3f7688ba98e2805949127a1d9e8859ff96ee1a9

With a SHA-256 match, the downloaded file is verified.

Raspberry PI OS images are compressed and will need to be extracted with 7-Zip. (The following process assumes 7-Zip has been installed.)
Highlight the compressed file, right click the mouse, and make the menu selections shown below.

The result of the above action is the extraction of an uncompressed folder, with the image file inside. Open that folder. The image file's extension is .img

When an SD-card is inserted and recognized, Windows may offer to format the card more than once. Cancel each of these attempts.

Using SDFormatter, do a clean format:

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.

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

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, mentioning 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.

Start USBImager:

Using the highlighted file selector box, select and open the decompressed 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.

{{ :divider2.png?600 |

Raspberry PI OS is designed to have it's configuration finalized with a monitor and keyboard attached. However, there's no need for a monitor and keyboard to support an OMV installation. OMV was designed, from the ground up, to run as a headless server.

For the sake of convenience, Raspberry PI OS can be configured to enable it's SSH server on first boot, so the server can be accessed remotely with PuTTY. The following will enable SSH access.

To insure the file system on the Raspberry PI OS flashed card is recognized, unplug the SD-card for a few moments and plug it back into the PC used to flash the SD-Card.

Open a file manager window, displaying the file contents of the of the SD-card.
Right click in the files side (right window) and select, New, and Text Document.

A file is created. Name the file ssh with no extension.

Confirm, as shown above, that the file ssh has no extension. (This will mean removing .txt from the file name.)

The following warning may pop up, regarding a file without an extension.
Ignore it and select “Yes”.

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

  • Insure the R-PI is connect to wired Ethernet.
  • Insert the SD-card with the Raspberry PI OS image, into the R-PI 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. Log into your router and look for the IP address associated with your R-PI.

(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. 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 Raspberry Pi's IP address on their DHCP server, connect a monitor and a USB 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 pi using the password raspberry.

Once logged in, type ip add on the command line. Note the IP address of the Ethernet interface, in the output, and proceed to First Time Login.

(To be able to utilize Copy + Paste; working with the R-PI using SSH, as detailed in First Time Login, is highly recommended.)

Open PuTTY and type in the IP address as previously found.

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: pi
The Raspberry PI OS default password is: raspberry

After logging in with the default password, it's strongly recommended that the password for the pi user be changed.

On the command line, type;


Re-enter the current password raspberry, then follow the prompts to enter and confirm a new password for the pi user password. (Remember this password.)

Before installing OMV, update and upgrade Raspberry PI OS using the following commands, executed one at at time:

sudo apt-get update

sudo apt-get upgrade -y

The following command applies to R-PI 3 models only, but there's no penalty if it runs on other models.

sudo rm -f /etc/systemd/network/

When the above commands above are complete, type;

sudo reboot

PuTTY will disconnect – this is expected. Wait 3 to 5 minutes and reopen a new PuTTY SSH window and log in again.


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

In some cases, the router / DHCP server may need a reboot.

Installing OMV on Raspberry's 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.

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.
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 R-PI 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 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.)

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 R-PI 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).

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

  • omv6/alternate_raspberry_pi_install.txt
  • Last modified: 2023/02/25 14:07
  • by crashtest