Armbian with preinstalled OpenMediaVault (OMV)

[MrT]

So something is wrong. When booting up the i can see all the checks that debian normally does. But then my screen turns black and the disks spin down.

I will try to see when this happens an if i can see the error on the screen.

 

 

 

[Igor]

28 minutes ago, MrT said:

for Odroid XU4 with OMV

32 bit Debian / OMV packages could be a problem. Can you try the same using some other hw platform?

[MrT]

I only have a Raspberry pi 4  or 3 to play with. Would that do?

[Werner]

Feel free to try with rpi4 since we provide 64bit images for it.

[AlexVS]

Hello Igor.

May I ask you to build an image with OMV7 preinstalled for RockPro64?
I don't have enough knowledge to do it on my own.

I know that OMV6 can be upgraded to OMV7 using omv-release-upgrade.
But as I understand it, the Armbian version will remain current.

[Werner]

There isn't much to it. tl;dr: clone the repo using git and execute ./compile.sh. Rest is interactive. https://docs.armbian.com/Developer-Guide_Build-Preparation/

Yes it is possible to include omv6(!) while building the image but there is actually not much to it doing by hand. This is basically how an Armbian omv-preinstalled image is made:

https://github.com/armbian/os/blob/3c2bf37c3544f2d16ac12e1c407e6976367ec4d0/userpatches/extensions/omv.sh#L15-L35

tl;dr: grab omv key, install omv key, apt update, apt install openmediavault

You can do that manually after first boot.

[AlexVS]

Hello.
Thanks for the hints, but unfortunately I don't understand everything.
In the previous version of armbian, OMV6 was included in the repository and installation was easy even for me.
In the new version (Bookworm), OMV7 is missing from the repository. 
If you can tell me which commands to add OMV7 to the repository, then I'll just have to write apt install omv.

[Werner]

Just checked and it seems like their Release file on the repo is still marked with ovm6 while the package you get when installing is omv7.

Tried to build an image with omv pre-installed, but throw a bunch of errors, so no idea if it works. https://fi.mirror.armbian.de/.testing/Armbian-unofficial_25.02.0-trunk_Rockpro64_bookworm_current_6.12.9-omv.img.xz

If not grab a standard rockpro image ( https://dl.armbian.com/rockpro64/Bookworm_current_minimal ) and proceed according omv docs:  https://docs.openmediavault.org/en/stable/installation/on_debian.html

Keep in mind that omv heavily messes with the system, so if anything breaks after installation (like network access or even boot) we cannot help. This is userspace.

 

[AlexVS]

Thank you. I'll try to install it.

[AlexVS]

11.01.2025 в 14:36, Werner сказал:

If not grab a standard rockpro image ( https://dl.armbian.com/rockpro64/Bookworm_current_minimal ) and proceed according omv docs:  https://docs.openmediavault.org/en/stable/installation/on_debian.html

Keep in mind that omv heavily messes with the system, so if anything breaks after installation (like network access or even boot) we cannot help. This is userspace.

Thanks for your help, the OMV7 installation went smoothly.

[Floyd2000]

Hi all,

I installed the pre-built OMV Image for my RPi4 the other week (Image from section "Dedicated applications images with Armbian Linux v6.12 Build Date: Mar 6, 2025") and everything is working fine so far.

However, today I noticed that the unattended-upgrades would not upgrade libraspberrypi0 and libraspberrypi-run. Upon attempting a manual upgrade I got the message that libc6 should be at least 2.38 while the installed version is 2.36. Before I trigger a dependency avalanche and possibly break things, I was just going to ask whether these 2 upgrades could simply be ignored or if there is a safe way to solve this.

Thanks for any feedback.

[Igor]

On 4/6/2025 at 10:43 AM, Floyd2000 said:

today I noticed that the unattended-upgrades would not upgrade libraspberrypi0 and libraspberrypi-run.

This should be fixed, but there might be an error with firmware package. Fix is uninstalling armbian-bsp*, updating all packages, installing bsp againg. 

[Floyd2000]

Hello Igor,
 

thanks for your reply and the advice about the armbian-bsp* package. It worked! 👍
I tried it out and finally managed to update all previously withheld packages and get rid of the error messages, but it was still kind of bumpy...

I had to take these steps:

1. dpkg -r the armbian-bsp-cli-rpi4b-current because apt remove would not work and produce errors
2. apt --fix-broken install
3. dpkg -i --force-all /var/cache/apt/archives/armbian-bsp-cli-rpi4b-current_25.2.3_arm64.deb as apt install would not work without errors and dpkg would not work without forcing it. The error message was something about armbian-bsp* trying to overwrite a file that had been created by raspi-firmware (or something like that. Unfortunately, I did not copy the exact message)

Now, everything seems up to date, including the RPi firmware (which had been quite old in the pre-built image, now it's up to date). BTW: in my previous post I wrote that OMV is running on an RPi4B, in fact that was a typo, it is an RPI3B+ really, so the firmware is not in an EEPROM, but only in a couple files in the /boot/firmware folder.
 

Thanks again. I'm curious if it will stay stable or if future updates will cause trouble again at some point. 🙂 🙃