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

Issue 693767 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Recovery images fail : Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

Project Member Reported by bleung@chromium.org, Feb 17 2017

Issue description

<b>Chrome Version: <From about:version: Google Chrome x.x.x.x></b>
Chrome OS Version: 58.9292.0
Chrome OS Platform: Samus, Reef
<b>Network info: <network, encryption type, router model (if known)></b>

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) Grab 9292.0 signed recovery image from goldeneye
(2) put samus or reef into recovery mode
(3) plug in the drive.

Expected Result:
Successful recovery.

Actual Result:
Failed.

+ dlog Installing software; this will take some time.
+ tee -a /run/frecon/vt1 /run/frecon/vt2
+ echo Installing software; this will take some time.
Installing software; this will take some time.
+ dlog See the debug log on VT3 for the full output.
+ tee -a /run/frecon/vt1 /run/frecon/vt2
+ echo See the debug log on VT3 for the full output.
See the debug log on VT3 for the full output.
+ echo 1
+ chroot /usb /usr/sbin/chromeos-recovery /dev/sda
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
.: 848: Can't open /tmp/tmp.pgfQ9Dl4Pn/usr/sbin/write_gpt.sh
/usr/sbin/chromeos-install: 1: DST: parameter not set
+ local install_status=127
+ [ 127 -ne 0 ]
+ dlog WARNING!!! Installation of software failed. Displaying hw diagnostics
+ echo WARNING!!! Installation of software failed. Displaying hw diagnostics
+ tee -a /run/frecon/vt1 /run/frecon/vt2

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always 

What is the impact to the user, and is there a workaround? If so, what is
it?

Please provide any additional information below. Attach a screen shot or
log if possible.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.


 
recovery.log
77.3 KB View Download

Comment 1 by bleung@chromium.org, Feb 17 2017

Cc: jrbarnette@chromium.org
Doesn't fail on 9285.0. I'll bisect down to the exact build this started.

Comment 2 by bleung@chromium.org, Feb 17 2017

Owner: bleung@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 3 by bleung@chromium.org, Feb 17 2017

first build to fail is 9288.0 Looking at changes now. 
https://crosland.corp.google.com/log/9287.0.0..9288.0.0

Comment 4 by bleung@chromium.org, Feb 17 2017

Status: WontFix (was: Assigned)
Tracked here : https://code.google.com/p/chrome-os-partner/issues/detail?id=62989

Sign in to add a comment