The recovery.log is 0 bytes, so we fail before we write anything.

0.15.892.0 is the last image that is working. So from 0.15.893.0 onwards its not working.

(No comment was entered for this change.)

What is the X-86 platform here? A laptop? desktop?

And what is the "PVT" image for the platform?

Adding Restrict-View-Commit tag in case there's some confidential information...

Error message:
An unrecoverable error occurred with your security device.
Please power down and try again.
Failed to lock bGlobalLock.

TPM error?

Failed in src/platform/initramfs/recovery_init.sh -> (init)lock_tpm -> "tpmc block" command

Since initramfs has been not changed for a while (since Aug 9), I wonder if there's some TPM stuff changed in kernel side.

Hi Luigi, can you take a look at this issue?
Try to grab a x86 "recovery" image from image download side (CR48, Alex, ZGB seems all having this issue), boot with it, and it'll end as failure in TPM init.

(No comment was entered for this change.)

flipping restrictview bit again.

Looking at it now.

(No comment was entered for this change.)

Possible related bugs:
https://code.google.com/p/chromium-os/issues/detail?id=19242
https://code.google.com/p/chromium-os/issues/detail?id=19227

I reproduced this with 0.15.908.0, and I verified that it works with 0.15.892.0.

I looked at changes between versions 0.15.892.0 and 0.15.893.0 at http:chromeos-images/diff.  The only change is Anush's busybox change.  I expanded the search to include 0.15.891.0 and 0.15.894.0 but didn't see anything useful.

I did a repo sync, build_packages, etc. and rebuilt a recovery image with additional logging, but unfortunately the problem doesn't reproduce.

Just another one of those fun bugs.

initramfs is executed with busybox right?

Yes Hung-Te.  In fact I will check the syntax of that statement to see if it is non-standard.

Unfortunately I have to sign off for the day.  Would you be able to work on this now?  It's a big blocker.

I spent sometime today studying this but no results.
Adding more people who recently changed recovery/initramfs to see if anyone can help.

It's really difficult to debug the recovery initramfs.
Is there anyway to open a console, or change the content of initramfs without always rebuilding the kernel?

Commit: a7a0a856aaaef13d5b9a2bb7cab903b504d9119a
 Email: hungte@chromium.org

initramfs: fix recovery script failure by busybox upgrade

The "&>" (redirect both stdout and stderr) is supported in C shell, bash, and
some other shells, but not in original Bourne shell.

Latest busybox (introduced by http://gerrit.chromium.org/gerrit/5959) seems not
supporting this syntax anymore - it interprets that as "& >" (fork and execute
in background, then redirect stdout).

The more portable syntax is ">file 2>&1", which works fine on old and new
busybox.

BUG=chromium-os:19172
TEST=mod_image_for_recovery.sh; image_to_usb -i recovery_image.bin
     # verified on x86 devices, and the recovery program successfully finished.

Change-Id: I4f8f396ac163ce8b3c043dd04b60dbd201ee696c
Reviewed-on: http://gerrit.chromium.org/gerrit/6148
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Luigi Semenzato <semenzato@chromium.org>

M	init

This is believed fixed.  To verify, please check that the recovery installer works.

I've downloaded 0.15.913 and it seems working fine.

(No comment was entered for this change.)

verified in 0.15.916.0. All builds working fine on recovery image. 

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)