installing_omv5_raspberry_pi

Getting Started with OMV Addendum B:

Installing OMV5 on a Raspberry PI



If preferred, this document is available in PDF form at this location → Installing OMV5 on a Raspberry PI

Installing OMV5 on Raspberry PI OS Lite, using a scripted install, is a relatively easy task. This document is a guide for that 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 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: omvguide@gmail.com


OMV5 will install on R-PI models 2B and higher. 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.)

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 expand, check, 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, Etcher is recommended. (It burns the image and verifies it in one process.) Etcher is installable on a Windows client.
  • 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

  • When selecting an Image, for best possible compatibility with OMV5, don't use an image with a desktop.
  • On the Raspberry PI OS download page, scroll down and select the download for Raspberry Pi OS Lite

For the purposes of illustration, this SHA-256 hash for an older version of Buster Lite was: 9e5cf24ce483bb96e7736ea75ca422e3560e7b455eee63dd28f66fa1825db70e (* This hash number will change with the image, as images are updated. *) Make a note of the hash number found, or bookmark the download web page for reference. This will be used later.



After downloading the Raspbian OS Lite image, 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.

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 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 image 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 illustration only it's: 9e5cf24ce483bb96e7736ea75ca422e3560e7b455eee63dd28f66fa1825db70e

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


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. 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 Etcher:

Etcher, in most cases, will auto detect the SD-card or a USB thumb-drive. Click on “Select Image” and navigate to the decompressed Raspberry PI OS image. Then click on Flash!

  • A windows confirmation dialog may pop up. (Click on OK.)
  • Etcher will write the image, then verify it in one operation.

A “Success” flag will pop up when the job is finished and the Etcher window will display “Flash Another?”. The flash operation is complete. (For the moment, leave the SD-card connected to the PC.)

Raspberry PI OS is designed to have it's configuration finalized with a monitor and keyboard attached. 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;

passwd

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

sudo rm -f /etc/systemd/network/99-default.link

When all three 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.


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 - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | 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 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 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.)


OPTIONAL: The user pi is added by Raspberry PI OS, by default. Since this is a minor security risk, it's recommended that users add a new user for server admin purposes. For the purposes of illustration, the user added in the following will be named admin-user.



Under Access Rights Management, User, in the Users Tab, click on the Add button.

Add a new user name to the Name field. Set and confirm a Password for the new user.

(*Note that the users admin, root, backup, and others are Linux system users. Do not attempt to create a user using these exact system account user names. The add user dialog may reject attempts to configure a new user with the exact same name of an existing system user*)

Click on the Groups tab. Under System Accounts, check the boxes for the following: adm, root, ssh, sudo, users Other groups may be selected if needed.

Click Save.

Using the new user name and password, test the result by ssh'ing in the R-PI with PuTTY. If successful, the user pi can be deleted.

New users can continue with the setup of OMV using the Getting Started with Openmediavault 5 guide, starting in the section titled OMV - Initial Configuration.

All users are encouraged to review the section titled Operating System Backup for an easy process to clone your SBC's SD-Card.

To add a Wireless Interface see Final Notes below.


If you found this guide to be helpful, and OMV on Raspberry PI OS to be useful, please consider a modest donation

In addition to enabling the installation of OMV on Raspberry PI's, OMV-extras.org develops plugin's for OMV that increase functionality, enabling Dockers VIA Portainer and other extensions for your Raspberry PI. To support continuing development and to help offset some of the Developer's costs, even small donations are greatly appreciated.






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.

(*In the example below, a wireless USB adapter is being added to a Rock64 without an onboard interface.*)

Under System, Network, in the Interfaces tab, click on the + Add button. Select Wi-Fi.



When the Add Wi-Fi dialog box pops up, select the drop down arrow next to Device. The on-board or add-on wireless interface will be the only interface in the list. Select it.

In the Wi-Fi section, add the SSID for the wireless network and the encryption Password.



Using the right scrool bar, scroll down to IPv4. Next to Method, click the drop down arrow and make the appropriate selection. (DHCP is recommended for beginners.)

Click, Save.

At this point, the wireless interface will appear under System, Network, in the Interfaces tab. Further configuration can be done, as needed, by editing the interface in the Interfaces tab.


To further configure the R-PI; refer to the Getting Started with Openmediavault 5 guide, starting in the section titled OMV - Initial Configuration.

  • installing_omv5_raspberry_pi.txt
  • Last modified: 2021/02/16 19:37
  • by crashtest