FredK

@helios4user12 > I updated the sd card with the provided image via dd. Will this be a one time thing? Yes. In the meantime there were further updates and my Helios4 is still going strong.

@Igor After @Mangix's post I was able to fix my installation patching the bootloader. I'm aware that Helios4 is a dead-end and I plan to switch to a 64bit-SBC providing 4 or 5 SATA-ports (but I don't find a suitable board up to now).

@Mangix Thank you, that was simple. @Dee2022 What I did: Download of the 1st SolidRun image (... sd.kwb) Copy the image to SDcard containing unbootable Armbian 25.2 (on my Linux desktop using dd, SDcard available here at /dev/sdf) sudo dd if=u-boot-helios-4-sd.kwb of=/dev/sdf bs=512 seek=1 status=noxfer sudo sync Boot Helios4. Voilà.

@Igor Is a new update to 25.2 for Helios4 planned of the kernel binaries ? If so, when can this be expected? If not, what can I do? The post of @Josua-SR is marked as solution. But I have no idea what to do with the *.kwb files from SolidRun. In particular I never made a custom build.

Same here: "No boot after upgrade to Armbian 25.2.2". Same message: Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid The very "unfriendly" behaviour was the unattended-upgrade. Therefore I had no chance first to make an update of my 24.11 system with Linux 6.6.63-current-mvebu (see signature). I had to use for recovery the backup from 24.8 immediately before 24.11 in the pipeline. The recovered system is now Armbian 24.8 with Linux 6.6.47-current-mvebu. Any chance to get 24.11 again?

@pegamonstro I'm using a very similar configuration (see signature) but as a part of OMV. Last February I performed the upgrade to bookworm and OMV7 without any severe problem worth mentioning. mdadm and /proc/mdstat were present. The multiple device /dev/md0 is now present as /dev/md127. Perhaps it would help to install OMV7 to see whether your RAID5 can be recovered using OMV storage management.

@Igor Thank you for your comment and caveat. SATA port multiplication is definitely a no-go for my application (OMV6 + RAID5 with 4 8TB HDD). Is there any Armbian-based recommendation supporting 4 SATA ports "natively"? I want to avoid to go away from Armbian and looking for for a Mini-ITX based configuration (e.g. Intel N100).

I (still) use Helios4 which has been downgraded to "Community maintained" recently after Armbian 23.8.1. I'm aware that I have to migrate to a different HW later in 2025 because It's getting more difficult every day to deal with a 32-bit system using OMV (plus some docker based services) with Armbian. Question: Is there any good advice for a 64-bit HW supported by Armbian and (at least) 4 SATA ports?

bullseye is alive again.

Thank you and waiting for the re-creation ....

Support for bullseye dropped?

@Werner In Armbian Leaflet #8 from June 8th we read (bold typing by me): Now we are in week 5. Any news about Helios4 23.05 Bookworm?

@SvenHz Thank you to link to your work from last Friday. I decided for me to stay with bullseye until the repository update will be re-activated.

@SteeMan Thank you. The leaflet #8 explains the release situation sufficiently.

I'm using Armbian 23.02.2 Bullseye with Linux 5.15.93-mvebu and OMV6. I want to upgrade to Armbian 23.5.1 Bookworm with Linux 6.1.30. Up to now no upgrade is offered. If the answer to the thread title is "yes" I need help how to do the upgrade. If the answer is "no" I kindly ask for information about the reason not to be able to upgrade. By the way: Helios4 is a maintained platform, maintainer is @Heisath

@SteeMan Thank you for your explanation. I'll keep patient.

I'm using 22.11.4 Bullseye on Helios4. 23.02.2 is available in dl.armbian.com (and mirrored) since Feb 18th. But an upgrade of my installation is not possible because apt.armbian.com/dists is from Feb 12th (all mirrors) for all supported platforms (not only Helios4). It could be that the problem is related to last year's problem discussed in https://forum.armbian.com/topic/19982-how-to-upgrade-to-2202/ (aptly?).

@Kribbstar Some facts from my configuration, in general: Nothing fancy here. OS: Linux 5.15.89-mvebu + Armbian 22.11.4 (up-to-date) NAS: OMV 6.2.0 + omvextrasorg 6.1.1 (up-to-date) + RAID5 (4 * 8TB WD Red) Filesystems: type=ext4*, 3 fs, one of them LUKS-encrypted Shared foldes (5) provided bei SMB/CIFS omv-extras: docker, portainer, yacht Container: nextcloud (supported by nextclouddb and swag) Backup: a) SD-card cloning, b) rsync ext4*: I started with ext4 because of no own experience with btrfs, zfs, ... But because the configuration is stable and sufficiently responsive, I stayed with ext4. Any further information you are interested in?

Straightforward! See signature. Thanks to the team.

Update successful, see my signature. Thank you.

@Heisath Unfortunately I am not able to build a new kernel applying your patch. Sorry. But I will test the new kernel after release asap. OTOH I can live with the situation that from time to time the fancontrol doesn't work. Now I know what to do (using last working alternative kernel) and reporting the fact here in the forum or within discord. EDIT: I see that the patch has been committed and merged.

@Igor Thank you for the explanation. Let's see what will happen at the next kernel update. Maybe @Heisath has an idea/solution preventing the problem in future updates?

Same effect here. After applying the workaround by @Igor - now I'm back at 22.08.2/5.15.69 - fancontrol is working again. Any patch for 22.08.4 or an upstream solution to be expected?

System successfully upgraded. No problems detected (so far). Thanks to the team.