Helios64 - Armbian 23.08 Bookworm issues (solved)

TDCroPower · March 7

OMV 7 is based on OS Bookworm, OMV 6 is based on OS Bullseye.

If 6.6.21 is Bookworm you can go to OMV 7

bigheart · March 8

thanks!

is there anywhere i can download current release other than the minimal?

or only minimal is avaliable for current release

TDCroPower · March 8

why do you want to use a current one when @ebin-dev has put together a stable one?

if you have a Helios64 I would definitely recommend installing the image compilation from @ebin-dev, it has been running very well here for weeks and I will soon roll it out to my productive Helios64.

magostinelli · March 10

Hello,

my current Helios64 setup is running on armbian buster, and i want to update it to lastest stable release.

I found this topic, and it says to boot from a new sd operating system, can i update my system inline?

Thanks.

ebin-dev · March 10

3 hours ago, magostinelli said:

can i update my system inline?

You can try to upgrade from buster to bullseye. Unfortunately your mileage may vary. It may or may not work depending on circumstances.

This is why Armbian moderators always post messages like "user space upgrades are not supported" ...

magostinelli · March 10

Thanks, i read in this comment a complex guide to install the system (firware files, etc), it is needed also for inline upgrade?

I suppose if anything goes wrong i can proceed in the recommended way, so before starting I will backup my system settings and customization, so i will able to redo a restore.

TDCroPower · March 11

@magostinelli I would always recommend a new installation for a release jump, especially if you currently have to go from Buster to Bullseye and than to Bookworm.
I have therefore written the instructions for @ebin-dev in more detail so that the reinstallation is not so complex.
It looks more complex than it is in the end

magostinelli · March 12

I have no problem with the command line, I'm lazy , that's all.

So I will do a list of all my service and configuration (i have already done a backup), so i will proceed with a clean install.

I see there is an update Armbian image for Helios, may it includes the files you mentioned in your guide?

Edited March 12 by magostinelli

grek · March 12

I installed Armbian_23.5.4_Helios64_bookworm_current_6.1.36 and kernel helios64 6.6.8-edge-rockchip64.

Generally it is ok. First from long time I do not need to limit my sata to 3gbit , and I using cpu governor : on demand with min: 408000 max: 1200000 . ,instead of performance 1416000

My configuration its little specific because Im using LUKS crypt on top of my ZFS mirror (2x 4TB) + 1 cache SSD + 2 hdd EXT4 encrypted with ZFS.

I tested NFS yesterday , and I successfully downloaded ~ 700GB without any errors .

