volker

New updates available

openmediavault 8.0.9

  • Use performance CPU governor for AMD64 and i386 architectures by default. Other architectures use schedutil as default governor. Run the cpupower frequency-info command to check the governors available on your system and use the OMV_CPUPOWER_GOVERNOR environment variable to customize it if necessary.
  • Issue #2120: Sync HTML lang attribute with current locale.

openmediavault-k8s 8.1.0

  • Update locale files.
  • Remove the Kubernetes Dashboard integration.

New updates available

openmediavault 8.0.8

  • Issue #1520: Improve button accessibility by adding aria-label.
  • Issue #2115: Language switcher is not visible on mobile devices.
  • Issue #2116: Fix RRD graph render issue on mobile devices.

openmediavault-k8s 7.4.17

  • Ensure the port configuration is correct in Traefik Helm chart.

openmediavault-k8s 8.1.0

  • Issue #1940: Add UI support to configure additional Load Balancer (Traefik) ports.
  • The Load Balancer port web will not be exposed by default anymore.
    Please enable it via UI if needed.
  • The following environment variables have been removed, please use the new UI functionality instead:
    • OMV_K8S_TRAEFIK_PORTS
    • OMV_K8S_TRAEFIK_ENTRYPOINT_TRANSPORT_RESPONDINGTIMEOUTS_READTIMEOUT

New updates available

openmediavault 8.0.7

  • Update i18n files.
  • Various improvements.
  • Issue #2100: Fix bug when reloading sysctl configuration.

openmediavault-md 8.0.2

  • Show device file in dashboard widget if name is empty.

openmediavault-photoprism 8.0.1

  • Issue #2110: Modify MariaDB image version to 11 as suggested in the PhotoPrism documentation.

New updates available

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.

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

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