Won't boot after update #2017
Labels
Comments
fhamborg
changed the title
I assume you are running an armbian based image on a pi, then you should consider updating manual by armbian-upgrade. It took my test-pi to v24.11.1 for Raspberry Pi 4 running Armbian Linux 6.6.63-current-bcm2711. |
|
I thought the proposed way to update was ncp-update? |
To update nextcloudpi, yes.
Therefore my hint to use armbian-upgrade. |
|
Alright, so that's interesting. I started on the freshly recovered system (where I had recovered it by This is exactly the one that is also present when I see that the system doesn't boot. But then the updater doesn't finish because of this: |
|
I.e. note how the path |
imho it is quite rude method starting up a configured instance with first boot / install boot environment again. Not an expert but I think it's messing up the system. Take a look at / and /boot - the links: |
|
would you be so kind and also post the contents of /boot/firmware ? |
|
|
cool thanks a lot! after some diving into this, i found that for some reason the wrong kernel is configured for my system to update. due to this, the debian bookworm kerneles are being pulled (see first output above) as well as the (correct) armbian ones (second above). i made some changes to prioritize armbian kernels higher than debian kernels and now it seems to work. this is what i added: and in case you have time, would be interesting to see if you also have any of these two files set or if not im really wondering why your system pulls the correct one (from both sources) whereas mine doesnt. |
|
ncpi4 is my test instance, fresh install with latest ncp 155.3 (armbian based) nextcloudpi is my production instance, updatet to ncp 155.3 (stays debian based) |
|
Ah weird, and what's the content when you use the two cat commands (the first two, with sources)? |
|
ncpi4 nextcloudpi |
|
Okay that's interesting, you also got the Debian bookworm source (from which the wrong kernel I always ended up having after performing an update or having an auto update). |
|
Anyway, thanks for your help :) |
|
If I read your first post right, you use a pi5? ncpi5 |
|
yes, im using a pi 5. your sources look pretty identical to mine i think. so the reason seems to be on my system that for some reason the wrong kernel was pulled. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Every time the system does an udpate (automatically) or I perform one manually (
apt update && apt upgrade), it won't be able to boot next time I restart it. Thus far, I always ended updding the boot partition from a fresh nextcloudpi image to my USB stick and would boot again.Not sure if this relevant, but this time I found at least out that there is a new kernel version installed:
compared to
6.6.45-current-bcm2712on the fresh nextcloudpi image. While this not bad per se, I noticed that the other files were not updated correctly, e.g., note howlib/modulesis still on 6.6.45 (whereas the kernel on the old system was already upgraded to 6.10.11):Now I think there might be two potential issues here:
FYI, not sure if this is relevant, but the diff between the old (broken) initrd.img and the fresh one (note that some files related to cryptsetup are added to the old/broken setup (perhaps because I enabled encryption in the old setup)
The text was updated successfully, but these errors were encountered: