Setting Up OpenMediaVault on a Raspberry Pi: Web-Based RAID, Shares, and Plugin Management
Hand-rolling a NAS on a Raspberry Pi with raw Samba config files and command-line mdadm works fine right up until a drive fails at 2am, a share permission breaks, or you want to add a second service without SSHing in and editing conf files from memory. OpenMediaVault (OMV) is a free, Debian-based NAS operating system with a full web UI for exactly this: RAID and filesystem management, Samba/NFS shares, user and ACL permissions, S.M.A.R.T. drive health monitoring, scheduled scrub jobs, and a plugin system that adds Docker, UPS monitoring, and dozens of other services without touching a terminal. On a Pi 4 or 5 with USB3 or a PCIe M.2/SATA HAT, it turns a $100 board into a genuinely manageable, appliance-like NAS that a less technical household member can actually use.
This guide covers installing OMV on a Raspberry Pi specifically (the official installer targets x86 Debian, so the Pi path is different), configuring your first RAID array and shares through the web UI, and the plugins worth installing on day one.
Why OMV Instead of Plain Samba or Manual ZFS
If you only need one or two shared folders and never plan to touch the config again, a manual Samba setup is fine and genuinely simpler. OMV earns its keep once you want any of: a web dashboard for drive health and disk usage, more than a couple of users with different share permissions, snapshot or scrub scheduling without remembering cron syntax, or additional self-hosted services running alongside file sharing. It's the difference between a single shared folder and an actual NAS appliance you can hand off to someone else in the house to manage day-to-day.
Hardware Requirements for a Usable Pi NAS
| Component | Recommendation | Why |
|---|---|---|
| Board | Raspberry Pi 4 (4GB+) or Pi 5 | OMV's web UI and plugin daemons want more headroom than a Pi Zero can give |
| Boot/OS drive | A separate SSD or quality USB3 flash drive — not the storage drives themselves | Keeps the OS off the array and avoids wearing out an SD card with constant writes |
| Storage drives | USB3 enclosures, or a PCIe/USB SATA or NVMe HAT | The Pi's SD card interface is far too slow and unreliable for bulk storage |
| Power supply | Official Pi power supply, plus a powered USB hub if running multiple bus-powered drives | Spinning up multiple drives at once can brown out an underpowered Pi |
| Network | Gigabit Ethernet (built-in on Pi 4/5), wired — never Wi-Fi for a NAS | Wi-Fi throughput and latency will bottleneck transfers badly |
Installing OMV on a Raspberry Pi
- Flash a clean Raspberry Pi OS Lite (64-bit) image to your boot drive using Raspberry Pi Imager, enable SSH in the imager's advanced options, and boot the Pi headless.
- SSH in, run a full
apt update && apt full-upgrade, and reboot. - Download and run the official OMV installer script for Raspberry Pi OS (the OMV project maintains a Debian-based installer script specifically for ARM/Pi hosts — check the current script URL on openmediavault.org before running, since install scripts change and you should never pipe a remote script into a root shell without reading it first).
- Let the installer run — it will install the OMV web stack, reboot once or twice, and finish by printing the web UI address (the Pi's IP address on port 80).
- Log into the web UI (default credentials are
admin/openmediavaulton first boot) and immediately change the admin password under General Settings.
Building Your First Array and Shares
Under Storage → Disks, wipe and initialize any new drives. Under Storage → RAID Management, create your array if you're using more than one drive — RAID1 (mirroring) is the sane default for a home NAS with two drives, trading capacity for the ability to survive a single drive failure without data loss. Format the resulting array under File Systems, then create a Shared Folder pointing at it. Finally, under Services → SMB/CIFS, enable the service and add your shared folder as an SMB share with the permissions you want — this is the point where OMV's web UI genuinely saves time over editing smb.conf by hand, especially once you have more than one user with different access levels.
Plugins Worth Installing Immediately
| Plugin | What It Adds |
|---|---|
| openmediavault-smart | S.M.A.R.T. drive health monitoring with email alerts before a drive fails outright |
| openmediavault-compose or openmediavault-docker-gui | Runs Docker containers (Home Assistant, Pi-hole, a media server) alongside file sharing, managed from the same web UI |
| openmediavault-usbbackup | One-click scheduled backup to or from a USB drive — handy for an off-site backup rotation |
| openmediavault-ups | Graceful shutdown integration if you've got a UPS protecting the NAS |
Backup Strategy: RAID Is Not a Backup
RAID1 protects you from a single drive failing; it does nothing for accidental deletion, ransomware, fire, or theft. Pair your OMV array with the openmediavault-usbbackup plugin or a scheduled rsync job to an external drive you can disconnect and store elsewhere, and treat the RAID array itself as availability, not backup. A NAS with no copy of its data living somewhere physically separate is one incident away from losing everything on it.
OpenMediaVault turns the fiddly, easy-to-forget parts of running a NAS — share permissions, drive health, scheduled maintenance — into something you configure once through a web page instead of relearning from scattered notes every time something needs changing. For a household Pi NAS that more than one person needs to use or trust, it's worth the extra setup step over a bare Samba config.