viking3r

So the prior replacement of the linux-image seems to be the culprit Makes sense in hindsight I now installed wireguard via sudo apt install -t buster-backports wireguard wireguard-dkms wireguard-tools linux-headers-legacy-odroidxu4 now it works I rebooted a couple of times no issues there. So in the end it seems like it was the install of wireguard who led to all of this. The one time I could reproduce the device not rebooting without having it installed must be something like tparsys said. So for now the problem is solved. And some knowledge was gained I should pay more attention when apt wants to install some packages.

So another try: I did a fresh install on sd card: moved install to hdd then update (via sudo apt update /upgrade) couple of random reboot attempts --> works installed wireguard: during the install this appears: Setting up linux-image-5.10.0-0.bpo.5-rt-armmp (5.10.24-1~bpo10+1) ... I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.14.222-odroidxu4 I: /initrd.img.old is now a symlink to boot/initrd.img-4.14.222-odroidxu4 I: /vmlinuz is now a symlink to boot/vmlinuz-5.10.0-0.bpo.5-rt-armmp I: /initrd.img is now a symlink to boot/initrd.img-5.10.0-0.bpo.5-rt-armmp /etc/kernel/postinst.d/initramfs-tools: Dunno if this is intended. But I would guess that replacing the kernel image is not a good thing ? I am not a linux pro so maybe its nothing. After reboot with wireguard the device does not come back up anymore. Will try armbianmonitor -u as well. Thanks

Update: So it turns out the fact I installed wireguard and docker and the hc1 wouldn't reboot after that was more or less random. I was able to replicate the not booting issue without installing these. I bought an uart adapter to be able to understand more what is going on. Here is the output: U-Boot 2017.05-armbian (Mar 08 2021 - 18:56:26 +0100) for ODROID-XU4 CPU: Exynos5422 @ 800 MHz Model: Odroid XU4 based on EXYNOS5422 Board: Odroid XU4 based on EXYNOS5422 Type: xu4 DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1 MMC Device 0 ( SD ): 59.5 GiB Card did not respond to voltage select! mmc_init: -95, time 11 *** 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 13366 bytes read in 22 ms (592.8 KiB/s) ## Executing script at 43e00000 ** File not found /boot/armbianEnv.txt ** ** Unrecognized filesystem type ** ** File not found armbianEnv.txt ** 5733224 bytes read in 463 ms (11.8 MiB/s) 22379925 bytes read in 1714 ms (12.5 MiB/s) 0 bytes read in 18 ms (0 Bytes/s) Found mainline kernel configuration 63518 bytes read in 68 ms (912.1 KiB/s) libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND Kernel image @ 0x40008000 [ 0x000000 - 0x577b68 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 22379861 Bytes = 21.3 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 4401281d Starting kernel ... Starting Kernel stays there forever no further progress. I am not sure about the armbianenv missing and why the boot.ini is missing ?

Hello, I own two odroid hc1 both run on armbian buster Kernel 4.14.222. With my second one I am experiencing something odd. I tried setting it up as a webserver with docker multiple times, at some point I have to reboot and then it never comes back up (not reachable via ssh). Now after each package install I tried rebooting to see if it comes back up. Below is a list of things I did in armbian after initial boot. - apt update --> reboots fine - apt dist-upgrade --> reboots fine -change hostname --> reboots fine - add docker armhf repository -install armbian to disk --> reboot stuck but with power cycle booted up - apt install docker-ce docker-ce-cli containerd.io -apt install docker-compose --> reboot fine -apt install wireguard from buster-backports via clia (-t option) --> no reboot possible, powercycle has no effect, the green led is on but not flashing, blue is flashing. drives makes some noise after powercycle, not reachable via ssh. I am a bit clueless what I am doing wrong. Is it the board, is it linux or is what I am doing the problem? I unfortunately do not own an UART USB-Debugging device. But if anyone can recommend something I will buy it.