New issue
Advanced search Search tips

Issue 621646 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

BUDDY Recovery Image is corrupt

Project Member Reported by jayhlee@google.com, Jun 20 2016

Issue description

Chrome OS Version: 7978.66.3
Chrome OS Platform: BUDDY / Acer Chromebase 24

Steps To Reproduce:
(1) Open Chrome OS Recovery Tool app, select "BUDDY " for image. Create image on USB Drive.
(2) Unplug USB Drive and plug back in.
(3) OBSERVE: No notifications of found disks, nothing mounted by existing Chrome OS install.
(4) Download current image to a Linux machine:

wget https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7978.66.3_buddy_recovery_stable-channel_mp.bin.zip

(5) Unzip:

unzip chromeos_7978.66.3_buddy_recovery_stable-channel_mp.bin.zip

(6) Attempt to examine partitions with parted:

sudo parted chromeos_7978.66.3_buddy_recovery_stable-channel_mp.bin
(parted) print list

OBSERVE: partitions not listed, error message:
Error: end of file while reading Success                                  
parted: invalid token: list

Expected Result:
Stateful and log partitions of recovery drive mounted when inserted in existing Chrome OS device.

parted lists 12 standard Chrome OS partitions on image.

Actual Result:
No partitions mounted for USB device with BUDDY image.

parted cannot read USB image's partitions

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always (confirmed issue is not due to USB issues)

What is the impact to the user, and is there a workaround? If so, what is
it?
I don't have a BUDDY device available to me today but can attempt recovery on one tomorrow to confirm if it's working with current image or completely fails. In any case, seems to be some level of corruption of recovery image.


 
Cc: ka...@chromium.org sontis@chromium.org

Comment 2 by son...@google.com, Jun 20 2016

Not able to reproduce this issue on M51 build 8172.56.0
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 21 2016

Labels: Hotlist-Google

Comment 4 by jayhlee@google.com, Feb 24 2017

Status: WontFix (was: Unconfirmed)
No longer able to repro this

Sign in to add a comment