g00d

Hello all, meanwhile I purchased the USB UART serial kit to watch the u-boot process. I sticked to the tutorial here, I tried many times and as explained before the odroid-hc2 is not reachable when rebooting. U-Boot serial log: U-Boot 2017.05-armbian (Oct 08 2021 - 19:51:17 +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 ): 29.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 13370 bytes read in 44 ms (295.9 KiB/s) ## Executing script at 43e00000 57 bytes read in 84 ms (0 Bytes/s) 7337840 bytes read in 816 ms (8.6 MiB/s) 11083175 bytes read in 1153 ms (9.2 MiB/s) ** File not found /boot/.next ** ** Unrecognized filesystem type ** ** File not found .next ** 88701 bytes read in 184 ms (470.7 KiB/s) libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND Kernel image @ 0x40008000 [ 0x000000 - 0x6ff770 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11083111 Bytes = 10.6 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 44018a7c Starting kernel ... Loading, please wait... Starting version 247.3-6 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Waiting up to 180 secs for eth0 to become available ... Begin: Running /scripts/local-top ... Please unlock disk rootfs: as you see, the ODROID-HC2 asks for the rootfs password. The network is NOT up, but I'd expect it to. Without network one cannot connect and unlock the rootfs as explained in the tutorial. Can anyone dig into it and tell us more? How can this be solved? How do we instruct the network to get enabled BEFORE ? thank you EDIT: while I wrote this post the serial console throwed additional lines, see here Begin: Mounting root file system ... Begin: Waiting up to 180 secs for eth0 to become available ... Begin: Running /scripts/local-top ... Please unlock disk rootfs: Failure: Interface eth0 e done. ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure /scripts/init-premount/dropbear: .: line 329: can't open '/run/net-eth0.conf': No such file or directory why does the system fail to init the ethernet network ? I tried both variants in initramfs.conf, DEVICE=eth0 but also with static IP. The serial log above shows the output when I used DEVICE=eth0

here too, the file /boot/armbianEnv.txt is not present in the latest Armbian image I use for the ODROID-HC2.

hi Steven. The hardware IS ok. Tried many other micro SD cards which are proven to be good and we also tried the same procedure on a friends' ODROID-HC2. I can install and run all various images in the "normal" unencrypted state. But the full-encrypted setup does not boot.

@Steven: I have no clue how if the ODROID-HC2 has a serial port and how to connect to it. I searched the net and found this thread which leads to this USB UART module kit. Honestly said, I don't think this is the right way as I'd have to spend more money, just to be able to connect with serial port to the device. Maybe there's a more convenient way to achieve this? @Werner: Thanks for the hint. I mounted the micro-SD card onto my notebook, then I touched the hidden file and also added the verbosity level 7 to the armbianEnv.txt inside the boot partition. Then I inserted the micro-SD back into the ODROID-HC2 and tried booting which will fail of course. Then I wait for 5mins, turn off the ODROID-HC2 and reinsert the micro-SD into the notebook. I mount the encrypted LUKS partition to /mnt and the unencrypted boot partition to /mnt/boot. When I look inside /mnt/var/log folder, there is absolutely no syslog, no daemon.log, no messages, no kern.log ... I guess this is an additional indicator that shows the system was not booting at all. Is there any other way than serial debugging to find out what is causing the problem ?

Hello Nico. The system is not booting, the NIC is not up, there is no IP (tried both DHCP and static IP address) so I cannot SSH into it. My thought was that I fail boot, then unmount the micro-SD card and mount it on another host and check the dmesg or syslog but I wasn't able to find any useful information in the log files under /var/log. I even don't know how to view and debug via serial console that's why I asked here can I debug somehow through serial console on the ODROID-HC2 and see what is going wrong during the boot process? Thanks for the hint about OMV, but that is not what I aiming for.

Hello Nico, I appreciate the feedback but I'm really curious if you red my question at all

Hello all, I am unsuccessful in setting up FDE (Full-Disk-Encryption) on an ODROID HC-2. This device has no display output and I have no clue if and how it's possible to debug the boot issue. The boot is done through the micro-SD card and I can mount the micro-SD card successfully on any other host for insight. Is there any known trick how to see what fails during the boot process? How can I do this?

