OpenMediaVault
5 minute read
From Exaviz Management 1.1.2, OpenMediaVault 8 (a file server with its own web interface) can run on the same board as the dashboard. The dashboard keeps ports 80 and 443 and moves OpenMediaVault’s web interface to port 8080 or the next free port. Tested on Interceptor only.
On a board running Debian 13, the dashboard’s Help has an OpenMediaVault section with the same instructions. Read it, or this page, before you start.
Before you start
- The board must run Debian 13. OpenMediaVault 8 needs Debian 13. On a board running Debian 12 it is not supported, and Help says so.
- Update Exaviz Management to 1.1.2 or later (see Getting Started).
- Install OpenMediaVault first. Installing it after Exaviz Management is handled (the dashboard waits for the install to finish, then moves OpenMediaVault’s web interface), but that order has not been tested on a fresh install.
What the install changes
The install takes about 15 minutes and changes SSH, the kernel, networking and a hardware reset timer. Read the details before you start and check them when it finishes.
SSH. SSH logins are refused for about 11 minutes during the install, until the installer adds your account to OpenMediaVault’s
_sshgroup. Any other account that needs SSH must be added to_sshafterwards.Root SSH login. The installer turns root SSH login on. To turn it off, read the settings, send them back with
permitrootloginset tofalse, then apply onlysshandavahi:sudo omv-rpc -u admin Ssh get sudo omv-rpc -u admin Ssh set '<the same JSON>' sudo omv-rpc -u admin Config applyChanges '{"modules":["ssh","avahi"],"force":false}'Kernel. The installer upgrades the kernel (6.12 to 6.18 on our test board).
Networking. The installer turns on systemd-networkd next to NetworkManager.
Reset timer. The installer turns on a hardware reset timer that restarts the board if it stops responding for 14 seconds.
SMB. SMB in OpenMediaVault needs a hostname of 15 characters or fewer.
Install
Run the install from your normal login account with sudo, not from a root shell, with this one command:
wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | sudo bash -s -- -n
The -n belongs to the install script and leaves the board’s network setup alone. Without -n
the same script removes NetworkManager and reboots the board, which takes it off its current
network setup.
Do not apply its network changes
OpenMediaVault copies the board’s network setup into its own settings. Do not apply OpenMediaVault’s pending network changes: they would replace the board’s port setup. Storage in the dashboard shows a warning while such changes are waiting.
Changing the hostname or anything on OpenMediaVault’s Network pages marks its network configuration (systemd-networkd) as pending, and the next Apply in its web interface applies it with everything else. That writes a second configuration for each port next to the board’s own, and the two compete for the same ports, which can take the board off the network.
Apply the other pending changes from the command line instead, leaving systemd-networkd out, for example:
sudo omv-rpc -u admin Config applyChanges '{"modules":["samba","fstab"],"force":false}'
Then take the network entry off the pending list:
sudo cp /var/lib/openmediavault/dirtymodules.json /root/dirtymodules.json.bak
sudo jq 'map(select(. != "systemd-networkd"))' /root/dirtymodules.json.bak | sudo tee /root/dirtymodules.json.new
Check that it printed a list, then:
sudo mv /root/dirtymodules.json.new /var/lib/openmediavault/dirtymodules.json
If jq reports an error, stop: the live file is unchanged. The warning in Storage goes away once
the list no longer holds systemd-networkd.
What Exaviz Management does for you
Exaviz Management keeps ports 80 and 443 for its own dashboard and screen. When OpenMediaVault’s web interface is set to port 80 or 443, at install or later, it changes only that setting, to the first free port from 8080 to 8089 (HTTPS from 8443 to 8452), and applies only OpenMediaVault’s web server (nginx and monit). Storage shows the port the web interface is on now, and links to it.
- It waits while a package install or an OpenMediaVault configuration run is in progress.
- It never applies OpenMediaVault’s network, SSH or file sharing settings, and every change it makes is written to the system journal.
- It masks
systemd-networkd-wait-online.serviceonce, when systemd-networkd manages none of the board’s network links, which removes a boot delay of about a minute. If you unmask it, it stays unmasked. The mask stays if Exaviz Management is removed; to undo it, runsudo systemctl unmask systemd-networkd-wait-online.service. - OpenMediaVault stays on its new port too. Move it back with
omv-firstaidor in its web interface settings.
OpenMediaVault drives in Storage
OpenMediaVault mounts drives under /srv, for example /srv/dev-disk-by-uuid-<uuid>. Storage
lists each one under its filesystem label, or as OpenMediaVault drive (<device>) when it has
none. You can browse and download files there.
- Upload and delete are refused on these drives, and on a
/mnt/data*folder that is a bind of one, because a file the dashboard writes would belong to root and a share user could not remove it. Use OpenMediaVault’s shares to add or remove files. A board that used such a bind can no longer upload or delete there after the update to 1.1.2. - The dashboard login can read every file on these drives, regardless of share permissions.
- A drive that is also bound at
/mnt/data*is listed once, under its/mnt/data*name. - On a software RAID (md) volume, the health label on its Storage card shows No health data, because that card reports health only for one NVMe or SATA drive. Each disk in the array still has its own row on the Drives card. That row is about the disk. It does not say whether the array is degraded or rebuilding.
Last modified November 18, 2026