No Bootable Kernel Found

[Packjackisback]

Describe the bug After install, I got the "no bootable kernel found" screen, and when I went to the reco screen I got the reason "No bootable kernel found"

System (please complete the following information):

• Board: octopus
• Version: 130
  • Installation method used: devmode installer

[Eboi47]

I would just recover the Chromebook and try murkmodding again. If that doesn't work then record the terminal output during installation and put it here.

[Packjackisback]

Yeah that was the second time, I'm gonna try one more time, then run it without wp tonight

[Packjackisback]

iirc the only error was the wp error for the flag change, but I worry this could be related to the recent changes.

[rainestorme]

Fascinating... I have no idea what could cause this but I can check codesearch to try to traceback the error a bit.

[rainestorme]

Looks to be able to be traced back to 2recovery_reasons.c: https://source.chromium.org/chromiumos/chromiumos/codesearch/+/main:src/platform/vboot_reference/firmware/2lib/2recovery_reasons.c?q=%22No%20bootable%20kernel%20found%22&ss=chromiumos%2Fchromiumos%2Fcodesearch Here's all the potential places where this could be raised: https://source.chromium.org/search?q=%22VB2_RECOVERY_RW_NO_KERNEL%22&sq=&ss=chromiumos%2Fchromiumos%2Fcodesearch

[Packjackisback]

Running it again rn, it is overwriting rn with no errors so far

[Packjackisback]

I'm wondering if it stems from how I am accessing devmode

[Packjackisback]

I am running sh1mmer, running unenroll, booting into devmode, running tpm manager + device management client, and powerwashing, then turning on the wifi and running the script.

[rainestorme]

You may be able to extract some log information from the stateful partition. If this error occurs again, can you boot into SH1mmer immediately after and check /mnt/stateful_partition for logs?

[Packjackisback]

I got a ton of flashrom errors at the end.

[Packjackisback]

booted this time, we'll see if it persists

[rainestorme]

I got a ton of flashrom errors at the end.

To be expected if WP is enabled.

[Packjackisback]

Hmm, hanged on boot and then went back to the transitioning to developer screen. Assuming this is intended behaviour?

[rainestorme]

Again, tracing it back in codesearch, the most critical file seems to be here. If I had to guess, this just has something to do with how verity is disabled during the image patching process.

[rainestorme]

Hmm, hanged on boot and then went back to the transitioning to developer screen. Assuming this is intended behaviour?

Intended behaviour.

[Packjackisback]

I don't feel like finding a proxy rn, as chromium.org is blocked, but I'll check chromium and try and figure it out in appx 5 minutes

[Packjackisback]

If it boots as expected should I close the issue? It clearly happens, but simply recovering a few times seems to have fixed it so far.

[rainestorme]

No, I'll leave it open incase someone else can repro.