Hi all,

 

I'm running a couple of ODroid XU4's as a server. Yesterday I ran an update and after this update the board no longer boots... (I was running Armbian Focal kernel 4

I have tested a 'fresh' armbian image and then the system boots without issues. I have saved what packages are updated and wonder if I would be able to restore this somehow?

 

A log of the update (never mind the dutch)

https://pastebin.com/WWP2DFfC

 

I used to have kernal 5.4 on this board, but I downgraded about 6 months ago. Could that be the issue?

Because in the log I read:

Uitpakken van .../77-linux-image-current-odroidxu4_21.02.2_armhf.deb wordt voorbereid...
update-initramfs: Deleting /boot/initrd.img-5.4.72-odroidxu4
Removing obsolete file 4.14.202-odroidxu4
Removing obsolete file uInitrd-4.14.202-odroidxu4
update-initramfs: Deleting /boot/initrd.img-4.14.202-odroidxu4
Bezig met uitpakken van linux-image-current-odroidxu4 (21.02.2) over (20.08.13) ...
Uitpakken van .../78-linux-image-legacy-odroidxu4_21.02.2_armhf.deb wordt voorbereid...
Bezig met uitpakken van linux-image-legacy-odroidxu4 (21.02.2) over (20.08.13) ...
Uitpakken van .../79-linux-u-boot-odroidxu4-legacy_21.02.1_armhf.deb wordt voorbereid...
Bezig met uitpakken van linux-u-boot-odroidxu4-legacy (21.02.1) over (20.08.13) ...

 

But later I find:

Instellen van linux-image-current-odroidxu4 (21.02.2) ...
update-initramfs: Generating /boot/initrd.img-5.4.98-odroidxu4
update-initramfs: Converting to u-boot format

And even later:

Instellen van linux-image-legacy-odroidxu4 (21.02.2) ...
update-initramfs: Generating /boot/initrd.img-4.14.212-odroidxu4
update-initramfs: Converting to u-boot format

 

What would be the way to revert the culprit updates?

38 minutes ago, dieterpi said:

What would be the way to revert the culprit updates?

This "board not start" section only covers "Impossible cases - when official armbian builds from the download section doesn't start at all". Moving to Bug tracker section.

 

38 minutes ago, dieterpi said:

I used to have kernal 5.4 on this board, but I downgraded about 6 months ago. Could that be the issue?

 

If you still have both kernels installed, this is certainly bad and possible source of troubles. Try recover this way https://docs.armbian.com/User-Guide_Recovery/ and remove one kernel, together with its dtb package.