Closed Kreyren closed 6 months ago
Most of these options do not work
Partially agree with this
have potential to break the system such as the CRYPTROOT
Whats wrong with CRYPTROOT? I just fixed it couple of months ago. Are you facing any issue with it? if yes, could you please share your build logs?
Whats wrong with CRYPTROOT? I just fixed it couple of months ago. Are you facing any issue with it? if yes, could you please share your build logs? -- @viraniac (https://github.com/armbian/documentation/pull/360#issuecomment-1709774233)
For me when building olimex teres-a64 with full disk encryption it failed in a very dirty state and was pain to clean and make work again, try building the image on your end to see if you can reproduce that if not then i try to set up a container to test it :thinking:
For me when building olimex teres-a64 with full disk encryption it failed
Few months ago or today?
Few months ago or today? -- @igorpecovnik
~5 days ago
when building olimex teres-a64 with full disk encryption it failed in a very dirty state
@Kreyren Tried building on my machine just now. Builds fine, initrd contains all the files and hooks required to unlock cryptroot. I can't test if it boots cause I don't have the device. So you share your logs of failure or send me a teres a-64 to test things on.
@Kreyren in case you want to see my logs, check them here - https://paste.next.armbian.com/itixakicik
I do have some changes listed in the logs, but everything is related to Orange PI 3 LTS that I am trying to get into better state. Nothing related to cryptroot. Still builds fine
Most of these options do not work or have potential to break the system such as the CRYPTROOT -> Advice against using it until it's updated