• 0

Broken image in repo


1 1


Hi guys!
Image from that link http://imola.armbian.com/dl/khadas-vim3l/archive/Armbian_22.05.1_Khadas-vim3l_jammy_edge_5.17.5_xfce_desktop.img.xz is about 352 Mb. When Im unzip it - 7zip give me error. 
http://imola.armbian.com/dl/khadas-vim3l/archive/Armbian_22.05.1_Khadas-vim3l_focal_current_5.10.110_xfce_desktop.img.xz - same problem. By the way I have some problem with building image by myself, some time it gives me complete with success, but image is broken too. I think so because first boot take loooooong time with no set root pwd, only rounding circle and second boot don't give me to set root pass and other credentials.
So if it possible, could you test that images (in links) and if it's really problem - repair. May be problem there and build script repairing by itself when everything be ok. Much thanks! 



If its need, I can share my Img. 

Edited by enote
Link to post
Share on other sites

3 answers to this question

Recommended Posts

Donate and support the project!

  • 0

Added a script so we can check them in 10m with a click on a button. (after release is made)



xz: dl/jetson-nano/archive/Armbian_22.05.1_Jetson-nano_jammy_edge_5.18.0_xfce_desktop.img.xz: Unexpected end of input
xz: dl/khadas-vim3l/archive/Armbian_22.05.1_Khadas-vim3l_jammy_edge_5.17.5_xfce_desktop.img.xz: Unexpected end of input
xz: dl/khadas-vim3l/archive/Armbian_22.05.1_Khadas-vim3l_focal_current_5.10.110_xfce_desktop.img.xz: Unexpected end of input
xz: dl/uefi-arm64/archive/Armbian_22.05.1_Uefi-arm64_focal_current_5.15.43_xfce_desktop.img.xz: Unexpected end of input
xz: dl/khadas-vim3/archive/Armbian_22.05.1_Khadas-vim3_jammy_edge_5.17.5_xfce_desktop.img.xz: Unexpected end of input
xz: dl/station-p2/archive/Armbian_22.05.1_Station-p2_bullseye_legacy_4.19.219_xfce_desktop.img.xz: Unexpected end of input
xz: dl/khadas-vim3/archive/Armbian_22.05.1_Khadas-vim3_focal_current_5.10.110_xfce_desktop.img.xz: Unexpected end of input
xz: dl/renegade/archive/Armbian_22.05.1_Renegade_focal_current_5.15.35_xfce_desktop.img.xz: Unexpected end of input
xz: dl/orangepione/archive/Armbian_22.05.1_Orangepione_focal_current_5.15.43_xfce_desktop.img.xz: Unexpected end of input
xz: dl/orangepioneplus/archive/Armbian_22.05.1_Orangepioneplus_focal_current_5.15.43_xfce_desktop.img.xz: Unexpected end of input
xz: dl/clockworkpi-a06/archive/Armbian_22.05.1_Clockworkpi-a06_bullseye_current_5.15.35_xfce_desktop.img.xz: Unexpected end of input
xz: dl/nanopim4v2/archive/Armbian_22.05.1_Nanopim4v2_focal_current_5.15.35_cinnamon_desktop.img.xz: Unexpected end of input
xz: dl/khadas-vim2/archive/Armbian_22.05.1_Khadas-vim2_focal_current_5.10.110_xfce_desktop.img.xz: Unexpected end of input
xz: dl/firefly-rk3399/archive/Armbian_22.05.1_Firefly-rk3399_bullseye_current_5.17.9_xfce_desktop.img.xz: Unexpected end of input
xz: dl/firefly-rk3399/archive/Armbian_22.05.1_Firefly-rk3399_bullseye_edge_5.18.0_xfce_desktop.img.xz: Unexpected end of input
xz: dl/rockpi-4b/archive/Armbian_22.05.1_Rockpi-4b_jammy_edge_5.18.0_xfce_desktop.img.xz: Unexpected end of input
xz: dl/station-m2/archive/Armbian_22.05.1_Station-m2_bullseye_legacy_4.19.219_xfce_desktop.img.xz: Unexpected end of input
xz: dl/station-m2/archive/Armbian_22.05.1_Station-m2_jammy_edge_5.18.0_xfce_desktop.img.xz: Unexpected end of input
xz: dl/pineh64-b/archive/Armbian_22.05.1_Pineh64-b_focal_current_5.15.43_xfce_desktop.img.xz: Unexpected end of input
xz: dl/khadas-vim1/archive/Armbian_22.05.1_Khadas-vim1_jammy_edge_5.17.5_xfce_desktop.img.xz: Unexpected end of input
xz: dl/station-m1/archive/Armbian_22.05.1_Station-m1_bullseye_edge_5.18.0_xfce_desktop.img.xz: Unexpected end of input
xz: dl/khadas-edge/archive/Armbian_22.05.1_Khadas-edge_focal_current_5.15.35_cinnamon_desktop.img.xz: Unexpected end of input
xz: dl/khadas-edge/archive/Armbian_22.05.1_Khadas-edge_jammy_edge_5.18.0_xfce_desktop.img.xz: Unexpected end of input



The only fast (few days of work since it never goes as planned) repair is - recompiling all images, running this test and if not o.k. do it again ... and identifying why this happens, fix trouble, adjust code, do it again and again until things are o.k. This is how complex systems operations looks like. When all those little things will have unit testings attached too, problems will be detected earlier ...

Link to post
Share on other sites

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.

Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


1 1