OMV7 on RaspberryPi 5 - INFO - DO NOT INSTALL UNLESS FOR TESTING

[EDIT]

DISCLAIMER: This is just a proof-of-concept and shouldn't be used in a production environment.

The idea for this is for experienced people to test and brush off any possible issues.

If you don't know how to, DO NOT TRY IT UNTIL IT'S READY AND RELEASED!!!

[/EDIT]

Following the instructions from votdev

Install OMV7 on Debian 12 (Bookworm) - Guides - openmediavault

This is what has been going on, on the Pi5:

Flashed SDcard with RaspiOS 64 Lite (Bookworm) with pre-sets for:

Hostname

Locale (PT)

SSH enabled

USER name and PASSWORD

WiFi Network configured with SSID and PASSWORD

Booted first time and accessed via SSH with no issues.

apt install screen tree

Ran commands has guide instructs on a screen session (just in case)

After reboot now, systemd network-wait-online service was taking a huge amount of time to come up and constantly reseting the time taken.

omv-firstaid showed no interfaces for the network (although I had eth0 and Internet function)

Ran local, sudo raspi-config and disabled the A2 Network Interface Names Enable/disable predictable network i/f names

After reboot now, omv-firstaid showed the eth0 interface.

Configured it again with DHCPv4 only and after reboot, systemd didn't hog up anymore.

Disabled openmediavault-issue since it hogged +6 seconds on boot.

For now, this is what is going on:

pi@raspberrypi:~ $ sudo systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

multi-user.target @10.019s
└─collectd.service @9.730s +140ms
  └─rrdcached.service @9.340s +360ms
    └─network-online.target @9.305s
      └─NetworkManager-wait-online.service @3.625s +5.679s
        └─NetworkManager.service @3.293s +328ms
          └─dbus.service @2.956s +313ms
            └─basic.target @2.935s
              └─sockets.target @2.935s
                └─triggerhappy.socket @2.935s
                  └─sysinit.target @2.934s
                    └─systemd-resolved.service @2.610s +323ms
                      └─systemd-tmpfiles-setup.service @2.519s +57ms
                        └─local-fs.target @2.500s
                          └─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @2.525s
                            └─local-fs-pre.target @1.741s
                              └─systemd-tmpfiles-setup-dev.service @1.628s +112ms
                                └─systemd-sysusers.service @1.531s +95ms
                                  └─systemd-remount-fs.service @1.433s +68ms
                                    └─systemd-journald.socket @1.128s
                                      └─system.slice @919ms
                                        └─-.slice @919ms

It's fast.

What I'm surprised is the IDLE temp even with the oficial COOLER:

pi@raspberrypi:~ $ sudo vcgencmd measure_temp
temp=47.2'C

VS my CM4 with a hacked passive cooler with mini FAN on top (not much different from the Pi5 solution)

pi@panela:~ $ sudo vcgencmd measure_temp
temp=33.1'C

ryecoaaron

All I need now, is the flashmemory plugin to continue to test the rest,

Quote from ryecoaaron

If you waited just a little bit, I was going to release an update for the install script.

Just got home yesterday and took advantage of the wife beeing at work and cat's sleeping,

This was done in a speed run and just wanted to give some details, specially of the hiccup with the systemd service.

Will try to start over but with the WiFi disabled via config.txt and with the Enabled network predictive names to see if it hogs in the same way (the systemd network-wait-online service)

Quote from ryecoaaron

I would just hold off on creating guides. We will end up a mix of install methods and I don't even have an RPi5 to add anything RPi specific. I hate making OMV 7 available to RPi users let alone RPi5 users since I don't have one.

Well, in my defense, this isn't intended as a guide (unless you're refering something different).

Just followed the instructions available to see if they would work. The idea is to then, pass any issues to Github.

And, I should have started by asking you if you had already got a hold on a Pi5 (which I can see now that the answer is NO, unfortunately)

On a different approach, I am thinking if it's possible to do the above on a Pi4:

Flash Bookworm 64bit Lite and see how it behaves VS Pi5

Quote from ryecoaaron

Just jet lagged and grumpy.

How I understand you. Imagine it every 3~4 weeks (getting too old for it)

