[Bug]: OpenMediaVault Installation on Raspberry Pi 5

[SlevinK42]

What happened?

I tried to install OpenMediaVault (OMV) on a Raspberry Pi 5 with a fresh install of Armbian 25.8.1 (Debian Bookworm) with both, the armbian-config as well as the official OMV documentation.

The installation process does not finish even after ~3 hours. During the installation, I watched the logs under /var/log/syslog and found a myriad of the same log messages

rpi5b systemd-udevd[338]: /usr/lib/udev/rules.d/60-i2c-aliases.rules:8 Unknown group 'i2c', ignoring
rpi5b systemd-udevd[338]: /usr/lib/udev/rules.d/60-piolib.rules:1 Unknown group 'gpio', ignoring
rpi5b systemd-udevd[338]: /etc/udev/rules.d/99-com.rules:2 Unknown group 'i2c', ignoring
rpi5b systemd-udevd[338]: /etc/udev/rules.d/99-com.rules:3 Unknown group 'spi', ignoring
rpi5b systemd-udevd[338]: /etc/udev/rules.d/99-com.rules:4 Unknown group 'gpio', ignoring
rpi5b systemd-udevd[338]: /etc/udev/rules.d/99-com.rules:7 Unknown group 'gpio', ignoring
rpi5b systemd[1]: Reloading.

With every systemd reload, not only the installation, but the whole system freezes for ~90 seconds. after ~30 minutes into the installation process, the salt-minions start throwing errors as they timeout not being able to reach the salt master:

rpi5b salt-minion[19476]: [ERROR ] DNS lookup or connection check of 'salt' failed.
rpi5b salt-minion[19476]: [ERROR ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds

This finally breaks the installation.

I was able to fix both, the armbian-config and the official OMV installation procedures by simply adding the missing groups for the hardware interfaces before starting the installation via

groupadd --system --force i2c
groupadd --system --force gpio
groupadd --system --force spi
udevadm control --reload-rules
udevadm trigger

The systemd reloads now run through without freezes and the whole installation takes <3 minutes. As these groups might also be used by other packages for the Raspberry Pi, it is probably advisable to automatically add these groups during the Armbian installation, as it is done with the Raspberry Pi OS.

How to reproduce?

1. Start with a fresh install of Armbian 25.8.1 on a Raspberry Pi 5, skip the new user add
2. Update the system via apt update && apt upgrade and reboot
3. [The above fix would come here]
4. Start the OMV installation via armbian-config --cmd OMV001 and watch the logs under /var/log/syslog

On which OS are you observing this problem? (for easier diagnosis please provide logs with armbianmonitor -u)

Armbian Debian 12 Bookworm

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Hey @SlevinK42! 👋

Thanks for opening your first issue with the Armbian project — we’re glad to have you here! 🧡
Your input doesn’t just help us improve the project — it benefits everyone who uses Armbian.

If you'd like to stay informed about project updates or collaborate more closely with the team,
you can optionally share some personal contact preferences at armbian.com/update-data.
This helps us keep in touch without relying solely on GitHub notifications.

Also, don’t forget to ⭐ star the repo to support the work — and welcome aboard! 🚀