DanOB Posted Wednesday at 12:34 AM Posted Wednesday at 12:34 AM Today unattended upgrades ran and installed the following: libtasn1-6 linux-dtb-current-odroidxu4 linux-image-current-odroidxu4 linux-u-boot-odroidxu4-current Afterward, the system automatically rebooted and went into a boot loop. I had a backup I was able to copy to the emmc and get back up and running but it is from October 2024 and I am not really sure what to do. coming here to see if anyone else has experienced the same. I tried to run armbianmonitor -U and it had some weird html. I am pretty good with Linux but everything is self taught. thank you in advance for any help Dan 0 Quote
Igor Posted Wednesday at 06:22 AM Posted Wednesday at 06:22 AM This upgrade (for this board) fall into update by mistake and unfortunately its broken. We are still working on to determine why this happen, then publish images and if there is no report on problems, we pushed update to repo. To minimize what just happened to you. I am truly sorry, but we are operating this service with way too small resources and proper professional testing is far out of our reach. I am removing this broken update from repository ... 0 Quote
prof Posted Wednesday at 07:20 AM Posted Wednesday at 07:20 AM It would be great to publish a gzipped tar archive of the fixed /boot directory so that those of us bitten by this bug don't have to reinstall from scratch. 0 Quote
Igor Posted Wednesday at 09:58 AM Posted Wednesday at 09:58 AM Fixed by: https://github.com/armbian/build/commit/5115cdf47a91f9cf5eb15f1b4984deebbe329002 2 hours ago, prof said: don't have to reinstall from scratch. This can help https://docs.armbian.com/User-Guide_Recovery/ 0 Quote
DanOB Posted Wednesday at 12:34 PM Author Posted Wednesday at 12:34 PM @Igor All good, I totally understand and appreciate what you do. I assumed with the update removed I would be ok to move forward updating my older backup but I got into a boot loop again. I am back up and running again from my backup so no big deal. I guess I should just standby until things are good on your end to move forward. thanks again, Dan 0 Quote
Igor Posted Wednesday at 12:54 PM Posted Wednesday at 12:54 PM 18 minutes ago, DanOB said: no big deal. Its a shame for us There are so many problems (in general) and so little time / resources. Not yet fully fixed, but working on. 0 Quote
prof Posted Wednesday at 09:06 PM Posted Wednesday at 09:06 PM 11 hours ago, Igor said: This can help https://docs.armbian.com/User-Guide_Recovery/ The last part of those instructions say to download boot-odroidxu4.cmd from github and then execute mkimage. But there is no such file on github. 0 Quote
prof Posted yesterday at 06:19 AM Posted yesterday at 06:19 AM Have not seen any of the new files on any of the mirrors yet. OTOH, https://imola.armbian.com/apt/pool/main/l/ still has the old (bad) files. 0 Quote
Igor Posted yesterday at 07:31 AM Posted yesterday at 07:31 AM 1 hour ago, prof said: still has the old (bad) files. You should always use apt.armbian.com as we are automatically removing mirrors from pool that are not synced yet. I just tested Odroid XU4 switching between nightly and stable, and it works when installing packages from stable repo. Name / version of the file is the same. If someone has time, those instructions would need some update https://docs.armbian.com/User-Guide_Recovery/ I am totally busy making a release and can't touch this in weeks to come. 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.