New 'Armbian 25.11.1 Trixie Minimal / IOT' image is possibly corrupted

[pbg]

As of 2025-12-01, current 'Armbian 25.11.1 Trixie Minimal / IOT' lists as 'Kernel: 6.12.58, Size: 505 KB, Release date: Nov 22, 2025' and seems to have had problems on image generation.

 

Please check when possible.

 

Thanks in advance,

 

pbg

[Igor]

2 hours ago, pbg said:

and seems to have had problems on image generation.

Does it fail to assemble image? Or you can make image but image is corrupted? For that part we have an explanation: https://docs.armbian.com/User-Guide_Getting-Started/#flash-to-sd-card

[eselarm]

File (.xz) less than 1M, it extracts to 1444M, only 836k content, rest is sparse. Only U-Boot is written It looks like. So clearly image generation failed.

[Werner]

just noticed current kernel is broken. I assume because of upstream changes. looks like similar what I've fixed for meson64 6.18-rc7.

 

Got it, will send pr

 

Of course this does not explain why the image wasn't correctly assembled at all...

 

Looking good: https://paste.armbian.de/ohagifufem

 

ls -l|grep Odr
-rw-rw-r-- 1 root root        142 Dec  2 05:14 Armbian-unofficial_26.02.0-trunk_Odroidc2_trixie_current_6.12.60_minimal.img.sha
-rw-rw-r-- 1 root root      19751 Dec  2 05:14 Armbian-unofficial_26.02.0-trunk_Odroidc2_trixie_current_6.12.60_minimal.img.txt
-rw-rw-r-- 1 root root  322026836 Dec  2 05:14 Armbian-unofficial_26.02.0-trunk_Odroidc2_trixie_current_6.12.60_minimal.img.x

 

[Igor]

11 hours ago, pbg said:

Please check when possible.

 

We checked and it works on supported build host. We need to see logs to understand why it is failing for you.

[pbg]

I have not tried to build the image myself. I wanted to flag that the file linked for download was not correctly assembled. I should have been more precise.

[Igor]

3 hours ago, pbg said:

the file linked for download was not correctly assembled.

Aha. We only test one randomly picked image per board - not all of them. And nobody noticed small size of the file ... I see now. Probably runner starved for memory or some other problem. Logs were already deleted so I can't check, but have started new build.

 

3 hours ago, pbg said:

I should have been more precise.

Indeed  All clear now.