boat

Thank's, did this but wasn't enough. But now I found the secret as it now installed after issuing this weird command https://unix.stackexchange.com/a/674661

It looks a bit better with "apt install ./filename.deb" but for whatever reason I get a permission denied error despite being root. Maybe some chroot specialty I'm not aware of? So close to get the system working again but also so far.... 😫 Also tried chmod 777 on the deb files (root is already owner) but still the permission denied error.... I'm out of clue with a big headache trying since two days getting this thing working again just hitting about every tree on the way 😣 @odroidhc2 how did you manage installing the deb files in chroot?

Thank's Igor! I tried the docs but didn't find a hint on manual installing deb packages... with google fu I found the command "dpkg -i" that I tried but sadly failed: Forums are always great so users can help other users... specially who are in the same boat 🚣‍♂️ Keep up the great work with armbian!

Thank's for your answer. If I understand correct you downloaded outside of chroot then and copied the files over? What command did you use in the terminal to install the deb packages inside chroot please?

Could you drop a line or two on how to do this please? I can see wget is available but I don't even manage to localize the .deb packages with a IP address to download 😭 Thank's a lot!

That did the trick indeed! Thanks a million Werner! Now I'm stuck here as well 😢 I tried running "apt update" but the problem persists. How could I solve DNS problems? I'm first time doing chroot and I actually have around 0 clue what I do... I tried nslookup in the chroot shell but that is not available... Trying ping on google does indeed indicate hostnames cant be resolved 😭 I guess quickest fix would be just to download the package files from server via IP address and install them manually?

I used this command on a HC running OMV (armbian) which was not restarted with success! root@armbianomv:~# apt install linux-image-current-odroidxu4=24.11.1 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be DOWNGRADED: linux-image-current-odroidxu4 0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 4 not upgraded. Need to get 30.7 MB of archives. After this operation, 14.2 MB disk space will be freed. Do you want to continue? [Y/n] Y Get:1 http://netcup.armbian.com/apt bookworm/main armhf linux-image-current-odroidxu4 armhf 24.11.1 [30.7 MB] Fetched 30.7 MB in 4s (8521 kB/s) dpkg: warning: downgrading linux-image-current-odroidxu4 from 25.2.1 to 24.11.1 (Reading database ... 34762 files and directories currently installed.) Preparing to unpack .../linux-image-current-odroidxu4_24.11.1_armhf.deb ... Armbian 'linux-image-current-odroidxu4' for '6.6.75-current-odroidxu4': 'prerm' starting. Armbian 'linux-image-current-odroidxu4' for '6.6.75-current-odroidxu4': 'prerm' finishing. Armbian 'linux-image-current-odroidxu4' for '6.6.60-current-odroidxu4': 'preinst' starting. Armbian 'linux-image-current-odroidxu4' for '6.6.60-current-odroidxu4': 'preinst' finishing. Unpacking linux-image-current-odroidxu4 (24.11.1) over (25.2.1) ... Armbian 'linux-image-current-odroidxu4' for '6.6.75-current-odroidxu4': 'postrm' starting. Armbian 'linux-image-current-odroidxu4' for '6.6.75-current-odroidxu4': 'postrm' finishing. Setting up linux-image-current-odroidxu4 (24.11.1) ... Armbian 'linux-image-current-odroidxu4' for '6.6.60-current-odroidxu4': 'postinst' starting. update-initramfs: Generating /boot/initrd.img-6.6.60-current-odroidxu4 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.60-current-odroidxu4 Image Name: uInitrd Created: Thu Feb 13 12:50:07 2025 Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 13361420 Bytes = 13048.26 KiB = 12.74 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.60-current-odroidxu4 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.6.60-current-odroidxu4' update-initramfs: Armbian: done. Remove unused generated file: /boot/uInitrd-6.6.75-current-odroidxu4 Remove unused generated file: /boot/initrd.img-6.6.75-current-odroidxu4 Armbian: update last-installed kernel symlink to 'zImage'... '/boot/zImage' -> 'vmlinuz-6.6.60-current-odroidxu4' Armbian: Debian compat: linux-update-symlinks install 6.6.60-current-odroidxu4 boot/vmlinuz-6.6.60-current-odroidxu4 I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.6.60-current-odroidxu4 I: /initrd.img.old is now a symlink to boot/initrd.img-6.6.60-current-odroidxu4 I: /vmlinuz is now a symlink to boot/vmlinuz-6.6.60-current-odroidxu4 I: /initrd.img is now a symlink to boot/initrd.img-6.6.60-current-odroidxu4 Armbian 'linux-image-current-odroidxu4' for '6.6.60-current-odroidxu4': 'postinst' finishing. root@armbianomv:~#

Which host OS did you use? I struggle with a fresh debian install and passing your commands as root, I stuck with `chroot` (`bash: chroot: command not found`)

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!

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).

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!