only what is not working as expected, that running sbc-bench.sh , causing kernel panic . ( http://sprunge.us/3VLJNX )

I will still test it, but it good point to start.

[ 3500.389590] Internal error: Oops: 0000000086000004 [#1] PREEMPT SMP
[ 3500.390166] Modules linked in: governor_powersave governor_performance dm_crypt trusted asn1_encoder nfsv3 nfs fscache netfs rfkill lz4hc lz4 zram binfmt_misc zfs(PO) spl(O) snd_soc_hdmi_codec snd_soc_rockchip_i2s crct10dif_ce rockchip_vdec(C) hantro_vpu snd_soc_core rockchip_rga v4l2_vp9 leds_pwm snd_compress v4l2_h264 ac97_bus videobuf2_dma_contig v4l2_mem2mem snd_pcm_dmaengine videobuf2_dma_sg snd_pcm pwm_fan panfrost gpu_sched gpio_charger drm_shmem_helper videobuf2_memops videobuf2_v4l2 snd_timer rk_crypto videodev snd videobuf2_common nvmem_rockchip_efuse mc soundcore gpio_beeper ledtrig_netdev nfsd lm75 auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 efivarfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear cdc_ncm cdc_ether usbnet r8152 rockchipdrm realtek dw_mipi_dsi dw_hdmi analogix_dp fusb302 drm_display_helper tcpm cec typec dwmac_rk stmmac_platform drm_dma_helper drm_kms_helper stmmac drm adc_keys pcs_xpcs
[ 3500.398227] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P         C O       6.6.8-edge-rockchip64 #1
[ 3500.399007] Hardware name: Helios64 (DT)
[ 3500.399362] pstate: 000000c5 (nzcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 3500.399988] pc : psi_group_change+0xc8/0x358
[ 3500.400388] lr : psi_task_change+0x8c/0xbc
[ 3500.400767] sp : ffff80008203bd60
[ 3500.401069] x29: ffff80008203bd70 x28: ffff800075e65000 x27: ffff800081cac8e8
[ 3500.401720] x26: ffff800081909d40 x25: 0000000000000000 x24: ffff800081907008
[ 3500.402368] x23: 0000000000000001 x22: 0000000000000000 x21: 0000000000000000
[ 3500.403015] x20: ffff0000f776ed40 x19: 0000000000000004 x18: 0000000000000000
[ 3500.403662] x17: ffff800075e65000 x16: ffff800082038000 x15: 0000000000000001
[ 3500.404309] x14: 0000000000000000 x13: ffff800081581d50 x12: ffff800081c89b68
[ 3500.404957] x11: 0000000000000040 x10: 0000000000000004 x9 : 0000032eff793e13
[ 3500.405605] x8 : ffff800081c8dd28 x7 : 0000000000000000 x6 : 000000001c036006
[ 3500.406252] x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000001
[ 3500.406898] x2 : 0000000000000001 x1 : 0000000000000004 x0 : ffff0000f776ed40
[ 3500.407545] Call trace:
[ 3500.407771]  psi_group_change+0xc8/0x358
[ 3500.408131]  psi_task_change+0x8c/0xbc
[ 3500.408479]  activate_task+0xcc/0x128
[ 3500.408818]  ttwu_do_activate+0x58/0x274
[ 3500.409180]  sched_ttwu_pending+0xe4/0x1c0
[ 3500.409557]  __flush_smp_call_function_queue+0x14c/0x458
[ 3500.410042]  generic_smp_call_function_single_interrupt+0x14/0x20
[ 3500.410594]  ipi_handler+0x84/0x250
[ 3500.410920]  handle_percpu_devid_irq+0xa4/0x230
[ 3500.411337]  generic_handle_domain_irq+0x2c/0x44
[ 3500.411756]  gic_handle_irq+0x50/0x128
[ 3500.412097]  call_on_irq_stack+0x24/0x4c
[ 3500.412458]  do_interrupt_handler+0xd4/0xd8
[ 3500.412842]  el1_interrupt+0x34/0x68
[ 3500.413173]  el1h_64_irq_handler+0x18/0x24
[ 3500.413548]  el1h_64_irq+0x64/0x68
[ 3500.413860]  cpuidle_enter_state+0xc0/0x4bc
[ 3500.414246]  cpuidle_enter+0x38/0x50
[ 3500.414577]  do_idle+0x1fc/0x270
[ 3500.414878]  cpu_startup_entry+0x38/0x3c
[ 3500.415238]  secondary_start_kernel+0x128/0x148
[ 3500.415653]  __secondary_switched+0xb8/0xbc
[ 3500.416043] Code: 54fffec1 52800002 52800024 34000173 (8b224a80) 
[ 3500.416592] ---[ end trace 0000000000000000 ]---
[ 3500.417009] Kernel panic - not syncing: Oops: Fatal exception in interrupt
[ 3500.417621] SMP: stopping secondary CPUs
[ 3500.418110] Kernel Offset: disabled
[ 3500.418425] CPU features: 0x1,00000208,3c020000,1000421b
[ 3500.418903] Memory Limit: none
[ 3500.419192] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]---

TDCroPower · March 12

@grek if you install the other things from @ebin-dev, then you can also use the sbc-bench.sh script.

Look to my instructions for that...

ebin-dev · March 12

9 hours ago, grek said:

I installed Armbian_23.5.4_Helios64_bookworm_current_6.1.36 and kernel helios64 6.6.8-edge-rockchip64.

Generally it is ok. First from long time I do not need to limit my sata to 3gbit , and I using cpu governor : on demand with min: 408000 max: 1200000 . ,instead of performance 1416000

My configuration its little specific because Im using LUKS crypt on top of my ZFS mirror (2x 4TB) + 1 cache SSD + 2 hdd EXT4 encrypted with ZFS.

I tested NFS yesterday , and I successfully downloaded ~ 700GB without any errors .

NFS is known to cause problems with kernel 6.6.8. It would probably be wise to switch to 6.1.71 or 5.15.93 in your case.

magostinelli · March 12

This is the last version released from here https://www.armbian.com/helios64/:

https://github.com/armbian/community/releases/download/24.5.0-trunk.168/Armbian_community_24.5.0-trunk.168_Helios64_bookworm_current_6.6.21_minimal.img.xz

ebin-dev · March 16

On 3/12/2024 at 10:11 PM, magostinelli said:

This is the last version released from here https://www.armbian.com/helios64/:

https://github.com/armbian/community/releases/download/24.5.0-trunk.168/Armbian_community_24.5.0-trunk.168_Helios64_bookworm_current_6.6.21_minimal.img.xz

Did you test that image ?

None of the Armbian built 6.6.x (x >8) kernels (downloadable on beta.armbian.com) are stable on my system. They all seem to have the same issue.

magostinelli · March 17

Not yet. I'm doing a list of software, configuration, customize of my current installation. I'm also searching for a spare sd card to make a try.

magostinelli · March 20

I tryed today, the system boot correctly but it freezes during first wizard, i tried two times, same error.

So what do you suggest?

EDIT: after third try, the system now is working (via microsd boot)

Edited March 20 by magostinelli

TDCroPower · March 20

@ebin-dev I tried to transfer my installation to my productive helios64 installation today, but unfortunately I still get...

Segmentation fault
free(): invalid pointer

... but here i am using a m.2 ssd on sata1 for the filesystem
What should the "dd" commands look like in this setup?

Here is the output of the volumes ...

root@helios64:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            1.8G  8.3M  1.8G   1% /dev
tmpfs           380M  6.0M  374M   2% /run
/dev/sda1       117G  3.1G  108G   3% /
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/mmcblk0p1   15G  182M   14G   2% /media/mmcboot
tmpfs           1.9G     0  1.9G   0% /tmp
/dev/zram1       47M  556K   43M   2% /var/log
tmpfs           380M     0  380M   0% /run/user/0

root@helios64:~# lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
sda            8:0    0 119.2G  0 disk
└─sda1         8:1    0 119.2G  0 part  /var/log.hdd
                                        /
sdb            8:16   0   3.6T  0 disk
└─md127        9:127  0   7.3T  0 raid5
sdc            8:32   0   3.6T  0 disk
└─md127        9:127  0   7.3T  0 raid5
sdd            8:48   0   3.6T  0 disk
└─md127        9:127  0   7.3T  0 raid5
mmcblk0      179:0    0  14.6G  0 disk
└─mmcblk0p1  179:1    0  14.4G  0 part  /boot
                                        /media/mmcboot
mmcblk0boot0 179:32   0     4M  1 disk
mmcblk0boot1 179:64   0     4M  1 disk
zram0        252:0    0   1.9G  0 disk  [SWAP]
zram1        252:1    0    50M  0 disk  /var/log
zram2        252:2    0     0B  0 disk

ebin-dev · March 20

8 hours ago, magostinelli said:

EDIT: after third try, the system now is working (via microsd boot)

I observed the same issues you describe (freezing shortly after the first script is manually started) and I would like to understand why it seems to be stable after your third attempt.

Could you post the messages output during boot ? Does it start with 'DDR Version 1.25 20210517' ?

ebin-dev · March 20

On 3/20/2024 at 1:04 PM, TDCroPower said:

What should the "dd" commands look like in this setup?

I am using the following script to transfer a system to another volume (in this case the running system to emmc) (UUIDs to be adapted to your case (sed -e 's/UUID=<from device>/UUID=<to device>/g' -i /mnt/emmc/etc/fstab)

#!/bin/bash

# Check if user is root
if [ $(id -u) != "0" ]; then
    echo "Error: You must be root to run this script."
    exit 1
fi

cat > install-exclude <<EOF
/dev/*
/proc/*
/sys/*
/run/*
# /tmp/*
# /root/*
EOF

exec 2>/dev/null
umount /mnt/emmc
exec 2>&1

mount  --uuid 7268e76f-3e1b-4e01-a6be-987654321098 /mnt/emmc

rsync -avxSE --delete --exclude-from="install-exclude"  /  /mnt/emmc

# change fstab
sed -e 's/UUID=b790c4d7-5709-4000-91ac-123456789012/UUID=7268e76f-3e1b-4e01-a6be-987654321098/g' -i /mnt/emmc/etc/fstab
sed -e 's/UUID=b790c4d7-5709-4000-91ac-123456789012/UUID=7268e76f-3e1b-4e01-a6be-987654321098/g' -i /mnt/emmc/boot/armbianEnv.txt
umount /mnt/emmc
rm install-exclude

echo "All done."

On top of that you may wish to manually rsync /var/log and /var/log.hdd to the other device.

The segmentation fault is probably caused by the wrong bootloader on emmc. Armbian tools might overwrite it. So install again the recommended bootloader to emmc.

Good luck.

Edited March 21 by ebin-dev

TDCroPower · March 21

@ebin-dev thanks for the script, i will try it.

But you have 3 different UUID in the script...

first one 7268e76f-3e1b-4e01-a6be-123456789012 ...

mount  --uuid 7268e76f-3e1b-4e01-a6be-123456789012 /mnt/emmc

the second b790c4d7-5709-4000-91ac-123456789012 and the third 7268e76f-3e1b-4e01-a6be-987654321098 ...

sed -e 's/UUID=b790c4d7-5709-4000-91ac-123456789012/UUID=7268e76f-3e1b-4e01-a6be-987654321098/g' -i /mnt/emmc/etc/fstab

the mount one is the "to device" or it is an another?

here are my uuid's...

root@helios64:~# blkid
/dev/sdd: UUID="29f2832b-d95d-3e76-0375-3b2b0f0xxxxx" UUID_SUB="e187038d-7022-19b6-ac81-2f7dd80b2dae" LABEL="helios64:0" TYPE="linux_raid_member"
/dev/md127: LABEL="nas" UUID="b5c52051-e75f-408c-a7af-4a5d0daxxxxx" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdb: UUID="29f2832b-d95d-3e76-0375-3b2b0fxxxxx" UUID_SUB="914413d8-94a7-a983-6c96-7ae639f85ad2" LABEL="helios64:0" TYPE="linux_raid_member"
/dev/mmcblk0p1: LABEL="armbi_root" UUID="b790c4d7-5709-4000-91ac-099eeefxxxxx" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="188abe42-01"
/dev/sdc: UUID="29f2832b-d95d-3e76-0375-3b2b0fxxxxx" UUID_SUB="dbef45c4-9262-371c-fa47-b5efccc1b384" LABEL="helios64:0" TYPE="linux_raid_member"
/dev/mmcblk1p1: UUID="e4d8315e-aeb2-4e95-becf-88aaed8xxxxx" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="f11f8806-01"
/dev/sda1: UUID="902f758f-240c-4f5a-b802-5ab5d35xxxxx" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0182fc84-01"
/dev/zram1: LABEL="log2ram" UUID="299a178d-7269-46e4-988c-f691813xxxxx" BLOCK_SIZE="4096" TYPE="ext4"
/dev/zram0: UUID="cab32334-75a4-4fda-b539-b17a55dxxxxx" TYPE="swap"

Edited March 21 by TDCroPower

ebin-dev · March 21

The uuids containing 'a6be' refer to the 'to device', the ones containing '91ac' refer to the 'from device'.

Edited March 21 by ebin-dev

magostinelli · March 22

i'm sorry, but I can't find the reply button on the forum.

In any case, @ebin-dev I don't have any monitor connected do the NAS.

The only stable kernel i found is the 6.1.63 (whith this image Armbian_23.11.1_Helios64_bookworm_current_6.1.63.img.xz).

My third try was ok, because the freeze is random, so sometis it occurs after 5 minutes, so you can configure the system.

Edit: I confirm that kenrel 6.1.63 is stable for me. The 6.1 is an LTS version, why isn't update in armbian?

https://endoflife.date/linux

Edited March 22 by magostinelli

SteeMan · March 22

12 hours ago, magostinelli said:

Edit: I confirm that kenrel 6.1.63 is stable for me. The 6.1 is an LTS version, why isn't update in armbian?

Armbian doesn't have a process to make regular releases to kernels in the stable channel.

magostinelli · March 23

Ok, I understand, But with the latest kernel the system freeze. Anyone here has a stable kernel (without freeze) to suggest?

Thanks!

TDCroPower · March 24

@ebin-dev I got it to work with the armbian tools, but before it wanted to shut down the system at the last query, I ran the dd commands again.

Unfortunately the transfer did not work with your script, the rsync command ran in a continuous loop.
Now it worked with the tests after booting via eMMC and SSD.

Strangely enough, however, I am now again having considerable problems with the installation of OMV and subsequent operation.
The system simply freezes and restarts during some runs.
I didn't have this with the other Helios64 device.

I'll test installing everything via microSD to see if the same unstable symptoms can be observed.

bigheart · March 24

i am also experienced multiple system freeze event (when it happen all HDD and system LED are all ON on the front penal), the kernel is 6.6.22-current-rockchip64.

strange enough i found the syslog in /var/log is empty.

ebin-dev · March 24

1 hour ago, bigheart said:

i am also experienced multiple system freeze event (when it happen all HDD and system LED are all ON on the front penal), the kernel is 6.6.22-current-rockchip64.

Depending on your use case try kernel 6.6.8, 6.1.71, and 5.15.93 (download links are provided here).

Armbian built kernels 6.6.x (x>8) are all unstable.

TDCroPower · March 24

Can I actually remove the 6.1.36 files?
Since it links to the 6.6.8-edge, the old ones are unused, right?

root@helios64:~# ll /
total 60
lrwxrwxrwx   1 root root     7 Jun 18  2023 bin -> usr/bin
drwxr-xr-x   4 root root  4096 Mar 24 12:41 boot
drwxr-xr-x  21 root root  4760 Mar 24 12:41 dev
drwxr-xr-x  99 root root  4096 Mar 24 12:41 etc
drwxr-xr-x   6 root root  4096 Mar 20 12:01 home
lrwxrwxrwx   1 root root    37 Feb 22 10:35 initrd.img -> boot/initrd.img-6.6.8-edge-rockchip64
lrwxrwxrwx   1 root root    33 Jun 30  2023 initrd.img.old -> boot/initrd.img-6.1.36-rockchip64
lrwxrwxrwx   1 root root     7 Jun 18  2023 lib -> usr/lib
drwx------   2 root root 16384 Jun 30  2023 lost+found
drwxr-xr-x   2 root root  4096 Jun 18  2023 media
drwxr-xr-x   9 root root  4096 Mar 23 20:19 mnt
drwxr-xr-x   3 root root  4096 Mar 20 12:09 opt
dr-xr-xr-x 293 root root     0 Mar 24 12:41 proc
drwx------   6 root root  4096 Mar 23 20:13 root
drwxr-xr-x  30 root root   880 Mar 24 12:47 run
lrwxrwxrwx   1 root root     8 Jun 18  2023 sbin -> usr/sbin
drwxrwxr-x   2 root root  4096 Jun 30  2023 selinux
drwxr-xr-x   4 root root  4096 Mar 20 12:15 srv
dr-xr-xr-x  13 root root     0 Mar 24 12:41 sys
lrwxrwxrwx   1 root root    42 Mar 24 12:41 thermal_zone0 -> /sys/devices/virtual/thermal/thermal_zone0
drwxrwxrwt  10 root root   200 Mar 24 12:42 tmp
drwxr-xr-x  11 root root  4096 Jun 18  2023 usr
drwxr-xr-x  13 root root  4096 Feb 22 09:51 var
lrwxrwxrwx   1 root root    34 Feb 22 10:35 vmlinuz -> boot/vmlinuz-6.6.8-edge-rockchip64
lrwxrwxrwx   1 root root    30 Jun 30  2023 vmlinuz.old -> boot/vmlinuz-6.1.36-rockchip64

root@helios64:~# ll /boot/
total 167948
-rw-r--r-- 1 emby emby      166 Mar 24 12:41 armbianEnv.txt
-rw-r--r-- 1 root root     1536 Jun 30  2023 armbian_first_run.txt.template
-rw-r--r-- 1 root root    38518 Jun 30  2023 boot.bmp
-rw-r--r-- 1 emby emby     3180 Jun 12  2023 boot.cmd
-rw-rw-r-- 1 root root     3252 Jun 30  2023 boot.scr
-rw-r--r-- 1 root root   238799 Jun 28  2023 config-6.1.36-rockchip64
-rw-r--r-- 1 root root   258775 Dec 20 18:58 config-6.6.8-edge-rockchip64
lrwxrwxrwx 1 root root       25 Feb 22 10:33 dtb -> dtb-6.6.8-edge-rockchip64
drwxr-xr-x 3 root root     4096 Jun 30  2023 dtb-6.1.36-rockchip64
drwxr-xr-x 3 root root     4096 Feb 22 10:33 dtb-6.6.8-edge-rockchip64
lrwxrwxrwx 1 root root       29 Feb 22 10:39 Image -> vmlinuz-6.6.8-edge-rockchip64
-rw-r--r-- 1 root root 22339789 Jun 30  2023 initrd.img-6.1.36-rockchip64
-rw-r--r-- 1 root root 27251745 Feb 22 10:39 initrd.img-6.6.8-edge-rockchip64
-rw-r--r-- 1 root root  4801937 Jun 28  2023 System.map-6.1.36-rockchip64
-rw-r--r-- 1 root root  5251808 Dec 20 18:58 System.map-6.6.8-edge-rockchip64
lrwxrwxrwx 1 root root       29 Feb 22 10:39 uInitrd -> uInitrd-6.6.8-edge-rockchip64
-rw-r--r-- 1 root root 22339853 Jun 30  2023 uInitrd-6.1.36-rockchip64
-rw-r--r-- 1 root root 27251809 Feb 22 10:39 uInitrd-6.6.8-edge-rockchip64
-rw-r--r-- 1 root root 29331968 Jun 28  2023 vmlinuz-6.1.36-rockchip64
-rw-r--r-- 1 root root 32815616 Dec 20 18:58 vmlinuz-6.6.8-edge-rockchip64

ebin-dev · March 24

The old files can of course be deleted in / , /boot , /usr/src , and in /lib/modules .

TDCroPower · March 24

@ebin-dev ok great, this gives me a clean installation and no unnecessary leftovers lying around.

TDCroPower · March 24

I think I found something in the install script of omv that may be causing the problems.
The script changes the CPU min/max frequency and the governor, which is known to be fatal with a Helios64!

Spoiler

[...]
confCmd="omv-salt deploy run"
cpuFreqDef="/etc/default/cpufrequtils"
crda="/etc/default/crda"
[...]
if [ ${armbian} -eq 1 ]; then
  systemctl unmask systemd-networkd.service 2>&1 | tee -a ${logfile}
  # save off cpuFreq settings before installing the openmediavault
  if [ -f "${cpuFreqDef}" ]; then
    . ${cpuFreqDef}
    gov="${GOVERNOR}"
    minspd="${MIN_SPEED}"
    maxspd="${MAX_SPEED}"
  fi
fi
[...]
# governor and speed variables
if [ ${armbian} -eq 1 ]; then
  if [ -n "${defaultGov}" ]; then
    GOVERNOR="${defaultGov,,}"
  elif [ -n "${gov}" ]; then
    GOVERNOR="${gov}"
  fi
  if [ -n "${minspd}" ]; then
    MIN_SPEED="${minspd}"
  fi
  if [ -n "${maxspd}" ]; then
    MAX_SPEED="${maxspd}"
  fi
elif [ -f "${cpuFreqDef}" ]; then
  . ${cpuFreqDef}
else
  if [ -z "${DEFAULT_GOV}" ]; then
    defaultGov="ondemand"
  fi
  GOVERNOR=${defaultGov,,}
  MIN_SPEED="0"
  MAX_SPEED="0"
fi
[...]
# update config files
${confCmd} nginx phpfpm samba flashmemory ssh chrony timezone monit rrdcached collectd cpufrequtils apt watchdog 2>&1 | tee -a ${logfile}
[...]
if [ ! "${GOVERNOR,,}" = "schedutil" ]; then
  _log "Add a cron job to make NAS processes more snappy and silence rsyslog"
  cat << EOF > /etc/rsyslog.d/omv-armbian.conf
:msg, contains, "omv-ionice" ~
:msg, contains, "action " ~
:msg, contains, "netsnmp_assert" ~
:msg, contains, "Failed to initiate sched scan" ~
EOF

the omv install script can be found under...

https://raw.githubusercontent.com/OpenMediaVault-Plugin-Developers/installScript/master/install

edit:

ok it's totally crazy, now the omv installation went through without any problems.
However, I am surprised that I saw the following cpufrequtils during the failed installation...
GOVERNOR="schedutil"
MAX_SPEED="0"
MIN_SPEED="0"

so now I'll test it again with eMMC + SSD, hope it runs smoothly this time!

edit2:

the same again, in the middle of the installation of omv the helios64 restarts and has the following cpufrequtils content...

root@helios64:~# cat /etc/default/cpufrequtils
ENABLE="true"
GOVERNOR="schedutil"
MAX_SPEED="0"
MIN_SPEED="0"

Why does it only work with eMMC + eMMC but not with eMMC + SSD?

I just don't see what the cause is.
The sbc-bench script ran before without any problems and the check with...

for i in $(seq 1 100);do python3 -c "import pkg_resources" || break;done

... was without any problems.

Edited March 25 by TDCroPower

Sign In

Helios64 - Armbian 23.08 Bookworm issues (solved)

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation

Important Information