FredK
Members-
Posts
57 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by FredK
-
@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?
-
Succes! Helios4 23.05 Bookworm with ZFS and working fan control
FredK replied to SvenHz's topic in Marvell mvebu
@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
-
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.
-
Fancontrol service fails to start with kernel version 5.15.72
FredK replied to ef15c's topic in Marvell mvebu
Update successful, see my signature. Thank you. -
Fancontrol service fails to start with kernel version 5.15.72
FredK replied to ef15c's topic in Marvell mvebu
@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. -
Fancontrol service fails to start with kernel version 5.15.72
FredK replied to ef15c's topic in Marvell mvebu
@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? -
Fancontrol service fails to start with kernel version 5.15.72
FredK replied to ef15c's topic in Marvell mvebu
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? -
Upgrade to 22.05.3 successful also.
-
System successfully upgraded. No problems detected (so far). Thanks to the team.
-
@Igor I just used http://imola.armbian.com/apt for the upgrade and at the end the system rebooted successfully (Linux 5.15.25-mvebu | Armbian 22.02.1). Thank you for your help. I conclude that I'm the only one on any platform to upgrade a running system to 22.02 now using apt-get. Or, is there any other method for upgrading without starting from scratch with a release package?
-
@Heisath > Seems weird or really kinda broken. Its been now 5days(?) since release If I have a look at any mirror the situation is: - The "dl" subtree is up-to-date. - The "apt/pool" subtree is up-to-date. - The "apt/dists" (where apt-get is looking for updates) subtree is of Feb 1st.
-
@Heisath Thank you for your clarification. Than I practice patience until the repo rebuild will be completed. In the meantime I'm observing the build train #267.
-
@Werner Because this problem is a generic one and affects all supported platforms, I recommend to move this thread to a more general and more active forum. The question is: How to upgrade bullseye from armbian 21.08.8 to armbian 22.02.1 via apt as long as the apt/dists branch of a armbian mirror is frozen at Feb 1st 2022? Thank you in advance
-
@Werner @Heisath According to https://docs.armbian.com/Release_Board-Maintainers heisath is the maintainer for helios4 and the new release is available at <mirror>/dl/helios4/archive. But the problem is not helios4-centric: <mirror>/apt/dists is from Feb 1, so I think the "inline" upgrade problem is valid for all platforms.
-
I'm using Armbian 21.08.8 (Bullseye). I want to upgrade to Armbian 22.02.1 but "apt-get update" doesn't offer anything. Reason seems to be that <mirror>/apt/dists is from Feb 1st 2022. OTOH <mirror>/dl contains the new release but "starting from scratch" (download image, write SDcard) implies that I have to rebuild my OMV6 on top of Armbian. Question: When can I expect that <mirror>/apt/dists will be refreshed? Or is there any other way to upgrade my installation?