porg Posted February 9 Posted February 9 My hardware: Odroid HC2 Armbian 24.5.1 Bookworm with Linux 6.6.31-current-odroidxu4 : My backup restoration → Has other issues too → But apt upgrade results in various size and hash mismatches. Offtopic: apt upgrade or sudo dpkg --configure -a always crash the system (since summer 2024, troubleshooting without success since christmas 2024) Ruled out HW failure 80-90%. My local apt/dpg cache was corrupted, thus at /var/lib/dpkg/ backed up info/ to info.bak/ and mkdir info/ afresh. And now sudo dpkg --configure -a completed successfully the very first time! But 2025-02-09 ca. 12:00 CET and also later the afternoon apt upgrade results in various size and hash mismatches. Mirror sync in progress? Spoiler $ sudo mv /var/lib/dpkg/info /var/lib/dpkg/info.bak $ sudo mkdir /var/lib/dpkg/info $ sudo dpkg --configure -a # Completed $ sudo apt update # Starts normal Get:1 http://packages.openmediavault.org/public sandworm/main armhf salt-minion all 3006.0+ds-1+225.1 [126 kB] Get:2 http://security.debian.org bookworm-security/main armhf git armhf 1:2.39.5-0+deb12u2 [6,060 kB] [...] # But then some hash mismatches occur Get:5 http://apt.armbian.com bookworm/bookworm-utils armhf base-files armhf 25.2.1-12.4+deb12u9-bookworm [53.0 kB] Err:5 http://apt.armbian.com bookworm/bookworm-utils armhf base-files armhf 25.2.1-12.4+deb12u9-bookworm Hash Sum mismatch Hashes of expected file: - SHA512:2e2823fa52355f70ed4a8a5d34a26528dbf27d12fcec1d873e7bfb67c7019bdefe25bfa053c857e904fc6e681be0ae92eeaa2d6342e5548e59b7c6426b4c65dc - SHA256:96e7ca7a69ef8fae4a52311d14115c288e05d98bbbfe1b7a7304573798f14297 - SHA1:6f217dc12471a8f79a87c6711be6c40f602e0888 [weak] - MD5Sum:049413cb0eb2fbf97f04e56f1f3d4ba9 [weak] - Filesize:52960 [weak] Hashes of received file: - SHA512:f5bc6012293b6516d7f74e71d6c7697e961c76c265d5b81976c18f809787db9968c88f2385adb82d6bd6f39357239950a27740a90593f365737a0bb9ce3cf32a - SHA256:5495bf319ec88106001cc15fad3f315626752a083044db60e7bd3829b593f4d2 - SHA1:ba43b5b711d7a210bcf1a8c7776760b19757ba19 [weak] - MD5Sum:7623285eddd888a9f5dd10f3de441438 [weak] - Filesize:52960 [weak] Last modification reported: Sat, 08 Feb 2025 22:47:38 +0000 Err:9 http://apt.armbian.com bookworm/main armhf armbian-zsh all 25.2.1 File has unexpected size (10829720 != 10829716). Mirror sync in progress? [IP: 152.53.15.45 80] Err:8 http://apt.armbian.com bookworm/main armhf armbian-firmware all 25.2.1 File has unexpected size (91589632 != 91589640). Mirror sync in progress? [IP: 65.21.120.247 80] kB] Get:143 http://deb.debian.org/debian bookworm/main armhf rfkill armhf 2.38.1-5+deb12u3 [32.3 kB] Fetched 211 MB in 1min 7s (3,171 kB/s) E: Failed to fetch http://netcup.armbian.com/apt/pool/bookworm-utils/b/base-files/base-files_25.2.1-12.4+deb12u9-bookworm_armhf__1-bookworm-1armbian1-Baa17-U12.4--deb12u9-R55fa.deb Hash Sum mismatch Hashes of expected file: - SHA512:2e2823fa52355f70ed4a8a5d34a26528dbf27d12fcec1d873e7bfb67c7019bdefe25bfa053c857e904fc6e681be0ae92eeaa2d6342e5548e59b7c6426b4c65dc - SHA256:96e7ca7a69ef8fae4a52311d14115c288e05d98bbbfe1b7a7304573798f14297 - SHA1:6f217dc12471a8f79a87c6711be6c40f602e0888 [weak] - MD5Sum:049413cb0eb2fbf97f04e56f1f3d4ba9 [weak] - Filesize:52960 [weak] Hashes of received file: - SHA512:f5bc6012293b6516d7f74e71d6c7697e961c76c265d5b81976c18f809787db9968c88f2385adb82d6bd6f39357239950a27740a90593f365737a0bb9ce3cf32a - SHA256:5495bf319ec88106001cc15fad3f315626752a083044db60e7bd3829b593f4d2 - SHA1:ba43b5b711d7a210bcf1a8c7776760b19757ba19 [weak] - MD5Sum:7623285eddd888a9f5dd10f3de441438 [weak] - Filesize:52960 [weak] Last modification reported: Sat, 08 Feb 2025 22:47:38 +0000 E: Failed to fetch http://apt.armbian.com/pool/main/a/armbian-firmware/armbian-firmware_25.2.1_all__1-SAe75d-B6c7f-R448a.deb File has unexpected size (91589632 != 91589640). Mirror sync in progress? [IP: 65.21.120.247 80] E: Failed to fetch http://apt.armbian.com/pool/main/a/armbian-zsh/armbian-zsh_25.2.1_all__1-SAbfee-B6e0d-R448a.deb File has unexpected size (10829720 != 10829716). Mirror sync in progress? [IP: 152.53.15.45 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? Then decided to flash a fresh image and start fresh (in all cases the SHA checksum matched, and BalenaEtcher checked the flash as identical to the image) Armbian_24.11.1_Odroidxu4_bookworm_current_6.6.60-omv_minimal → Status LED flashes, but SSH never reachable. No idea at what level it fails. Armbian_25.2.1_Odroidxu4_bookworm_current_6.6.75_minimal.img.xz → Status LED flashes, but SSH never reachable. No idea at what level it fails. As recommended by the FAQs "Image does not boot" --> check previous images from archive Armbian_24.11.1_Odroidxu4_bookworm_current_6.6.60_minimal → Boots, SSH works, went through initial setup (root pw, locale, timezone, username, etc). → But apt update ; apt upgrade fails with size and hash mismatches at 2025-02-09 22:30 CET. Spoiler Err:5 http://apt.armbian.com bookworm/bookworm-utils armhf base-files armhf 25.2.1-12.4+deb12u9-bookworm Hash Sum mismatch Hashes of expected file: - SHA512:2e2823fa52355f70ed4a8a5d34a26528dbf27d12fcec1d873e7bfb67c7019bdefe25bfa053c857e904fc6e681be0ae92eeaa2d6342e5548e59b7c6426b4c65dc - SHA256:96e7ca7a69ef8fae4a52311d14115c288e05d98bbbfe1b7a7304573798f14297 - SHA1:6f217dc12471a8f79a87c6711be6c40f602e0888 [weak] - MD5Sum:049413cb0eb2fbf97f04e56f1f3d4ba9 [weak] - Filesize:52960 [weak] Hashes of received file: - SHA512:f5bc6012293b6516d7f74e71d6c7697e961c76c265d5b81976c18f809787db9968c88f2385adb82d6bd6f39357239950a27740a90593f365737a0bb9ce3cf32a - SHA256:5495bf319ec88106001cc15fad3f315626752a083044db60e7bd3829b593f4d2 - SHA1:ba43b5b711d7a210bcf1a8c7776760b19757ba19 [weak] - MD5Sum:7623285eddd888a9f5dd10f3de441438 [weak] - Filesize:52960 [weak] Last modification reported: Sat, 08 Feb 2025 22:47:38 +0000 E: Failed to fetch http://fi.mirror.armbian.de/apt/pool/bookworm-utils/b/base-files/base-files_25.2.1-12.4+deb12u9-bookworm_armhf__1-bookworm-1armbian1-Baa17-U12.4--deb12u9-R55fa.deb Hash Sum mismatch Hashes of expected file: - SHA512:2e2823fa52355f70ed4a8a5d34a26528dbf27d12fcec1d873e7bfb67c7019bdefe25bfa053c857e904fc6e681be0ae92eeaa2d6342e5548e59b7c6426b4c65dc - SHA256:96e7ca7a69ef8fae4a52311d14115c288e05d98bbbfe1b7a7304573798f14297 - SHA1:6f217dc12471a8f79a87c6711be6c40f602e0888 [weak] - MD5Sum:049413cb0eb2fbf97f04e56f1f3d4ba9 [weak] - Filesize:52960 [weak] Hashes of received file: - SHA512:f5bc6012293b6516d7f74e71d6c7697e961c76c265d5b81976c18f809787db9968c88f2385adb82d6bd6f39357239950a27740a90593f365737a0bb9ce3cf32a - SHA256:5495bf319ec88106001cc15fad3f315626752a083044db60e7bd3829b593f4d2 - SHA1:ba43b5b711d7a210bcf1a8c7776760b19757ba19 [weak] - MD5Sum:7623285eddd888a9f5dd10f3de441438 [weak] - Filesize:52960 [weak] Last modification reported: Sat, 08 Feb 2025 22:47:38 +0000 E: Failed to fetch http://apt.armbian.com/pool/main/a/armbian-firmware/armbian-firmware_25.2.1_all__1-SAe75d-B6c7f-R448a.deb File has unexpected size (91589632 != 91589640). Mirror sync in progress? [IP: 46.102.157.202 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? 0 Quote
porg Posted February 9 Author Posted February 9 On the freshly flashed Armbian_24.11.1_Odroidxu4_bookworm_current_6.6.60_minimal $ cat /etc/apt/sources.list.d/armbian.list deb [signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com bookworm main bookworm-utils bookworm-desktop No /boot/ArmbianEnv.txt yet. Meanwhile created that with board_name=hc1. Reboot now. SSH again not reachable. Now it occurred to me. Those file size and hash mismatches could yet again be just another sign of SD card corruption. So far I tried different of my existing cards. Maybe I was unlucky and they all had issues. I will now buy a new card and try again. If it then still persists, then it could be that the SD card reader/writer is faulty. By which the whole device would be done effectively then. 0 Quote
Igor Posted February 10 Posted February 10 8 hours ago, porg said: No /boot/ArmbianEnv.txt yet. There is /boot/boot.ini Change this there and try. 0 Quote
derdietmar Posted February 10 Posted February 10 (edited) Hi, same here. Odroid XU4. Works fine using Armbian_24.11.1_Odroidxu4_bookworm_current_6.6.60_minimal.img No boot using Armbian_25.2.1_Odroidxu4_bookworm_current_6.6.75_minimal.img Upgrade sometimes causes mismatch errors. After upgrade the device does not boot. It is not a hardware issue, but a configuration issue with Armbian_25.2.1_Odroidxu4_bookworm_current_6.6.75_minimal.img See you Edited February 10 by derdietmar 0 Quote
Igor Posted February 10 Posted February 10 We will look into this. Build was reported working, but images were not tested yet. 0 Quote
Davy Posted February 10 Posted February 10 After an `apt upgrade` from 24.11 to the kernel doesn't boot anymore. I've flashed 25.2.1 and same error (both with minimal as with server). I flashed 24.11 and it booted. Then I did `apt update` and `apt upgrade` and after reboot it got into the same state. I connected uart to my odroid hc2 to capture some usefull debug logs: U-Boot 2017.05-armbian-2017.05-S42ac-P1bb2-H0673-V2e86-Bda0a-R448a (Nov 21 2024 - 02:52:38 +0000) for ODROID-XU4 CPU: Exynos5422 @ 800 MHz Model: Odroid XU4 based on EXYNOS5422 Board: Odroid XU4 based on EXYNOS5422 Type: unknown DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1 MMC Device 0 ( SD ): 14.8 GiB Card did not respond to voltage select! mmc_init: -95, time 12 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press quickly 'Enter' twice to stop autoboot: 0 ** File not found /boot.ini ** ## Executing script at 43e00000 Wrong image format for "source" command 13424 bytes read in 44 ms (297.9 KiB/s) ## Executing script at 43e00000 15 bytes read in 46 ms (0 Bytes/s) 10455240 bytes read in 840 ms (11.9 MiB/s) 10011566 bytes read in 810 ms (11.8 MiB/s) 0 bytes read in 40 ms (0 Bytes/s) Found mainline kernel configuration 83366 bytes read in 107 ms (760.7 KiB/s) libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND Kernel image @ 0x40008000 [ 0x000000 - 0x9f88c8 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 10011502 Bytes = 9.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 44000000 Booting using the fdt blob at 0x44000000 Using Device Tree in place at 44000000, end 440175a5 Starting kernel ... [ 2.561470] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 2.568252] CPU: 4 PID: 1 Comm: swapper/0 Not tainted 6.6.75-current-odroidxu4 #1 [ 2.575702] Hardware name: Samsung Exynos (Flattened Device Tree) [ 2.581777] unwind_backtrace from show_stack+0x10/0x14 [ 2.586969] show_stack from dump_stack_lvl+0x40/0x4c [ 2.591996] dump_stack_lvl from panic+0x118/0x340 [ 2.596760] panic from mount_root_generic+0x1c8/0x268 [ 2.601873] mount_root_generic from prepare_namespace+0x1fc/0x258 [ 2.608024] prepare_namespace from kernel_init_freeable+0x284/0x298 [ 2.614350] kernel_init_freeable from kernel_init+0x18/0x130 [ 2.620070] kernel_init from ret_from_fork+0x14/0x28 [ 2.625095] Exception stack(0xf0835fb0 to 0xf0835ff8) Looks to me like the uboot config got corrupted? as it could not even find `boot.ini`? 0 Quote
belegdol Posted February 11 Posted February 11 Apologies for the trouble. I will try to have a look over the next few days. In the meantime, @Davy, are you able to post UART logs for the working boot? I somehow recall the boot.ini message is always there. It is also possible to mount the SD card on a PC, this is how I recovered from a broken update once or twice. I am running a self-compiled 6.6.75 on my HC1 at this very moment so this issue is definitely curious. 0 Quote
belegdol Posted February 11 Posted February 11 (edited) For comparison purposes, the hash values for my working build are: linux-image-current-odroidxu4_24.11.1.2_armhf__1-S1b53-D0531-P3da6-C3a73H5845-HK01ba-V014b-B59f0-R448a.deb. I could upload my builds somewhere for testing purposes, but I am not sure if it won't be setting a bad example wrt. not downloading builds from random strangers on the internet. Edited February 11 by belegdol 0 Quote
Davy Posted February 11 Posted February 11 (edited) @belegdol true. I should have said, the boot.src thing, you don't see the probing of the armbianEnv etc. Here is a capture of freshly flashed 24.11 U-Boot 2017.05-armbian-2017.05-S42ac-P1bb2-H0673-V2e86-Bda0a-R448a (Nov 21 2024 - 02:52:38 +0000) for ODROID-XU4 CPU: Exynos5422 @ 800 MHz Model: Odroid XU4 based on EXYNOS5422 Board: Odroid XU4 based on EXYNOS5422 Type: unknown DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1 MMC Device 0 ( SD ): 14.8 GiB Card did not respond to voltage select! mmc_init: -95, time 12 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press quickly 'Enter' twice to stop autoboot: 0 ** File not found /boot.ini ** ## Executing script at 43e00000 Wrong image format for "source" command 13424 bytes read in 46 ms (284.2 KiB/s) ## Executing script at 43e00000 ** File not found /boot/armbianEnv.txt ** ** Unrecognized filesystem type ** ** File not found armbianEnv.txt ** 8788032 bytes read in 714 ms (11.7 MiB/s) 9299955 bytes read in 754 ms (11.8 MiB/s) 0 bytes read in 42 ms (0 Bytes/s) Found mainline kernel configuration 89288 bytes read in 107 ms (814.5 KiB/s) libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND Kernel image @ 0x40008000 [ 0x000000 - 0x861840 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 9299891 Bytes = 8.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 44000000 Booting using the fdt blob at 0x44000000 Using Device Tree in place at 44000000, end 44018cc7 Starting kernel ... .. lots of newlines.. and then a prompt odroidxu4 login: root (automatic login) Edited February 11 by Davy 0 Quote
Davy Posted February 11 Posted February 11 (edited) After the broken upgrade, i can still mount the sd card on a different machine, no errors reported. If it helps, there is the `apt upgrade` output that breaks it. Armbian 'linux-image-current-odroidxu4' for '6.6.60-current-odroidxu4': 'postrm' finishing. Preparing to unpack .../10-linux-u-boot-odroidxu4-current_25.2.1_armhf.deb ...#########...............................................] Unpacking linux-u-boot-odroidxu4-current (25.2.1) over (24.11.1) ... Preparing to unpack .../11-python3-pkg-resources_66.1.1-1+deb12u1_all.deb ... Unpacking python3-pkg-resources (66.1.1-1+deb12u1) over (66.1.1-1) ... Setting up python3-pkg-resources (66.1.1-1+deb12u1) ... Setting up libtext-iconv-perl:armhf (1.7-8) ... Setting up linux-u-boot-odroidxu4-current (25.2.1) ... Armbian 'uboot-odroidxu4-current' for '2017.05-S42ac-P3788-H27d6-Vc604-Bb703-R448a': 'postinst' starting. Armbian 'uboot-odroidxu4-current' for '2017.05-S42ac-P3788-H27d6-Vc604-Bb703-R448a': 'postinst' finishing. Setting up linux-image-current-odroidxu4 (25.2.1) ... Armbian 'linux-image-current-odroidxu4' for '6.6.75-current-odroidxu4': 'postinst' starting. update-initramfs: Generating /boot/initrd.img-6.6.75-current-odroidxu4 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.75-current-odroidxu4 Image Name: uInitrd Created: Tue Feb 11 09:39:19 2025 Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 10011470 Bytes = 9776.83 KiB = 9.55 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.75-current-odroidxu4 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.6.75-current-odroidxu4' update-initramfs: Armbian: done. Remove unused generated file: /boot/initrd.img-6.6.60-current-odroidxu4 Remove unused generated file: /boot/uInitrd-6.6.60-current-odroidxu4 Armbian: update last-installed kernel symlink to 'zImage'... '/boot/zImage' -> 'vmlinuz-6.6.75-current-odroidxu4' Armbian: Debian compat: linux-update-symlinks install 6.6.75-current-odroidxu4 boot/vmlinuz-6.6.75-current-odroidxu4 I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.6.75-current-odroidxu4 I: /initrd.img.old is now a symlink to boot/initrd.img-6.6.75-current-odroidxu4 I: /vmlinuz is now a symlink to boot/vmlinuz-6.6.75-current-odroidxu4 I: /initrd.img is now a symlink to boot/initrd.img-6.6.75-current-odroidxu4 Armbian 'linux-image-current-odroidxu4' for '6.6.75-current-odroidxu4': 'postinst' finishing. Setting up bsdextrautils (2.38.1-5+deb12u3) ... Setting up libglib2.0-0:armhf (2.74.6-2+deb12u5) ... No schema files found: doing nothing. Setting up openssh-client (1:9.2p1-2+deb12u4) ... Setting up linux-dtb-current-odroidxu4 (25.2.1) ... Armbian 'linux-dtb-current-odroidxu4' for '6.6.75-current-odroidxu4': 'postinst' starting. Armbian: DTB: symlinking /boot/dtb to /boot/dtb-6.6.75-current-odroidxu4... 'dtb' -> 'dtb-6.6.75-current-odroidxu4' Armbian 'linux-dtb-current-odroidxu4' for '6.6.75-current-odroidxu4': 'postinst' finishing. Setting up tzdata (2024b-0+deb12u1) ... Current default time zone: 'Europe/Brussels' Local time is now: Tue Feb 11 09:39:21 CET 2025. Universal Time is now: Tue Feb 11 08:39:21 UTC 2025. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up udev (252.33-1~deb12u1) ... Setting up libsystemd-shared:armhf (252.33-1~deb12u1) ... Setting up udev (252.33-1~deb12u1) ... Setting up libsystemd-shared:armhf (252.33-1~deb12u1) ... Setting up ucf (3.0043+nmu1+deb12u1) ... Setting up armbian-firmware (25.2.1) ... Setting up libfdisk1:armhf (2.38.1-5+deb12u3) ... Setting up mount (2.38.1-5+deb12u3) ... Setting up libpython3.11-minimal:armhf (3.11.2-6+deb12u5) ... Setting up armbian-bsp-cli-odroidxu4-current (25.2.1) ... Armbian 'armbian-bsp-cli-odroidxu4-current' for '1-PC53a1-V25c0-Hdf3f-B6e44-R7697': 'postinst' starting. Armbian 'armbian-bsp-cli-odroidxu4-current' for '1-PC53a1-V25c0-Hdf3f-B6e44-R7697': 'postinst' finishing. Setting up rsync (3.2.7-1+deb12u2) ... rsync.service is a disabled or a static unit not running, not starting it. Setting up python3.11-minimal (3.11.2-6+deb12u5) ... Setting up openssh-sftp-server (1:9.2p1-2+deb12u4) ... Setting up openssh-server (1:9.2p1-2+deb12u4) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. ssh.socket is a disabled or a static unit not running, not starting it. Setting up libpython3.11-stdlib:armhf (3.11.2-6+deb12u5) ... Setting up systemd (252.33-1~deb12u1) ... Setting file flags is only supported on regular files and directories, cannot set on '/var/log/journal'. Setting up fdisk (2.38.1-5+deb12u3) ... Setting up armbian-config (25.5.0-trunk.38.0210.230140) ... Setting up systemd-timesyncd (252.33-1~deb12u1) ... Setting up systemd-resolved (252.33-1~deb12u1) ... Setting up python3.11 (3.11.2-6+deb12u5) ... Setting up systemd-sysv (252.33-1~deb12u1) ... Setting up libpam-systemd:armhf (252.33-1~deb12u1) ... Processing triggers for libc-bin (2.36-9+deb12u9) ... Processing triggers for man-db (2.11.2-2) ... Processing triggers for dbus (1.14.10-1~deb12u1) ... Processing triggers for initramfs-tools (0.142+deb12u1) ... update-initramfs: Generating /boot/initrd.img-6.6.75-current-odroidxu4 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.75-current-odroidxu4 Image Name: uInitrd Created: Tue Feb 11 09:40:34 2025 Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 10011910 Bytes = 9777.26 KiB = 9.55 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.75-current-odroidxu4 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.6.75-current-odroidxu4' update-initramfs: Armbian: done. Edited February 11 by Davy 0 Quote
ursa Posted February 11 Posted February 11 The same issue. Upgrade to latest from 24.8.4 or fresh install 25.2.1 to another SD card calls up a kernel panic. 0 Quote
belegdol Posted February 11 Posted February 11 Are you guys able to check which of the packages is causing trouble specifically? 0 Quote
Torgar Posted February 11 Posted February 11 This is associated with the kernel only. Compiled from source (6.6.75) and results in kernel panic. 0 Quote
pauet Posted February 11 Posted February 11 (edited) Same with odroid xu4. I have upgraded to 25.2.1 (kernel 6.6.75) from 24.11.1 (kernel 6.6.60) and now I have a kernel panic Edited February 12 by pauet 0 Quote
belegdol Posted February 11 Posted February 11 @Igor, is it possible to compare the kernel configurations used for the official build vs what I have running? 0 Quote
DMG Posted February 11 Posted February 11 Also same with odroid hc1. I have upgraded to 25.2.1 from 24.11.1 and now I have a kernel panic. Fresh installation with kernel 6.6.75 also have kernel panic. Previous image with kernel 6.6.60 working fine. Kernel 6.6.75 "don't see" HDD disks. 0 Quote
belegdol Posted February 11 Posted February 11 Comparing the two UART logs provided by @Davy, log containing ** File not found /boot/armbianEnv.txt ** ** Unrecognized filesystem type ** ** File not found armbianEnv.txt ** does boot, whereas log not containing these 3 lines ends with a kernel panic. Not sure whether this is relevant yet, but it is definitely interesting. 0 Quote
belegdol Posted February 11 Posted February 11 If you are able to read the panicking SD card in another PC, how does the folder structure look like? This is mine: $ sudo ls -Rlh /boot [sudo] password for julas: /boot: total 36M -rw-r--r-- 1 root root 78 Feb 6 13:26 armbianEnv.txt -rw-r--r-- 1 root root 0 Sep 6 2019 armbianEnv.txt.out -rw-r--r-- 1 root root 1.5K May 29 2018 armbian_first_run.txt.template -rw-r--r-- 1 root root 38K May 29 2018 boot.bmp -rw-r--r-- 1 root root 4.8K May 29 2018 boot-desktop.png -rw-r--r-- 1 root root 13K Sep 15 2022 boot.ini -rw-r--r-- 1 root root 0 Jun 25 2019 boot.ini.out -rw-r--r-- 1 root root 200K Feb 6 13:11 config-6.6.75-current-odroidxu4 lrwxrwxrwx 1 root root 28 Feb 6 13:24 dtb -> dtb-6.6.75-current-odroidxu4 drwxr-xr-x 2 root root 4.0K Feb 6 13:23 dtb-6.6.75-current-odroidxu4 -rw-r--r-- 1 root root 13M Feb 6 13:24 initrd.img-6.6.75-current-odroidxu4 drwx------ 2 root root 12K May 29 2018 lost+found -rw-r--r-- 1 root root 3.2M Feb 6 13:11 System.map-6.6.75-current-odroidxu4 lrwxrwxrwx 1 root root 32 Feb 6 13:24 uInitrd -> uInitrd-6.6.75-current-odroidxu4 -rw-r--r-- 1 root root 13M Feb 6 13:24 uInitrd-6.6.75-current-odroidxu4 -rw-r--r-- 1 root root 8.4M Feb 6 13:11 vmlinuz-6.6.75-current-odroidxu4 lrwxrwxrwx 1 root root 32 Feb 6 13:24 zImage -> vmlinuz-6.6.75-current-odroidxu4 /boot/dtb-6.6.75-current-odroidxu4: total 3.1M -rw-r--r-- 1 root root 1.7K Feb 6 13:11 ads7846.dtbo -rw-r--r-- 1 root root 42K Feb 6 13:11 exynos3250-artik5-eval.dtb -rw-r--r-- 1 root root 52K Feb 6 13:11 exynos3250-monk.dtb -rw-r--r-- 1 root root 59K Feb 6 13:11 exynos3250-rinato.dtb -rw-r--r-- 1 root root 69K Feb 6 13:11 exynos4210-i9100.dtb -rw-r--r-- 1 root root 60K Feb 6 13:11 exynos4210-origen.dtb -rw-r--r-- 1 root root 57K Feb 6 13:11 exynos4210-smdkv310.dtb -rw-r--r-- 1 root root 64K Feb 6 13:11 exynos4210-trats.dtb -rw-r--r-- 1 root root 65K Feb 6 13:11 exynos4210-universal_c210.dtb -rw-r--r-- 1 root root 98K Feb 6 13:11 exynos4212-tab3-3g8.dtb -rw-r--r-- 1 root root 98K Feb 6 13:11 exynos4212-tab3-lte8.dtb -rw-r--r-- 1 root root 99K Feb 6 13:11 exynos4212-tab3-wifi8.dtb -rw-r--r-- 1 root root 106K Feb 6 13:11 exynos4412-i9300.dtb -rw-r--r-- 1 root root 106K Feb 6 13:11 exynos4412-i9305.dtb -rw-r--r-- 1 root root 75K Feb 6 13:11 exynos4412-itop-elite.dtb -rw-r--r-- 1 root root 103K Feb 6 13:11 exynos4412-n710x.dtb -rw-r--r-- 1 root root 74K Feb 6 13:11 exynos4412-odroidu3.dtb -rw-r--r-- 1 root root 74K Feb 6 13:11 exynos4412-odroidx2.dtb -rw-r--r-- 1 root root 74K Feb 6 13:11 exynos4412-odroidx.dtb -rw-r--r-- 1 root root 73K Feb 6 13:11 exynos4412-origen.dtb -rw-r--r-- 1 root root 98K Feb 6 13:11 exynos4412-p4note-n8010.dtb -rw-r--r-- 1 root root 65K Feb 6 13:11 exynos4412-smdk4412.dtb -rw-r--r-- 1 root root 64K Feb 6 13:11 exynos4412-tiny4412.dtb -rw-r--r-- 1 root root 106K Feb 6 13:11 exynos4412-trats2.dtb -rw-r--r-- 1 root root 63K Feb 6 13:11 exynos5250-arndale.dtb -rw-r--r-- 1 root root 59K Feb 6 13:11 exynos5250-smdk5250.dtb -rw-r--r-- 1 root root 65K Feb 6 13:11 exynos5250-snow.dtb -rw-r--r-- 1 root root 65K Feb 6 13:11 exynos5250-snow-rev5.dtb -rw-r--r-- 1 root root 61K Feb 6 13:11 exynos5250-spring.dtb -rw-r--r-- 1 root root 27K Feb 6 13:11 exynos5260-xyref5260.dtb -rw-r--r-- 1 root root 45K Feb 6 13:11 exynos5410-odroidxu.dtb -rw-r--r-- 1 root root 35K Feb 6 13:11 exynos5410-smdk5410.dtb -rw-r--r-- 1 root root 74K Feb 6 13:11 exynos5420-arndale-octa.dtb -rw-r--r-- 1 root root 73K Feb 6 13:11 exynos5420-chagall-wifi.dtb -rw-r--r-- 1 root root 73K Feb 6 13:11 exynos5420-klimt-wifi.dtb -rw-r--r-- 1 root root 83K Feb 6 13:11 exynos5420-peach-pit.dtb -rw-r--r-- 1 root root 69K Feb 6 13:11 exynos5420-smdk5420.dtb -rw-r--r-- 1 root root 82K Feb 6 13:11 exynos5422-odroidhc1.dtb -rw-r--r-- 1 root root 89K Feb 6 13:11 exynos5422-odroidxu3.dtb -rw-r--r-- 1 root root 88K Feb 6 13:11 exynos5422-odroidxu3-lite.dtb -rw-r--r-- 1 root root 88K Feb 6 13:11 exynos5422-odroidxu4.dtb -rw-r--r-- 1 root root 74K Feb 6 13:11 exynos5422-samsung-k3g.dtb -rw-r--r-- 1 root root 84K Feb 6 13:11 exynos5800-peach-pi.dtb -rw-r--r-- 1 root root 1.3K Feb 6 13:11 hktft32.dtbo -rw-r--r-- 1 root root 1.8K Feb 6 13:11 hktft35.dtbo -rw-r--r-- 1 root root 1.5K Feb 6 13:11 hktft-cs-ogst.dtbo -rw-r--r-- 1 root root 224 Feb 6 13:11 i2c0.dtbo -rw-r--r-- 1 root root 226 Feb 6 13:11 i2c1.dtbo -rw-r--r-- 1 root root 417 Feb 6 13:11 onewire.dtbo -rw-r--r-- 1 root root 691 Feb 6 13:11 spi0.dtbo -rw-r--r-- 1 root root 792 Feb 6 13:11 sx865x-i2c1.dtbo -rw-r--r-- 1 root root 227 Feb 6 13:11 uart0.dtbo /boot/lost+found: total 0 0 Quote
odroidhc2 Posted February 12 Posted February 12 (edited) After this upgrade my Odroids HC2 wont boot 🤕 (linux-u-boot-odroid xu4-current 2017.05-S42ac-P3788-H27d6-Vc604-Bb703-R448a) I have two and both stuck on solid blue light. Can this be fixed without reinstall? Edited February 12 by odroidhc2 0 Quote
Valsi Posted February 12 Posted February 12 Same issue at my HC1 NAS. After update reboot was required and then no boot and no system LED. After power off and on sometimes no no system LED or even permanent system LED. 0 Quote
pauet Posted February 12 Posted February 12 (edited) I have downgraded kernel on my odroid xu4 and now is booting again. This were my steps: #mount sd (use lsblk to indentify your sd device) mount /dev/sda1 /mnt/armbi_root #install qemu to execute arm inside amd64 apt install qemu-user-static #and copy it to sd cp /usr/bin/qemu-arm-static /mnt/armbi_root/usr/bin/ #mount pseudo-filesystems needed mount -t proc /proc /mnt/armbi_root/proc mount --rbind /sys /mnt/armbi_root/sys mount --rbind /dev /mnt/armbi_root/dev mount --rbind /run /mnt/armbi_root/run #chrooting sd chroot /mnt/armbi_root /usr/bin/qemu-arm-static /bin/bash #show installed previous versions apt-cache madison linux-image-current-odroidxu4 apt-cache madison linux-dtb-current-odroidxu4 #install working previous version (mine was 24.11.1 - kernel-6.6.60) apt install linux-image-current-odroidxu4=24.11.1 apt install linux-dtb-current-odroidxu4=24.11.1 #rebuild initramfs (maybe this is not necessary, but do not harm) update-initramfs -u #exiting chroot exit #unmonting sd for finishing umount -R /mnt/armbi_root Edited February 12 by pauet 3 Quote
odroidhc2 Posted February 12 Posted February 12 One My Odroid HC2 boot from sd card but OS is on USB stick. Can I use above fix for that in the same way? 0 Quote
ursa Posted February 12 Posted February 12 Quote Can I use above fix for that in the same way? Yes, only you may be need additional libraries in /lib/modules for this kernel on USB stick, they are cleaned. I install old version on another SD and copy those files. 0 Quote
Davy Posted February 12 Posted February 12 I didn't have time to grab a linux laptop, so here is a listing of the contents of the boot folder. 0 Quote
Igor Posted February 12 Posted February 12 XU4 / HC1 is fixed by https://github.com/armbian/build/commit/5115cdf47a91f9cf5eb15f1b4984deebbe329002 Images are in generation, update is going out when possible. (broken updates were also disabled, but takes time for repo to sync) 4 Quote
boat Posted February 12 Posted February 12 We are in the same boat. One of our two HC's got restarted after the unattended and is now not starting anymore (probably boot-looping). I see the post from @pauet how to recover (thank's) but we don't have a (full blown) linux host on site - just a second HC's running armbian which still is alive (not rebooted). Any idea if (with the help of a windows host or the second armbian) the broken system can be recovered somehow? Thank's everyone! 0 Quote
Igor Posted February 12 Posted February 12 11 minutes ago, boat said: Any idea This can give some ideas: https://docs.armbian.com/User-Guide_Recovery/ (not exact walk trough, but the principle is the same) Note that fixed packages are not yet uploaded. In a couple of hours. 0 Quote
boat Posted February 12 Posted February 12 Thank's! Just in the process installing a debian virtual machine in the present windows host to recover the system like described. I now checked the second HC and found out that the "update of death" is already installed and the system requests a reboot. Obviously I didn't do it! I just hope we don't have a power outage until a fixed update is available (so far my system can't seem to find one). 0 Quote
boat Posted February 12 Posted February 12 5 hours ago, pauet said: #chrooting sd chroot /mnt/armbi_root /usr/bin/qemu-arm-static /bin/bash So I just installed debian in a virtual machine on a windows host and the sd card is their. Everything until chroot command worked fine but now I'm stuck getting: bash: chroot: command not found despite having chroot (gnu coreutils) 9.1 under /usr/sbin/chroot I somewhat didn't end up with a user account (without su) in debian (used the automated install from virtual box for the first time) so I elevated to root first thing and did everything as root - maybe that's a problem? I would be grateful for any hints! 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.