Domas

Hey - just reopening this question. I have a related issue. This continues updating whenever I run the updates (at least once a week) I have noticed that it receives 9-12 of the same updates very often as stated in original post. But it seems that none of the other software is being updated. Is this normal? I remember back in the day if I run apt updates rarely, like once a month there would be a 40-ish packages to be updated. What happened was I did a lot of fiddling around ir sources.list.d and I probably broke something there. Or this is normal with beta on? This is my sources content: orangepiplus:~:% grep -Erh '^deb ' /etc/apt/sources.list* deb [arch=armhf signed-by=/usr/share/keyrings/armbian.gpg] http://beta.armbian.com jammy main jammy-utils jammy-desktop deb [arch=armhf signed-by=/usr/share/keyrings/armbian.gpg] http://beta.armbian.com jammy main jammy-utils jammy-desktop deb [signed-by=/usr/share/keyrings/armbian.gpg] https://github.armbian.com/configng stable main deb http://ports.ubuntu.com/ focal main restricted universe multiverse deb http://ports.ubuntu.com/ focal-security main restricted universe multiverse deb http://ports.ubuntu.com/ focal-updates main restricted universe multiverse deb http://ports.ubuntu.com/ focal-backports main restricted universe multiverse orangepiplus:~:% This is my apt-cache policy output: orangepiplus:~:% apt-cache policy Package files: 100 /var/lib/dpkg/status release a=now 100 http://ports.ubuntu.com jammy-backports/universe armhf Packages release v=22.04,o=Ubuntu,a=jammy-backports,n=jammy,l=Ubuntu,c=universe,b=armhf origin ports.ubuntu.com 100 http://ports.ubuntu.com jammy-backports/main armhf Packages release v=22.04,o=Ubuntu,a=jammy-backports,n=jammy,l=Ubuntu,c=main,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-security/multiverse armhf Packages release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=multiverse,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-security/universe armhf Packages release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=universe,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-security/restricted armhf Packages release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=restricted,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-security/main armhf Packages release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=main,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-updates/multiverse armhf Packages release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=multiverse,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-updates/universe armhf Packages release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=universe,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-updates/restricted armhf Packages release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=restricted,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-updates/main armhf Packages release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=main,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy/multiverse armhf Packages release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=multiverse,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy/universe armhf Packages release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=universe,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy/restricted armhf Packages release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=restricted,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy/main armhf Packages release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=main,b=armhf origin ports.ubuntu.com 500 http://beta.armbian.com jammy/jammy-desktop all Packages release o=Armbian,a=jammy,n=jammy,l=Armbian,c=jammy-desktop,b=all origin beta.armbian.com 500 http://beta.armbian.com jammy/jammy-desktop armhf Packages release o=Armbian,a=jammy,n=jammy,l=Armbian,c=jammy-desktop,b=armhf origin beta.armbian.com 500 http://beta.armbian.com jammy/jammy-utils all Packages release o=Armbian,a=jammy,n=jammy,l=Armbian,c=jammy-utils,b=all origin beta.armbian.com 500 http://beta.armbian.com jammy/jammy-utils armhf Packages release o=Armbian,a=jammy,n=jammy,l=Armbian,c=jammy-utils,b=armhf origin beta.armbian.com 500 http://beta.armbian.com jammy/main all Packages release o=Armbian,a=jammy,n=jammy,l=Armbian,c=main,b=all origin beta.armbian.com 500 http://beta.armbian.com jammy/main armhf Packages release o=Armbian,a=jammy,n=jammy,l=Armbian,c=main,b=armhf origin beta.armbian.com 500 https://github.armbian.com/configng stable/main armhf Packages release o=armbian.github.io/configurator,n=stable,l=armbian.github.io/configurator,c=main,b=armhf origin github.armbian.com Pinned packages: orangepiplus:~:% Also attaching putty home screen to show what I am on now, also showing update window where I get those reocurring updates.

Wow, unbelievable. But happy to see it is so actively maintained. I don't mind being on beta for time being and I am fine with updating this often. I actually enjoy receiving updates, since I decided to switch to beta and keep the kernel unfrozen. Worst case scenario - if some beta breaks my back, I will just restore whole SD card to a few month old backup and update to latest stable. I do not have anything useful on my board that changes over time. Lets consider this topic closed.