Quote from ryecoaaron

That would help for bookworm changes but not RPi5 specific things. I will update for OMV 7 things but not doing rpi things today.

Don't fret about it. Whenever you feel up to it,

Better brush of the jet lag first,

Quote from Amanwhocan

Hi Soma,

I am new here, how do I contact you < I may have some useful infor for you regarding the Pi5

best regards

Amanwhocan

Would be best to post here so everybody could benefit of the knowledge,

votdev

I forgot to mention but I stumbled with an issue that I need to clear (although you don't run Pi nor like it, )

Doing the initial configuration of the raspiOS, my user 1000 is already on group SSH.

After running the commands you posted and having OMV7 installed, once I rebooted, my user lost access to SSH.

When I went to GUI services, SSH, the blue banner showed:

Quote

Users must be assigned to the _ssh group to be able to log in via SSH.

To my surprise, group SSH didn't exist anymore and my user couldn't login no matter what.

Went on GUI, users and added my user to the, now existing group _ssh.

After that, I regain SSH access.

Is this by design on OMV7 or just some typo anywhere?

Quote from juanmanuelbc

If any information is needed, I'm here to help in any way I can...

Thanks for sharing this.

I need to do this again from scratch to see if the "issues" that I came across will repeat.

What I see from your screenshots is:

CPU Temp is quite lower than I'm getting.

Can you tell me what you're using?

ATM, my Pi5 is just thrown inside a wood box, laying horizontal with the active cooler and the TEMP is a bit high for my taste.

Will try to put it vertical and see the outcome.

Since Raspberry Foundation still hasn't changed the way the device controls the FAN speed (several users already asked for it), I can only wait and use it as is.

My kernel version shows different (I see 2 versions of it on the /boot/firmware/)

pi@raspberrypi:~ $ sudo ls -al /boot/firmware/kerne*
-rwxr-xr-x 1 root root 8729756 Nov 15 13:50 /boot/firmware/kernel8.img
-rwxr-xr-x 1 root root 8731342 Nov 15 13:50 /boot/firmware/kernel_2712.img

pi@raspberrypi:~ $ sudo ls -al /boot/firmware/initramfs*
-rwxr-xr-x 1 root root 14277011 Nov 15 13:50 /boot/firmware/initramfs8
-rwxr-xr-x 1 root root 14276518 Nov 15 13:50 /boot/firmware/initramfs_2712

I see on your screenshot that you have the v8 in use while mine is booting with the 2712.

Did you edit anything on the config.txt by any chance?

Quote from Soma

My kernel version shows different (I see 2 versions of it on the /boot/firmware/)
Code pi@raspberrypi:~ $ sudo ls -al /boot/firmware/kerne* -rwxr-xr-x 1 root root 8729756 Nov 15 13:50 /boot/firmware/kernel8.img -rwxr-xr-x 1 root root 8731342 Nov 15 13:50 /boot/firmware/kernel_2712.img pi@raspberrypi:~ $ sudo ls -al /boot/firmware/initramfs* -rwxr-xr-x 1 root root 14277011 Nov 15 13:50 /boot/firmware/initramfs8 -rwxr-xr-x 1 root root 14276518 Nov 15 13:50 /boot/firmware/initramfs_2712

I see on your screenshot that you have the v8 in use while mine is booting with the 2712.

Did you edit anything on the config.txt by any chance?

Found the answer to this in here:
Raspberry Pi Documentation - The config.txt file

juanmanuelbc

It seems that the v8 kernel means that you are not using the proper kernel with Pi5 optimizations.

Or, at least, the boot isn't loading/choosing it for some reason.

Quote from juanmanuelbc

Hi, I started the installation of OVM 7.0 on a Raspberry Pi 4

And only now, I see Pi4 and I've been waisting my Latin...

Please, this is for Pi5 info, NOT Pi4.

Quote from juanmanuelbc

Sorry for the inconvenience

Don't stress.

Just wanted to keep this on a Pi5 only subject since it's a brand new hardware.

Nonetheless, good to see it running on Pi4,

Just consider that OMV7 isn't released yet and things can go wrong.

So, don't use it as a daily system. Just use it for testing.