OMV 7 install on Helios64 fails

Zitat von TDCroPower

Why is the cpu frequency changed at all during the OMV installation?

The install is trying not to change them. Armbian puts the settings in /etc/default/cpufrequtils (as you said) but this is not what OMV's saltstack code uses for a source of truth. So, the script tries to read /etc/default/cpufrequtils on all Armbian installs and write them to OMV's default overrides allowing saltstack to rewrite /etc/default/cpufrequtils to the original values.

Zitat von TDCroPower

Is this really necessary or can it be left to the user's settings so that these changes do not occur?

If the script doesn't do this, OMV will change them to the values you saw. I'm not sure where things went wrong on your install. I will have to try an armbian install.

Zitat von TDCroPower

nd during this script part, i.e. the omv installation, the file is changed...

Weird, I guess I need to move the armbian setting collection before the OMV install then.

Actually, the install script is already doing that - https://github.com/OpenMediaVa…/blob/master/install#L286

I will have to try an install.

that command just rewrites the /etc/hosts file. What makes you think that is bad?

Zitat von TDCroPower

is just a thought when the wrong "0" values are written or who is responsible for the output at that time...

Code

/usr/lib/python3/dist-packages/salt/utils/pycrypto.py:26: DeprecationWarning: 'crypt' is deprecated and slated for removal in Python 3.13
  import crypt
/usr/lib/python3/dist-packages/salt/modules/linux_shadow.py:21: DeprecationWarning: 'spwd' is deprecated and slated for removal in Python 3.13
  import spwd
Deploying service configurations ... <<<<< here !?
Processing system modifications ... <<<<< or here !?

These lines are written by the postinst script of the openmediavault package.

• https://github.com/openmediava…nmediavault.postinst#L245
  
• https://github.com/openmediava…nmediavault.postinst#L255
  

Zitat von TDCroPower

We (Helios64 owners) are currently experiencing significant problems when we try to use the script from...

https://github.com/OpenMediaVa…Script/raw/master/install

... to install the current OMV 7 on a Armbian Bookworm system.

At the following point...

Code

/usr/lib/python3/dist-packages/salt/grains/core.py:2711: DeprecationWarning: Use setlocale(), getencoding() and getlocale() instead
  ) = locale.getdefaultlocale()
/usr/lib/python3/dist-packages/salt/grains/core.py:2711: DeprecationWarning: Use setlocale(), getencoding() and getlocale() instead
  ) = locale.getdefaultlocale()
/usr/lib/python3/dist-packages/salt/utils/pycrypto.py:26: DeprecationWarning: 'crypt' is deprecated and slated for removal in Python 3.13
  import crypt
/usr/lib/python3/dist-packages/salt/modules/linux_shadow.py:21: DeprecationWarning: 'spwd' is deprecated and slated for removal in Python 3.13
  import spwd
Deploying service configurations ... <<<<< here !?
Processing system modifications ... <<<<< or here !?

... the cpu frequency from the following value...

Code

# cat /etc/default/cpufrequtils
ENABLE="true"
GOVERNOR="ondemand"
MAX_SPEED="1200000"
MIN_SPEED="408000"

... is changed to this value...

Code

$ cat /etc/default/cpufrequtils
ENABLE="true"
GOVERNOR="schedutil"
MAX_SPEED="0"
MIN_SPEED="0"

the cpu frequency is then written back at the following point...

Code

              ----------
                        ID: sync_modules
                  Function: saltutil.sync_modules
                    Result: True
                   Comment: Updated modules.
                   Started: 23:12:40.830096
                  Duration: 1119.591 ms
                   Changes:
                            ----------
                            modules:
                                - modules.omv_conf
                                - modules.omv_utils

              Summary for helios64
              ------------
              Succeeded: 4 (changed=4)
              Failed:    0
              ------------
              Total states run:     4
              Total run time:   3.700 s

Summary for helios64
------------
Succeeded: 6 (changed=5)
Failed:    0
------------
Total states run:     6
Total run time:  22.648 s

Alles anzeigen

... and then the Helios64 automatically reboots and the installation is faulty.

The question remains with us...

Why is the cpu frequency changed at all during the OMV installation?

Is this really necessary or can it be left to the user's settings so that these changes do not occur?

Alles anzeigen

The file is modified because it is under the control of OMV. If you want to use custom settings, then you need to set the environment variables that you can find here: https://github.com/openmediava…/files/cpufrequtils.j2#L1

Zitat von ryecoaaron

The install is trying not to change them. Armbian puts the settings in /etc/default/cpufrequtils (as you said) but this is not what OMV's saltstack code uses for a source of truth. So, the script tries to read /etc/default/cpufrequtils on all Armbian installs and write them to OMV's default overrides allowing saltstack to rewrite /etc/default/cpufrequtils to the original values.

If the script doesn't do this, OMV will change them to the values you saw. I'm not sure where things went wrong on your install. I will have to try an armbian install.

I see Aaron has already explained the behaviour in detail.

Zitat von TDCroPower

Have you found a solution to the problem in the meantime?

No but you could just use the skip reboot flag on the install script, set the cpufreq frequencies (the ones below are wrong because I didn't look up what they are) and reboot.

sudo omv_set_default "OMV_CPUFREQUTILS_GOVERNOR" "performance"

sudo omv_set_default "OMV_CPUFREQUTILS_MINSPEED" "1000"

sudo omv_set_default "OMV_CPUFREQUTILS_MAXSPEED" "2000"

sudo omv-salt stage run prepare

sudo omv-salt deploy run cpufrequtils

Zitat von TDCroPower

We (Helios64 owners) are currently experiencing significant problems when we try to use the script from...

https://github.com/OpenMediaVa…Script/raw/master/install

... to install the current OMV 7 on a Armbian Bookworm system.

You have to realize that you're using an unsupported "automated" Armbian build for Dev's only. Those builds are untested and unsupported, by Armbian and OMV. BTW: I'm in the same boat with an older SBC, the Rock64.

This is the CLI logon for the Rock64 and this is what you're seeing as well:

While I understand trying to get use some out of an older more specialized SBC, in the bottom line, it's not supported.