djurny Posted Wednesday at 08:06 AM Posted Wednesday at 08:06 AM Hi @wolf7250, That does not look like the new bootscript. Did you update already? To get it working again, you can try the quick workaround as you pointed to earlier, which should allow more room for U-Boot loading kernel, initrd and the rest. Gr, 1 Quote
wolf7250 Posted Wednesday at 08:09 AM Posted Wednesday at 08:09 AM Yes, I did update… not sure why it’s not picking it up. If I go with the quick workaround, will the correct U-Boot get applied in future updates? 0 Quote
djurny Posted Wednesday at 08:55 AM Posted Wednesday at 08:55 AM Hi @wolf7250, The correct U-Boot and bootscript is for sure in the newest release. I built recently and all is there and working without issue on my helios4. Let's unravel what is happening for you and get that sorted out. Gr, 1 Quote
wolf7250 Posted Wednesday at 09:04 AM Posted Wednesday at 09:04 AM Ok. This might have been caused by a partial update. Running OMV there is a script to run to update to the latest in that version - in my case v6. Once that completes successfully then I need to run a release update script which will increment the major version to 7. But I never got that far. So maybe if I do the quick workaround to get me onto the latest and then the correct U-Boot and bootscript will then be included as you said in the latest? Hope that all made sense 😁 0 Quote
djurny Posted Wednesday at 11:03 AM Posted Wednesday at 11:03 AM Hi @wolf7250, I'm not familiar with OMV, so not sure what that update/upgrade process looks like. If it will update/upgrade the armbian packages to the latest release 25.11, then the correct version of armbian-bsp-cli will be installed. The installation of that package should update /boot/boot.scr and make a new U-Boot image available that you would have to install with nand-sata-install. Gr, 1 Quote
FredK Posted Wednesday at 05:03 PM Posted Wednesday at 05:03 PM @wolf7250fyi: I upgraded my Helios4 from OMV6 to OMV7 RC1 in February 2024 already. Upgrade went smoothly. But after that further OMV updates were not possible, solution found at https://forum.armbian.com/topic/23465-apt-get-update-fails-with-public-key-errors/?do=findComment&comment=178626 1 Quote
FredK Posted Wednesday at 05:42 PM Posted Wednesday at 05:42 PM Upgrade to Armbian 25.11.2 successful. 0 Quote
wolf7250 Posted Wednesday at 09:31 PM Posted Wednesday at 09:31 PM Thanks for responding @FredK! 4 hours ago, FredK said: But after that further OMV updates were not possible, solution found at https://forum.armbian.com/topic/23465-apt-get-update-fails-with-public-key-errors/?do=findComment&comment=178626 Is it possible this has been resolved now and I won't need to do anything? Or will I likely need to run the commands that @Igor listed in the post that you linked? 0 Quote
FredK Posted 22 hours ago Posted 22 hours ago @wolf7250 > Is it possible this has been resolved now and I won't need to do anything? I think so, because I was just able to perform a package update without any problems. > Or will I likely need to run the commands that Igor listed in the post that you linked? The background of my post was to encourage you to upgrade your OMV6 to OMV7 (after a full backup) and if the same (minor) problems arise, the solution is well-known. 1 Quote
wolf7250 Posted 34 minutes ago Posted 34 minutes ago Thank you! I've been unable to give this a crack over the last couple of days, but I'm hoping to try this weekend. I'll post back here with how I go 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.