sign_official_build.sh : rootfs hash mismatch during chromeos-install
Reported by
wenkai...@intel.com,
Feb 9 2017
|
|
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 Steps to reproduce the problem: 1. Verify a good OSimage.bin that can be installed to eMMC using chromeos-install 2. Sign the image again: /mnt/host/source/src/platform/vboot_reference/scripts/image_signing/sign_official_build.sh base OSimage.bin /mnt/host/source/src/platform/vboot_reference/tests/devkeys OSimage.bin.new 3. Boot OSimage.bin.new, and install to eMMC using chromeos-install What is the expected behavior? Installation is successful What went wrong? Setting up verity. dm:dm bht[DEBUG] Setting block_count 317440 dm:dm bht[DEBUG] Setting depth to 3. dm:dm bht[DEBUG] depth: 0 entries: 1 dm:dm bht[DEBUG] depth: 1 entries: 20 dm:dm bht[DEBUG] depth: 2 entries: 2480 Filesystem hash verification failed Expected 114a5d4699fe759b23707b4200da3e5dcceb897e != actual d2ead6598bb29867f71a07050295c421cc77816b Did this work before? N/A Chrome version: 58.0.3007 Channel: dev OS Version: 9267 Flash Version: Shockwave Flash 24.0 r0 Self image verification by following command show passing: /mnt/host/source/src/platform/vboot_reference/scripts/image_signing/sign_official_build.sh verify OSimage.bin.new |
|
►
Sign in to add a comment |
|
Comment 1 by sheriffbot@chromium.org
, Feb 12 2018