Hi again. The error I complained about in the last post related to CRYPTO_BOOT CRYPTO_ROOT in Step8) s not an error, but had been seen/written incorrectly by me. Was my mistake, sorry. However, I just can't get this to work with full encryption on the ODROID-HC2. Whenever I try to start the ODROID-HC2 with the new created full-encrypted microSD card I never see my ODROID-HC online, no IP in the network, no ping, not possible to ssh into the configured 2222 dropbear port.I have now made the following attempts in the meantime: 1) booted with the microSD card, quite normal into the Armbian operating system. Then inserted an empty USB stick and transferred with nand-sata-install the root filesystem to the USB stick. The microSD is now only used for booting the /boot partition, the filesystem was swapped to the USB stick. This allows me to easily "umount /boot" and then remove the microSD card while the Armbian OS is running. Then I inserted the second empty microSD into the slot of the ODROID-HC2 and went through the entire tutorial point by point exactly as indicated. For me, the startup sector is 8192, so I configured it accordingly. 2) In Step9.1) I have manually created the boot/armbianEnv.txt and fed it with the three lines. In step 9.2 I tried three things. First with device=eth0 to get the lease via DHCP, but it didn't work. Then I tried the manual IP assignment, also with eth0 specification. Did not work either. And last but not least I switched back to DEVICE=eth0 but replaced eth0 with enx001e06123456 because my running Armbian OS uses this interface name where 123456 is the real MAC address of the NIC. But this did not help either. 3) In step 9.8) I was unsure if I need the line. What is meant by "If the target system is an Ubuntu bionic?" that confuses me. Surely the target system is Armbian ??? Anyway, I have tried both possibilities. Once without this line and once with this line. However, neither of them worked. In step 10.2) I installed "cryptsetup-initramfs" and "dropbear-initramfs". Did not work. Then I tried the variant by installing also the package "cryptsetup". But again without success. EDIT: I see on the /boot partition unter /boot/boot.ini those lines: # this is for mainline only if test "${board_name}" = "xu4"; then setenv fdtfile "exynos5422-odroidxu4.dtb"; fi if test "${board_name}" = "xu3"; then setenv fdtfile "exynos5422-odroidxu3.dtb"; fi if test "${board_name}" = "xu3l"; then setenv fdtfile "exynos5422-odroidxu3-lite.dtb"; fi if test "${board_name}" = "hc1"; then setenv fdtfile "exynos5422-odroidhc1.dtb"; fi ODROID-HC2 seems missing here. Can that cause the trouble ? I have now prepared dozens of times my microSD as described in the instructions but the ODROIC-HC board just does not come online. The LEDs all light up as usual, nothing inconspicuous here. But no ping, no IP in the subnet (I checked by nmap scans and insight in my network router) and so I can't ping the rebooted system at all first. The ODROID-HC2 also has no video output, which means I have no way to see where the error is, or where it hangs. What else should I try, where could the worm be buried? Hope someone can help me.

Hello and first things first MANY THANKS for this great tutorial!!! And I think I have discovered a small typo which will cause the tutorial to fail at that particular step. See here Step 8 - Prepare the target system chroot # BOOT_PART=($(lsblk -l -o NAME,LABEL | grep CRYPTO_BOOT)) # ROOT_PART=${BOOT_PART%1}2 # ROOT_UUID="$(lsblk --nodeps --noheadings --output=UUID /dev/$ROOT_PART)" # BOOT_UUID="$(lsblk --noheadings --output=UUID /dev/$BOOT_PART)" this line here: # BOOT_PART=($(lsblk -l -o NAME,LABEL | grep CRYPTO_BOOT)) should be correctly # BOOT_PART=($(lsblk -l -o NAME,LABEL | grep CRYPTO_ROOT)) ,,,BOOT should be ,,,ROOT (see commands above for clarification) Unfortunately, I was not successful with the full encryption. I got an ODROID-HC2 as a gift and wanted to try a full encryption with the latest Armbian. I got stuck already at the beginning. In the requirements it says that you have to do it on an already running Armbian host and on the other hand you have to have a free card/reader on the respective host with which you can write to a free SD card. [ The ODROID-HC2 unfortunately has only one micro-SD slot, but it already has my micro-SD card 1 running on the Armbian Bullseye. I can badly pull out during operation this micro-SD card 1 and instead simply insert the empty micro-SD card 2 :-) I have no external SD-card reader which I could attach to the USB port of my ODROID-HC2. So I tried the following. I just used a USB stick (8GB) instead of the empty SD card 2 (32GB) and wrote all the procedure explained in the tutorial to the USB stick, so the target was the USB stick. After everything was successfully completed I removed the USB stick and the micro-SD2 from the ODROID-HC2 and plugged it into my Linux desktop PC. The USB stick was "sdb" and the microSD card was "sdc". I then cloned the contents of the USB stick I just created to the blank micro-SD card 2. dd if=/dev/sdb of=/dev/sdc bs=1M && sync but unfortunately it did not work. When I put the microSD card into the ODROID-HC2 and boot then I can neither ping nor connect via dropbear/ssh under the configured port. So it seems that the system is not reachable. I noticed that according to the tutorial you should enter DEVICE=eth0 in boot.ini. However, on my ODROID-HC2 with the Armbian bullseye image, the network interface is enx001e06xxxxxx where the numbers/letters after the prefix enx corresponds to the MAC address of the ODROID-HC2. I wonder if this is the error? Would I then have to enter the hardware MAC address in the boot.ini accordingly so device=enx001e06xxxxxx before I had generated the initram? maybe there are ODROID-HC2 users among you who have already done it and can give help? am curious and looking forward to helpful contributions. Thanks in advance.