Jump to content

Trouble with Armbian Build CRYPTROOT "Starting Kernel..."


Recommended Posts

Posted

Hi guys,

 

I've been trying to build Armbian with an encrypted rootfs, but I can't get it work...

 

If I build Armbian with the following build options it works fine:

 

sudo ./compile.sh  \
BOARD=odroidxu4 \
BRANCH=current \
RELEASE=buster \
BUILD_MINIMAL=no \
BUILD_DESKTOP=no \
KERNEL_ONLY=no \
KERNEL_CONFIGURE=no \
COMPRESS_OUTPUTIMAGE=sha,gpg,img

 

But if I build Armbian with these build options (as above but including the CRYPTROOT options) it doesn't work:

 

sudo ./compile.sh  \
BOARD=odroidxu4 \
BRANCH=current \
RELEASE=buster \
BUILD_MINIMAL=no \
BUILD_DESKTOP=no \
KERNEL_ONLY=no \
KERNEL_CONFIGURE=no \
COMPRESS_OUTPUTIMAGE=sha,gpg,img \
CRYPTROOT_ENABLE=yes \
CRYPTROOT_PASSPHRASE="yourpassword" \
CRYPTROOT_SSH_UNLOCK=yes \
CRYPTROOT_SSH_UNLOCK_PORT=2222

 

When I try to boot the image created with the CRYPTROOT options it gets stuck on "Starting Kernel...".

 

For reference the SBC I'm using is an Odroid HC2 with a serial console, and the build environment is as per the the documentation (Ubuntu Hirsute 21.04.x amd64 running as a virtual machine).

 

Is there anything that I'm doing wrong, or is there be something that I should be checking?

Posted

Forgive me if this is a dumb question but do I need to create the armbianEnv.txt file myself? The file doesn't exist in /boot...

 

I managed to get it to boot successfully by changing:

 

setenv console "both"

 

...to:

 

setenv console "serial"

 

...in boot.ini, but I note that it says:

 

# DO NOT EDIT THIS FILE
#
# Please edit /boot/armbianEnv.txt to set supported parameters

 

...so I'm obviously doing the wrong thing. :)

Posted

Just took a look. I don't see ArmbianEnv.txt on the stock image on the download page. Might be a bug?

 

Might be this one? Not clear on the rationale. https://github.com/armbian/build/issues/1538

 

You can do one of these things:

  1. Create ArmbianEnv.txt with the options you need?
  2. Modify boot.ini, and accept it will eventually break on some upgrade

You can also ask the Subforum for XU4 Support to see if anyone has any insight on why that's missing from the stock build? I would phrase it in terms of why that file is missing from the official build, not yours.

 

But expect the answer might go for both.

This thread is quite old. Please consider starting a new thread rather than reviving this one.

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines