Revisions:
February, 3rd, 2024 - Short version for RC1
February, 11th, 2024 - Expanded / Full version.
Installing OMV7 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.
OMV7 will install on R-PI models 2B and higher. However, in practical terms, the performance of the model 2B is marginal.
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 SD-cards are preferred for backup).
Note | |
For best results, please DO NOT vary from the process outlined. Examples of variation would be "preconfiguring wireless networking" or the installation of extra packages before running the installation script. |
To get started, a few utilities are needed to check the SD-card and install the Raspberry PI OS image.
For the best experience, use only high quality new SD-cards, such as Samsung or SanDisk, that are rated A1 Class 10 or better.
Due to the rise in counterfeit media and media that reports a fake size, it’s recommended that all SD-cards or USB thumbdrives, new or used, be formatted with SDFormatter and tested with h2testw1.4 before using them.
Note | |
When an SD-card is inserted and recognized, Windows may offer to format the card several times. Cancel all of these attempts. |
All supported models of Raspberry PI will run the 32bit lite image of Raspberry PI OS. However, when using the 32bit image, model 4's with 8Gb of ram would be limited to using 4Gb of ram for a “single process”. This is not to say that the extra 4Gb of ram is wasted. The additional 4Gb would be distributed among additional processes. However, the 64bit lite version will allow more than 4Gb per process and, in many instances, performance is better / faster.
In any case, users with Raspberry PI models 3 or higher will be well served with 64bit lite version.
Users of Raspberry PI model 2B users should use the 32bit lite image.
The Raspberry PI Imager is a convenient “all in one” utility for burning Raspberry PI OS onto an SD-card. In the options allowed by the imager, the appropriate image for OMV is selected, the image is downloaded, it's burnt to the SC-card and the image is verified in one step.
Warning | |
Do not select "Full" versions of Raspberry PI OS. Desktop versions are not compatible with Openmediavault. |
Warning | |
The username, created in this dialog, CAN NOT be admin. admin is reserved for the OMV installation. |
*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.*
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.
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.
Before installing OMV, update, upgrade and prepare Raspberry PI OS using the following commands:
Copy each of the following commands, one at a time.
Highlight a command and use (Ctrl+C) to copy the full line. Paste the line into PuTTY's SSH window, with a right mouse click. Then hit Enter.
sudo apt-get update
sudo apt-get upgrade -y
wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/preinstall | sudo bash
When the above commands 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.
Note | |
In the event that the SSH client does not respond to the IP address used during the first boot, look at your DHCP server to see if a “new” IP address has been assigned. In rare cases, the LAN's 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 - 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.
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.
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 (OMV-Extras) and the project (Openmediavault).
OMV-Extras.org