New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 776638 link

Starred by 1 user
Status: Assigned
Owner:
fshao@chromium.org
Cc:
chromeos-factory-eng@google.com
█ jrbarnette@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 768851



Sign in to add a comment

factory: Can not start if fixed storage is not readable

Project Member Reported by gwendal@chromium.org, Oct 20 2017 
Working on RMA'ed machine where the eMMC device is up but read commands fail, I can not start the factory image [6420.177.0]

The problem is in main() of src/platform/initramfs/recovery/init:
We try to find the root device in wait_for_gpt_root by calling cgpt find on all block devices. But if a block device fails to respond and hang the kernel we will never be able to continue.

Maybe add a 'removable device only' option to cgpt?

Comment 1 by gwendal@chromium.org, Oct 20 2017

Blockedon: -768851
Blocking: 768851

Comment 2 by hungte@chromium.org, Sep 7

Cc: chromeos-factory-eng@google.com
Labels: Hotlist-GoodFirstBug
Owner: fshao@chromium.org
Assign to fshao@ as first-bug for new factory team members.

Note this is actually modifying C program, not usual factory software.

Comment 3 by benhenry@google.com, Jan 11

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
►

Sign in to add a comment