OpenMediaVault: a Debian-based NAS you run entirely from a browser
You’ve got a few drives, an old server or a mini-PC, and you want a central place to keep backups, photos and movies, reachable from the network on any device. Two classic paths: buy a commercial NAS box (Synology, QNAP), pay for a closed firmware and hope security updates keep coming, or hand-configure Samba, NFS and mdadm on plain Linux, which works, except every new share or added disk means editing config files and restarting services.
OpenMediaVault (openmediavault.org ) sits in between: a complete NAS distribution built on Debian but managed entirely from a web interface, licensed under GPLv3. We evaluated it as an option for anyone who wants the convenience of a commercial box but on their own hardware, with full control over the system underneath.
What OpenMediaVault actually is
OpenMediaVault (often shortened to OMV) is, at its core, a stable Debian install with a management layer on top: a daemon and a web interface (built on Angular/PHP) that translates clicks in a friendly UI into system commands - creating software RAID, sharing over SMB, configuring users and permissions, monitoring disks. It’s the spiritual successor to the old FreeNAS (before it became TrueNAS), but built on Debian/Linux instead of FreeBSD, which means broader hardware and driver compatibility.
Redundant storage relies on two complementary mechanisms: software RAID via mdadm (classic RAID1/5/6/10 at the Linux kernel level) for real-time redundancy, and SnapRAID, a more unconventional tool that computes parity information periodically (not in real time), suited for archives of data that don’t change often - photos, movies, backups - where you don’t need instant protection against a dead disk, but you do want to be able to rebuild the data if it happens.
What makes OMV genuinely useful long-term is its plugin system, omv-extras: an additional package repository that extends the base install with ZFS support, Docker/Portainer integration for running containers directly on the storage box, cloud backup clients and more, all without leaving the web UI.
Why this matters
The difference from a commercial NAS box isn’t only hardware cost. With a closed firmware, you’re at the vendor’s mercy for how long you keep getting security updates and what features get added or dropped in a new release. With OMV, you have a standard Debian underneath: you can install any package from the Debian repositories, upgrade the operating system independently of OMV, and if the OMV project itself disappeared tomorrow, you’d still have a working Linux server with Samba and mdadm configured, not a sealed box turning into e-waste.
What you get out of the box
- A full web interface for managing disks, volumes and shares, no command line needed for day-to-day operations
- File services: SMB/CIFS (Windows/macOS/Linux), NFS (Linux/Unix), FTP, SSH, rsync
- Software RAID via mdadm (RAID0/1/5/6/10) plus SnapRAID as an alternative for rarely-modified data
- User and group system with per-share permissions, plus support for external authentication (LDAP/AD)
- SMART monitoring for disks, email notifications on events and thresholds
- A plugin system (
omv-extras) for ZFS, Docker/Portainer, cloud clients and more - Support for x86_64 and ARM architectures (including Raspberry Pi), useful for low-power boxes
Installing OpenMediaVault on a VPS
Let’s be upfront: OpenMediaVault is designed for physical hardware with dedicated disks, not a regular VPS with a single virtual disk. That said, it can make sense to test your configuration or run a management/monitoring instance on a VPS before deploying to physical hardware, or to validate a new plugin without touching the production box.
# install on a clean Debian machine (classic path, on top of an existing OS)
wget -O - https://packages.openmediavault.org/public/archive.key | gpg --dearmor | tee /etc/apt/trusted.gpg.d/openmediavault-archive-keyring.gpg
echo "deb [signed-by=/etc/apt/trusted.gpg.d/openmediavault-archive-keyring.gpg] https://packages.openmediavault.org/public sandworm main" \
| tee /etc/apt/sources.list.d/openmediavault.list
apt update
apt install openmediavault-keyring
apt update
apt install openmediavault
After install, the web UI listens on port 80/443 by default, and the initial login uses the admin user. In a VPS test environment with no extra physical disks attached, you can still practice configuring SMB/NFS shares on the main volume, though you won’t be able to demonstrate RAID or SnapRAID without separate attached disks.
# web admin interface
ufw allow 80/tcp
ufw allow 443/tcp
# SMB/CIFS
ufw allow 445/tcp
ufw allow 139/tcp
# NFS (portmapper + nfsd; exact port differs between NFSv3 and NFSv4)
ufw allow 2049/tcp
ufw allow 111/tcp
# FTP, if you enable it
ufw allow 21/tcp
On a VPS, consider restricting these rules to a single IP or a private network rather than exposing SMB/NFS publicly - these are protocols designed for trusted local networks, not the open internet.
Configuration patterns worth knowing
Choose RAID or SnapRAID based on the data type
For data that changes frequently and needs immediate availability after a disk failure, mdadm (RAID1/5/6) is the right call. For relatively static archives - media libraries, periodic backups - SnapRAID gives you the flexibility to add disks of different sizes at any point, something classic RAID doesn’t allow easily.
Don’t skip SMART monitoring
OMV has native integration with smartmontools, but email notifications need to be configured explicitly (SMTP server, temperature threshold, reallocated-sector threshold). A disk that starts throwing SMART errors weeks before it fully dies is exactly the scenario where you want to be alerted automatically, not to find out after you’ve already lost data.
Plugins mean an extra repository, not magic
omv-extras adds a package repository on top of standard Debian. Before enabling experimental plugins (especially community ones, not official ones), check which OMV version they’re actively maintained against - the project evolves, and abandoned plugins can end up incompatible after a major upgrade.
Docker through OMV vs. Docker managed manually
The Docker/Portainer plugin is convenient for running a handful of extra containers (say, a cloud sync service) directly on the NAS box, but if your plan is to run a complex, actively maintained Docker stack, consider separating it onto a dedicated machine - a NAS loaded with too many roles becomes harder to troubleshoot when something breaks.
Where OpenMediaVault is not the right answer
If you need storage for a production environment with serious availability requirements (automatic failover, multi-node replication), OMV isn’t built for that - it’s a single-node NAS solution. For that, look at Ceph or a dedicated cluster storage solution instead.
Also, on a regular VPS with a single virtual disk already redundant at the hypervisor level, most of OMV’s value (software RAID, SnapRAID, SMART monitoring on physical disks) simply doesn’t apply. OMV earns its place on physical hardware, with multiple disks mounted directly.
Finally, if all you need is a simple SMB share and nothing more, a standalone samba install without the OMV management layer stays easier to reason about and troubleshoot for anyone already comfortable with plain Linux.
Alternatives we considered
- TrueNAS CORE/SCALE : built on native ZFS (CORE on FreeBSD, SCALE on Debian/Linux), with more advanced enterprise storage features, but higher hardware requirements (especially RAM for ZFS)
- Unraid : a commercial (not free) solution very popular in the home-lab space, with a flexible parity model similar to SnapRAID, but a paid license
- Samba + mdadm managed manually: for anyone who wants full control with no management layer on top, at the cost of configuring everything from the command line
So, should you run it?
OpenMediaVault makes clear sense when you have dedicated physical hardware - a mini-PC, a repurposed old server, an ARM board with a few USB or SATA disks attached - and you want a friendly interface over Debian without giving up the flexibility of a standard Linux underneath. It’s not, however, the right tool for storage on a regular VPS, where the virtual disk is already managed by the hypervisor.
If your plan is to pair a local OMV NAS with offsite backups or with services running in the cloud alongside it, a VPS is the right place for the networking and externally-reachable services side of things, and if you’d rather have someone handle maintenance and monitoring for the whole setup, check out our server administration service and our network section for context on how all of this fits together in a full infrastructure.
