HelmSecure / armbian-images

GNU General Public License v2.0
32 stars 6 forks source link

Will not boot after disabling unified cgroup support #25

Closed elyk53 closed 1 year ago

elyk53 commented 1 year ago

The device refuses to boot after updating armbianEnv to disable unified cgroup support (as recommended to enable docker support). Steps to reproduce:

  1. Flash Armbian_22.11.2-build-48_Helm-v2a_bullseye_legacy_4.4.213_minimal.img
  2. Log in as root, run through the initial setup process
  3. As recommended in https://github.com/HelmSecure/armbian-images/issues/1#issuecomment-1368289816, add a new line to the end of /boot/armbianEnv.txt containing: extraargs=systemd.unified_cgroup_hierarchy=0
  4. Update the boot image, also as recommended in that post:
    root@helm-v2a:~# mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
    Image Name:   
    Created:      Sat Feb 25 10:01:16 2023
    Image Type:   ARM Linux Script (uncompressed)
    Data Size:    3326 Bytes = 3.25 KiB = 0.00 MiB
    Load Address: 00000000
    Entry Point:  00000000
    Contents:
    Image 0: 3318 Bytes = 3.24 KiB = 0.00 MiB
  5. Reboot the helm
  6. The helm never comes back on the network; neither ping nor ssh connection is successful even after several minutes.

This started after I reflashed to pick up the fix for #10; prior to that change I was able to update armbianEnv and use docker.

I've tried running apt update && apt upgrade before regenerating the boot image, but that didn't make any difference. I did this both with the default APT sources and with switching from https://github.com/HelmSecure/armbian-packages to https://github.com/HelmSecure/armbian-packages-staging, as armbian-packages tries to downgrade uboot from 48 to 38.

If there's any other experiments that I can run to help shed light on this, please let me know.

dsigurds commented 1 year ago

After modifying the /boot/armbianEnv.txt file you do not need to run mkimage. That step is creating a boot.scr that is incompatible with the version of u-boot that's now in the 22.11.2-48 image. Thanks for the info about the package downgrade. I'll fix that by merging staging into production.

elyk53 commented 1 year ago

Tried without mkimage and that did the trick. Thanks for the quick response.