Issue 403003 in chromium: Daisy: Not able to install recovery image.

[chro...@googlecode.com]

Status: Untriaged
Owner: ----
CC: ka...@chromium.org, venkatar...@chromium.org, son...@chromium.org,
helenzh...@chromium.org, hun...@chromium.org
Labels: Type-Bug-Regression Pri-1 Cr-Internals-Installer OS-Chrome M-38
ReleaseBlock-Dev

New issue 403003 by chiraggu...@chromium.org: Daisy: Not able to install
recovery image.
http://code.google.com/p/chromium/issues/detail?id=403003

Version: 6146.0.0
OS: Chrome

What steps will reproduce the problem?
1. Try installing recovery image using usb recovery stick.

What is the expected output?
The image should be installed.

What do you see instead?
The image is not installed.

Please use labels and text to provide additional information.
ChromeosChrootPostinst(6146.0.0)
Set boot target to /dev/mmcblk0p3: Partition 3, Slot A
SetImage
KERNEL_CONFIG: console= loglevel=7 init=/sbin/init cros_secure oops=panic
panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3
dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2506752
verity payload=PARTUUID=%U/PARTNROFF=1 hashtree=PARTUUID=%U/PARTNROFF=1
hashstart=2506752 alg=sha1
root_hexdigest=9d6d7136d1e5ab5b418684625c4312a0af859048
salt=104aa0f87e61b009efe4dda82daeeee7d1e0866df54a4831f79662e95915727f"
noinitrd vt.global_cursor_default=0 kern_guid=%U
Setting up verity.
Finished after 32 seconds.
Clearing network driver boot cache: /var/lib/preload-network-drivers.
Syncing filesystems before changing boot order...
Finished after 0 seconds.
Updating Partition Table Attributes using CgptManager...
Updated kernel 2 with Successful = 1 and NumTriesLeft = 6
RemovePackFiles Failed
Touch(/mnt/stateful_partition/.install_completed) FAILED
Starting firmware updater
(/tmp/install-mount-point/usr/sbin/chromeos-firmwareupdate --mode=recovery)
Command: /tmp/install-mount-point/usr/sbin/chromeos-firmwareupdate
--mode=recovery
Starting Snow firmware updater v4 (recovery)...
- Updater package: [Google_Snow.2695.117.0 / EC:snow_v1.3.139-375eb9f]
- Current system: [RO:Google_Snow.2695.132.0 , ACT:Google_Snow.2695.132.0
/ EC:snow_v1.3.139-375eb9f]
- Write protection: Hardware: ON, Software: Main=off EC=off
Detected x16 hardware - switching to x16 firmware now
RO BIOS: 2695.132.0, RW BIOS: 2695.132.0, EC: 2695.132.0
ERROR: Execution failed: ./updater4.sh (error code = 1)
Finished after 3 seconds.
Failed Command: /tmp/install-mount-point/usr/sbin/chromeos-firmwareupdate
--mode=recovery - Exit Code 1
Firmware update failed (error code: 1).
Rolling back update due to failure installing required firmware.
Successfully updated GPT with all settings to rollback.
PostInstall Failed
Running a hw diagnostics test -- this might take a couple minutes.



Attachments:
recovery.log 189 KB

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #10 on issue 403003 by hun...@chromium.org: Daisy: Not able to

install recovery image.
http://code.google.com/p/chromium/issues/detail?id=403003

Ok, got it. My tests were based on WP=ON, and these devices have WP=OFF and
caused a special case to fall into failure.

[chro...@googlecode.com]

Comment #11 on issue 403003 by hun...@chromium.org: Daisy: Not able to

install recovery image.
http://code.google.com/p/chromium/issues/detail?id=403003

Fix in https://chromium-review.googlesource.com/#/c/212231

[chro...@googlecode.com]

Comment #12 on issue 403003 by hun...@chromium.org: Daisy: Not able to

install recovery image.
http://code.google.com/p/chromium/issues/detail?id=403003

Re#6: Yes it's related to 165962. Sorry.

[chro...@googlecode.com]

Comment #13 on issue 403003 by josa...@chromium.org: Daisy: Not able to

install recovery image.
http://code.google.com/p/chromium/issues/detail?id=403003

HungTe, could you also land the fix in the dev mini-branch
(stabilize-6146.B)?

[chro...@googlecode.com]

Comment #14 on issue 403003 by hun...@chromium.org: Daisy: Not able to

install recovery image.
http://code.google.com/p/chromium/issues/detail?id=403003

The one for dev mini-branch:
https://chromium-review.googlesource.com/#/c/212246

[chro...@googlecode.com]

Comment #15 on issue 403003 by bugdro...@chromium.org: Daisy: Not able to
install recovery image.
http://code.google.com/p/chromium/issues/detail?id=403003#c15

Project: chromiumos/platform/firmware
Branch : stabilize-6146.B
Author : Hung-Te Lin <hun...@chromium.org>
Commit : f65056a647d2a9d9ee5d0fc1adc59a1115b478ed

Code-Review 0 : Hung-Te Lin, chrome-internal-fetch
Code-Review +2: Rong Chang
Commit-Queue 0 : Rong Chang, chrome-internal-fetch
Commit-Queue +1: Hung-Te Lin
Verified 0 : Rong Chang, chrome-internal-fetch
Verified +1: Hung-Te Lin
Change-Id : I8c51f857130cc5a9c4a186f9c9645a97d5f4d480
Reviewed-at : https://chromium-review.googlesource.com/212246

crosutil: Fix cros_override_rw_firmware_by_version when WP is disabled.

When WP is disabled, we should simply return true for recovery mode,
otherwise
updater may stop without error messages.

BUG=chromium:403003
TEST=unittest: ./crosutil_unittest # fail if this fix is not applied.
chromeos-firmwareupdate --debug --mode=recovery --wp=0

Original-Change-Id:
https://chromium-review.googlesource.com/#/q/I6042920e0018960a2c6a55c341e990e995b63ddc,n,z

pack_dist/crosutil.sh
unittests/crosutil_unittest

[chro...@googlecode.com]

Comment #16 on issue 403003 by bugdro...@chromium.org: Daisy: Not able to
install recovery image.
http://code.google.com/p/chromium/issues/detail?id=403003#c16

Project: chromiumos/platform/firmware
Branch : master
Author : Hung-Te Lin <hun...@chromium.org>
Commit : 18d4a5532635b61930618abd575f222da181c690

Code-Review 0 : Hung-Te Lin, Katie Roberts-Hoffman, chrome-internal-fetch
Code-Review +2: Daisuke Nojiri
Commit-Queue 0 : Daisuke Nojiri, Katie Roberts-Hoffman,

chrome-internal-fetch
Commit-Queue +1: Hung-Te Lin

Verified 0 : Daisuke Nojiri, Katie Roberts-Hoffman,

chrome-internal-fetch
Verified +1: Hung-Te Lin

Change-Id : I6042920e0018960a2c6a55c341e990e995b63ddc
Reviewed-at : https://chromium-review.googlesource.com/212231

crosutil: Fix cros_override_rw_firmware_by_version when WP is disabled.

When WP is disabled, we should simply return true for recovery mode,
otherwise
updater may stop without error messages.

BUG=chromium:403003
TEST=unittest: ./crosutil_unittest # fail if this fix is not applied.
chromeos-firmwareupdate --debug --mode=recovery --wp=0

[chro...@googlecode.com]

Updates:
Status: Fixed

Comment #17 on issue 403003 by hun...@chromium.org: Daisy: Not able to

install recovery image.
http://code.google.com/p/chromium/issues/detail?id=403003

Please try again, thanks!