{{indexmenu_n>2}}
Installing OMV8 on a Raspberry PI
\\ \\ {{ :omv8-splash.jpg?nolink&600 |}} \\ ====== Installing OMV8 on a Raspberry PI ====== \\ Draft: 22 Dec 2025\\ Revisions: N/A\\ ===== Introduction ===== Installing OMV8 on Raspberry PI OS Lite Debian Trixie, using a scripted install, is a relatively easy task. This document is a guide for that process.\\ \\ ===== About this Guide ===== 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: [[omvguide@gmail.com]] \\
  FOREWORD
This guide was written to avoid as many installation pitfalls as is possible to anticipate or predict. With that in mind, please adhere to this guide without deviating in any significant way. Specifically, that means DO NOT preconfigure wireless networking (that will be covered later - after OMV is installed), or use raspi-config prior to the installation of OMV. Once the OMV installation is complete, and after backing the OS' SD-card → Cloning Flash Media, additional configuration or experimentation will be possible without losing the install, if something goes awry.
===== Supported Devices ===== OMV8 will install on R-PI models 3B and higher. \\ \\ ===== Not Supported ===== * **__Desktop__** versions of Raspberry PI OS are **NOT** supported. (Use the __Raspberry PI OS "**lite**"__ version only.) * //**Legacy Raspberry PI's**// R-PI models **earlier** than the **3B** are not supported. OMV8 requires a 64-bit kernel and a 64bit userland which will not run on 32-bit hardware. Please do not post on [[https://forum.openmediavault.org/|OMV's forum]], expecting support for these models. \\ ===== Prerequisites ===== 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. * Raspberry PI OS images are installed using the Raspberry PI OS imager. Download the appropriate imager -> [[https://www.raspberrypi.com/software/|here]]. The Raspberry PI OS imager is installable on a Windows client. **Note:** Users who have a version of the R-PI imager, **earlier than ver 2.X**, will need to update to ver 2.X to install Debian Trixie. * [[https://www.sdcard.org/downloads/formatter/index.html|SDformatter]] is a utility for formatting SD-cards that does a trim operation on flash media to clear remnants of old deleted files. SDformatter is installable on a Windows client. * Users will need a utility like [[https://www.7-zip.org/|7-Zip]] to decompress zip archives like the SD-card test program below. 7-Zip is installable on a Windows client. * [[http://www.heise.de/ct/Redaktion/bo/downloads/h2testw_1.4.zip|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. * [[https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html|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 a second card 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. {{ :armbian1_sd-card.jpg?80 |}} {{ :divider2.png?800 |}} ==== Format and Test Flash Media ==== 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.
---- \\
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.
{{ ::omv6-rpi-4.jpg?400 |}} \\
Note that SDFormatter does a "trim" operation on the card which cleans up remnants of previously existing or deleted files.
{{ :divider2.png?600 |}}
After the SD-card format is completed, open h2testw and select your language.
Then, click on Select target.
{{ ::omv6-rpi-5.jpg?400 |}} {{ :divider2.png?600 |}}
Under Computer, select the flash media previously formatted.
{{ ::omv6-rpi-6.jpg?400 |}} {{ :divider2.png?600 |}}
Select Write+Verify. (Do not check the endless verify box).
{{ ::omv6-rpi-7.jpg?400 |}} {{ :divider2.png?600 |}}
A dialog similar to the following may pop up, mentioning a 1MB difference. Ignore it and click on OK.
{{ ::armbian10_h2testw_warning.jpg?400 |}} {{ :divider2.png?600 |}}
“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.
{{ ::omv6-rpi-8.jpg?400 |}} \\ \\
After H2testw verifies the SD-card; do one more clean format, using SDFormatter, before flashing the card.
{{ :divider2.png?600 |}} ===== Burning the Image ===== \\ ==== The Raspberry PI OS Imager ==== 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. ---- \\
As previously noted, the imager installs as a standard Windows program.
\\ {{ :omv8:omv8-rpi-imager-v2.0.0.jpg?nolink&600 |}} \\ ---- \\
Under Rapsberry PI Device, click "Choose Device".
From the pop down list, select the applicable device.
{{ :omv8:omv8-rpi-imager-1.jpg?nolink&600 |}}
In this instance, an R-PI4 was selected.
As a reminder; R-PI's 5, 4, 3 are supported. Other variants are NOT supported.
(See →OMV8 compatibility for details.)
\\
Click Next.
\\ \\ ---- \\
Under Operating System, scroll down to Raspberry PI OS other and select it.
{{ :omv8:omv8-rpi-imager-2.jpg?nolink&600 |}} \\ ----
Select Raspberry PI OS Lite (64bit)
"A port of Debian Trixie with no Desktop environment".
{{ :omv8:omv8-rpi-imager-3.jpg?nolink&600 |}}
Click Next.
\\
  Warning
