No bootable kernel found on disk on reks |
||
Issue descriptionChromeOS version: 65.0.3325.184 /10323.62.0 ChromeOS device model: reks Case#: 15749347 Description: No bootable kernel found on disk on reks Steps to reproduce: 1. Leave devices charging for a couple of hours 2. Turn off the device 3. Turn on the device Current Behavior / Reproduction: No bootable kernel found on disk Expected Behavior: Device boots normally Per logs, I see that recovery keys were not pressed: 107 | 2017-09-05 11:34:55 | Wake Source | GPIO | 27 108 | 2017-09-05 11:35:00 | System boot | 867 109 | 2017-09-05 11:35:00 | System Reset 110 | 2017-09-05 11:35:00 | Wake Source | GPIO | 27 111 | 2017-09-05 11:35:01 | Chrome OS Recovery Mode | No bootable kernel found on disk | 0x5b 112 | 2017-09-05 11:38:13 | Power Button 113 | 2017-09-05 11:38:13 | ACPI Enter | S5 114 | 2017-09-05 11:38:18 | System boot | 868 115 | 2017-09-05 11:38:18 | ACPI Wake | S5 116 | 2017-09-05 11:38:18 | Wake Source | Power Button | 0 117 | 2017-09-05 11:38:18 | Wake Source | GPIO | 27 118 | 2017-09-05 11:38:25 | System boot | 869 119 | 2017-09-05 11:38:25 | System Reset 120 | 2017-09-05 11:38:25 | Wake Source | GPIO | 27 121 | 2017-09-05 11:38:25 | Chrome OS Recovery Mode | No bootable kernel found on disk | 0x5b 122 | 2017-09-05 11:38:31 | Power Button and so per https://bugs.chromium.org/p/chromium/issues/detail?id=738895#c39 Raising new bug Gwendal, can you please help to take a look?
,
Dec 14
Hello! This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time - If you are currently working on this bug, please provide an update. - If you are currently affected by this bug, please update with your current symptoms and relevant logs. If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary. Thank you!
,
Dec 20
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information. |
||
►
Sign in to add a comment |
||
Comment 1 by gwendal@chromium.org
, Aug 7