What is openmediavault?

openmediavault is the next generation network attached storage (NAS) solution based on Debian Linux. It contains services like SSH, (S)FTP, SMB/CIFS, RSync and many more ready to use. Thanks to the modular design of the framework it can be enhanced via plugins. openmediavault is primarily designed to be used in small offices or home offices, but is not limited to those scenarios. It is a simple and easy to use out-of-the-box solution that will allow everyone to install and administrate a Network Attached Storage without deeper knowledge.

Download

Features

  • Running out-of-the-box
  • Debian Linux OS
  • Web based administration
  • Easy system updates via Debian package management
  • Volume management
  • S.M.A.R.T.

  • Link aggregation
  • Wake On Lan
  • IPv6 support
  • Email notifications
  • File sharing
  • Snapshot support of shared folders
  • Extendible via plugins

More features

Latest news

New updates available

Posted: 9. January 2026

openmediavault 8.0.6

  • Various improvements.
  • Add support for network interfaces connected via USB bus.

openmediavault-ftp 8.0.1

  • Handle SSL certificates with Elliptic Curve (EC) cryptography.

0 comments

mdadm: cannot be set as devname. Reason: Not POSIX compatible

Posted: 3. January 2026

If you are also affected by this warning from the MD subsystem, then take a look at this example to see how you can permanently disable this warning.

With Debian 13, mdadm now enforces POSIX-compliant device names for RAID arrays. Many older RAID arrays (metadata version 1.x) store their name internally in the form hostname:array (for example nas:md0). While Linux filesystems allow colons in filenames, POSIX standards do not. Debian 13 therefore refuses to use such names when creating block device nodes.

When this happens:

  • mdadm ignores the stored array name
  • the RAID is still assembled correctly using its UUID
  • a warning is printed to explain why the name was skipped

This is an intentional change aimed at improving portability, scripting safety, and long-term compatibility. The RAID itself is not damaged or misconfigured; only the legacy naming scheme is affected.

The following example shows how a RAID5 based on 3 drives is modified.

root@omv8box:/# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid4] [raid5] [raid6] [raid10]
md127 : active (auto-read-only) raid5 vdd[2] vdb[0] vdc[1]
      2093056 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
unused devices: <none>

root@omv8box:/# mdadm --detail --scan
mdadm: Value "omv8box:0" cannot be set as devname. Reason: Not POSIX compatible. Value ignored.
ARRAY /dev/md/omv8box:0 metadata=1.2 UUID=6b4e1273:61deb387:90439348:6acaeae0

root@omv8box:/# mdadm --stop /dev/md127
mdadm: Value "omv8box:0" cannot be set as devname. Reason: Not POSIX compatible. Value ignored.
mdadm: stopped /dev/md127

root@omv8box:/# mdadm --assemble --update=name --name=md0 /dev/md0 /dev/vdb /dev/vdc /dev/vdd
mdadm: Value "omv8box:0" cannot be set as devname. Reason: Not POSIX compatible. Value ignored.
mdadm: /dev/md0 has been started with 3 drives.

root@omv8box:/# mdadm --detail --scan
mdadm: Value "omv8box:0" cannot be set as devname. Reason: Not POSIX compatible. Value ignored.
ARRAY /dev/md0 metadata=1.2 UUID=6b4e1273:61deb387:90439348:6acaeae0

root@omv8box:/# omv-salt deploy run mdadm

root@omv8box:/# mdadm --detail --scan
ARRAY /dev/md0 metadata=1.2 UUID=6b4e1273:61deb387:90439348:6acaeae0
0 comments

More news