Do Not select "Full" versions of Raspberry PI OS. Desktop versions are not compatible with Openmediavault.
\\ ---- \\
Under Storage, select the mounted SD-card
{{ :omv8:omv8-rpi-imager-4.jpg?nolink&600 |}}
Click Next.
\\ ---- \\
Under Customisation, enter the hostname desired - users' choice.
{{ :omv8:omv8-rpi-imager-5.jpg?nolink&600 |}}
Click Next.
\\ ---- \\
Under Customisation, Customisation: Localisation, add the appropriate entries for the users' Capital City, Time zone and Keyboard layout.
{{ :omv8:omv8-rpi-imager-6.jpg?nolink&600 |}}
Click Next.
\\ ---- \\
Under Customisation, Customisation: Choose username, create a username and password.
The username and password entered here will be the administrative user that will be utilized in later operations on the command line.
{{ :omv8:omv8-rpi-imager-7.jpg?nolink&600 |}}
Click Next.
\\ ---- \\
Under Customisation, Customisation: Choose Wi-Fi, DO NOT change these entries.
If needed Wi-Fi will be configured later in the OMV8 GUI.
{{ :omv8:omv8-rpi-imager-8.jpg?nolink&600 |}}
Click Next.
\\ ---- \\
Under Customisation, Customisation: SSH authentication,
Enable SSH and select Use password authentication.
{{ :omv8:omv8-rpi-imager-9.jpg?nolink&600 |}}
Click Next.
\\ ---- \\
Under Customisation, Customisation: Raspberry Pi Connect:, users choice.
  Warning
Raspberry Pi Connect is a remote access tool with an unknown (to the author) security profile. Given that OMV is a server implementation, any software package that exposes server ports to the Internet should be CAREFULLY considered.
{{ :omv8:omv8-rpi-imager-10.jpg?nolink&600 |}}
Click Next.
\\ ---- \\
Under Write Image, review user selections. They should be very close to the following.
{{ :omv8:omv8-rpi-imager-11.jpg?nolink&600 |}}
Click Write.
Acknowledge the "Your are about to erase" Warning and continue.
\\
The imager will prompt: Write complete! Click Finish to conclude the burn.
\\ $$$$ Here $$$$ {{ :divider2.png?600 |}} ===== The First Boot ===== *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 a DHCP server example.
(In this example, the hostname "Raspberry PI" was changed to "R-PI4".)
{{ ::omv7-rpi-1srt_boot-1.jpg?800 |}} \\
With the IP address noted, proceed to First Time Login.
{{ :divider2.png?600 | |}}
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 may 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**. * In rare instances, it may be necessary to reboot the LAN's router, followed by rebooting the Raspberry 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. {{ :divider2.png?600 |}} ===== Raspberry PI OS - First Time Logon =====
Open PuTTY and type in the IP address as previously found.
(Optional, but recommended: Give the session a name, under Saved Sessions and save it for future use.)
Click on Open to start the session.
{{ ::omv7-rpi-1srt_boot-2.jpg? |}} \\
A PuTTY Security Alert will pop up in a first time connection.
This is normal. Ignore it and select Yes.
{{ :divider2.png?600 |}}
When the SSH window opens:
Login with the username and password entered in the R-PI imager.
{{ ::omv7-rpi-1srt_boot-3.jpg? |}} ---- \\ ===== Raspberry PI OS Updates and Upgrades ===== 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.
\\ ===== Install OMV ===== Installing OMV on Raspberry's is very easy, thanks to Arron Murray (ryecoaaron on the [[https://forum.openmediavault.org/|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''\\ \\ **Note:** Until OMV 8 comes out of BETA, pressing "C" to continue is necessary to continue with the install.\\ \\ 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. \\ ==== First Time GUI Logon ==== 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**\\ \\ Users may be prompted with a yellow banner to accept pending configuration changes. Click the check mark to accept.\\ ---- **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.) \\ \\ ===== Finishing Up ===== * **To add an existing or add-on Wireless Interface** to openmediavault, see [[https://wiki.omv-extras.org/doku.php?id=omv6:raspberry_pi_install#final_notes|Final Notes]] below. * New users can continue with the setup of OMV using the [[https://wiki.omv-extras.org/doku.php?id=omv7:new_user_guide|Getting Started with Openmediavault 7]] guide, starting in the section titled → [[https://wiki.omv-extras.org/doku.php?id=omv7:new_user_guide#initial_configuration|Initial Configuration]]. * All users are encouraged to review this resource → [[https://wiki.omv-extras.org/doku.php?id=omv7:utilities_maint_backup|Utilities, Maintenance & Backup]] for an easy process to clone your SBC's SD-Card and for additional information that will help in managing and maintaining an openmediavault server. \\ ===== Final Notes: ===== ==== Wireless Networking ==== 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.
\\ {{ ::omv6-rpi-18.jpg?800 |}} \\ ---- \\
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.
\\ {{ ::omv6-rpi-19.jpg?800 |}} \\
Scroll down and click, Save and Apply the changes with the yellow banner.
\\ 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). \\ \\ ---- ===== A Closing Note ===== 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** \\
\\ \\ **www.openmediavault.org** \\
\\ \\ **Venmo: ryecoaaron** \\