Hello, not sure if this should go under beginners, or this section but trying here. I have now set my armbian-config to rolling updates so I get the good beta stuff. Situation: I have no hard evidence of how often this actually happens, but it seems that every time i go and do armbian-upgrade, which I have performed yesterday and today, but also few days ago, I get the same 9 updates every time, armbian-bsp-cli-orangepiplus-current armbian-config armbian-firmware-full armbian-zsh base-files linux-dtb-current-sunxi linux-headers-current-sunxi linux-image-current-sunxi linux-u-boot-orangepiplus-current Is this normal with rolling updates? or my apt somehow loses the version information and reinstalls the new packages. Of course it does not happen if I run -upgrade twice. It compiles kernel etc, so a bit lengthy upgrade but no big deal. I am asking this because I was also performing a userspace upgrade unsuccessfully recently (also in same frequency as I do this armbian-upgrade) which fails for some reason. Just trying to find out if this is related. But this is not a part of this thread.

So it was a success. Version information updated too now But it did want to both uninstall and update armbian-bsp-cli-orangepiplus after updating armbian.list file and running apt update/upgrade Do you think it is safe to autoremove them if the system is up and running? I am so happy I managed to fix my junk from 2015.... It is probably a $30 board from china. But there is just something about making old hardware work for as long as possible. Thank you all!

Will attempt tonight.

Ok, upgraded successfully. I said no to removing obsolete stuff in the end and it seemed to want to delete armbian stuff. I did not freeze the kernel this time one thing is a bit weird Now it says Armbian 23.02.2 Jammy shouldn't the version be 24. something? I am nearly done, let me know if I can safely run apt update/upgrade? I'd really hate to start over. My /etc/apt/sources.list.d/armbian.list file contents - the directory was a bit different Thank you all so far!

Yes, in the very end I was asked to remove obsolete packages. I said yes all the times. I don't remember what was in the list, since it was about 76~ packages I may try with no option to keep them Is there any way to enforce this manually pre-upgrade? I only freeze the kernel, i suppose it is something different? Or maybe I can try to upgrade without freezing kernel? Or is that a guaranteed fail?

This is how healthy starting system looks like And the serial output when starting this older backup: Shall I now just give up and do a clean install? This time I made a backup of failed installation too.

So, upgraded and bricked again armbianEnv: fstab /boot seems to be populated And According to boot script, it seems that /boot/dtb directory is missing and this is causing the whole havoc?

This will take some time since it takes a few hours to upgrade, so maybe someday this week. I will not leave this thread without the final outcome, even if I will give up and do a fresh install. I remember it took me forever to configure autologin, samba and x11vnc for some reason (can't remember, it was 3 years ago). So my lazy ass just wants to upgrade. But looking at my log from serial interface I can see that /boot is there, not sure what it is inside though, at least it seems to have boot script (boot.scr is found). First one to fail is /boot/uInitrd. this is where I have to look. And also what Werner said too.

I can do that but this would require to run the update again to brick my pc. I have restored the backup for now But you mean to do this when it is bricked after update, right?

I am very well aware they are not officially supported. But as I understand, it does not mean that it won't work. So generally they more often don't work than they do? And this is bad luck, nothing to be done about that - suck it up and do a fresh install? Or there is some research I can do to avoid this?

Hi there, Since being only a novice in linux, there are some things that are difficult to understand. Like - which configs to update or keep old versions when doing the upgrade. Last time I said N (keep original version) to everything. Really the only things I care about are vnc configs and samba setup. I basically use it as a network drive for backups. Only necessary software is x11vnc and samba. Else I log into it just for updates/restarts. I have tried upgrading my armbian several times. Unfortunately it does not work and I have to restore my sd card backup and start over. I update it making sure all apt updates are done, and then freezing the kernel and running do-release-upgrade. Here is the data when logging in via terminal for you to see the context, pre-upgrade: Here goes lsb_release and etc/armbian-release info, pre-upgrade: And finally, after I brick my board, I get this data via serial interface: Where do I start?