New issue
Advanced search Search tips

Issue 767923 link

Starred by 5 users
Status: Untriaged
Merged: issue 760007
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Asus Chromebit losing enrollment after September 18th platform release

Reported by google.a...@wandcorp.com, Sep 22 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.18 Safari/537.36
Platform: 9592.96.0

Steps to reproduce the problem:
1. Have enrolled ASUS devices previously on R59
2. Allow OS updates
3. 

What is the expected behavior?
Device updates to R60 while remaining enrolled.

What went wrong?
Device crashes and loses enrollment

Did this work before? N/A 

Chrome version: 62.0.3202.18  Channel: stable
OS Version: 	 60.0.3112.114
Flash Version: 

This is impacting approximately 10% of enrolled ASUS devices currently.
logs_20170920-1601.zip
114 KB Download

Comment 1 by google.a...@wandcorp.com, Sep 22 2017 

This is actually reproducible on AOPEN and ASUS devices by doing a flash drive recovery which puts them on R57. When you try to update the device you get a warning that the OS is missing.

This has occurred on 6 of the 20 devices were are setting up today for our continuing digital signage roll outs.

Comment 2 by georgesak@chromium.org, Sep 22 2017

Labels: Enterprise-Triaged
Owner: dskaram@chromium.org
Status: Untriaged (was: Unconfirmed)
+dskaram for triage

Comment 3 by dskaram@google.com, Sep 22 2017

Mergedinto: 760007
Owner: ----
Status: Duplicate (was: Untriaged)

Comment 4 by gwendal@chromium.org, Sep 22 2017

Status: Available (was: Duplicate)
missing OS is not the same as 760007: in case of 760007, you "just" lose enrollment, not the full OS.

The log provided are sparse: no storage_info.txt, no ec.log (maybe these devices have none)

It would be interesting to grab console-ramoops when the device crashes.
I am suspecting we crash in a loop, preventing the GPT flag "successful" to be set. After few tries, we should rollback to the previous version. If that fails, coreboot would not have any kernel to boot from.

Recovery reason should be: "0x5b No bootable kernel found on disk"
Project Member

Comment 5 by sheriffbot@chromium.org, Sep 24

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment