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

Issue 851139 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 23
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

[caroline-arcnext] Recovery install failed

Project Member Reported by abod...@chromium.org, Jun 8 2018

Issue description

ChromeOS:10763.0.0/Chrome:69.0.3452.0

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

Steps To Reproduce:
(1)Try to install caroline-arcnext recovery image 
(2)
(3)

Expected Result:
Recovery should be successful.
 
Actual Result:
Recovery install failed. 

log info 
****************************************************************************************

CHROMEOS_ARC_ANDROID_SDK_VERSION=28
CHROMEOS_ARC_VERSION=4827612
CHROMEOS_AUSERVER=https://tools.google.com/service/update2
CHROMEOS_BOARD_APPID={E4E99475-2297-3104-EF71-064182D67DA2}
CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1}
CHROMEOS_DEVSERVER=
CHROMEOS_RELEASE_APPID={E4E99475-2297-3104-EF71-064182D67DA2}
CHROMEOS_RELEASE_BOARD=caroline-arcnext-signed-mpkeys
CHROMEOS_RELEASE_BRANCH_NUMBER=0
CHROMEOS_RELEASE_BUILDER_PATH=caroline-arcnext-release/R69-10763.0.0
CHROMEOS_RELEASE_BUILD_NUMBER=10763
CHROMEOS_RELEASE_BUILD_TYPE=Official Build
CHROMEOS_RELEASE_CHROME_MILESTONE=69
CHROMEOS_RELEASE_DESCRIPTION=10763.0.0 (Official Build) dev-channel caroline-arcnext 
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_PATCH_NUMBER=0
CHROMEOS_RELEASE_TRACK=dev-channel
CHROMEOS_RELEASE_VERSION=10763.0.0
DEVICETYPE=CHROMEBOOK
GOOGLE_RELEASE=10763.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 3584000 verity payload=PARTUUID=%U/PARTNROFF=1 hashtree=PARTUUID=%U/PARTNROFF=1 hashstart=3584000 alg=sha1 root_hexdigest=835863fb197a5d235054e2fa67ac5f39062879f0 salt=49a7f0633ea7f9db217afff2c26549ede2fa2eb656126e1fb7754c788d607538" noinitrd vt.global_cursor_default=0 kern_guid=%U add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic intel_idle.max_cstate=7  
Setting up verity.
Finished after 12 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
Checking /mnt/stateful_partition/unencrypted permission.
RemovePackFiles Failed
Touch(/mnt/stateful_partition/.install_completed) FAILED
Starting firmware updater (//usr/sbin/chromeos-firmwareupdate --mode=recovery)
Command: //usr/sbin/chromeos-firmwareupdate --mode=recovery
Starting Google_Caroline firmware updater v4 (recovery)...
 - Updater package: [RO:Google_Caroline.7820.300.0 RW:Google_Caroline.7820.356.0 / EC:caroline_v1.9.375-8829f10 / PD:caroline_pd_v1.9.375-8829f10]
 - Current system:  [RO:Google_Caroline.7820.300.0 , ACT:Google_Caroline.7820.300.0 / EC:caroline_v1.9.402-1d45472 / PD:caroline_pd_v1.9.402-1d45472]
 - Write protection: Hardware: off, Software: Main=off EC=ON PD=off
recovery: update RO+RW
 * invoke: flashrom -p host --fast-verify -w bios.bin
 Execution failed (255): flashrom -p host --fast-verify -w bios.bin
 Messages:
Calibrating delay loop... OK.
coreboot table found at 0x7ab82000.
Erasing and writing flash chip... Verifying flash... FAILED
flashrom v0.9.9  : 5503150 : Jun 06 2018 04:28:48 UTC on Linux 3.18.0-17855-g91277127d929 (x86_64)
WARNING: SPI Configuration Lockdown activated.
VERIFY FAILED at 0x000001f5! Expected=0x84, Read=0x82, failed byte count from 0x00000000-0x00ffffff: 0x1
Your flash chip is in an unknown state.
Get help on IRC at irc.freenode.net (channel #flashrom) or
mail flashrom@flashrom.org with FAILED: your board name in the subject line!
-------------------------------------------------------------------------------
DO NOT REBOOT OR POWEROFF!
ERROR: Execution FAILED.
ERROR: Execution failed: ./updater4.sh (error code = 1)
Finished after 24 seconds.
Failed Command: //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



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

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
155 KB View Download
Cc: pgangishetty@chromium.org
Cc: bhthompson@chromium.org
Labels: -ReleaseBlock-Dev
What build of device was this done on? It looks like the WP is disabled however the firmware is unable to write a portion of the SPI flash.

My suspicion is that this system has a locked ME, and we are trying to overwrite it here.

...
VERIFY FAILED at 0x000001f5! Expected=0x84, Read=0x82, failed byte count from 0x00000000-0x00ffffff: 0x1
...

This is probably WAI, we could get past this by either enabling WP so the firmware updater does not try to overwrite this, or by flashing the newer firmware with a servo to update the ME.

If this can repro on a production unit with a WP enabled SPI flash this may be blocking, but if this is on a developer unit only we don't need to block anything.
Status: WontFix (was: Untriaged)
updater4 has been deprecated and since updater5 we have a better way to handle ME updates. Please re-open or create another issue if you see such error again.

Sign in to add a comment