New issue
Advanced search Search tips

Issue 739481 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
jwer...@chromium.org
amstan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

veyron: invalid recovery image

Project Member Reported by gwendal@chromium.org, Jul 5 2017 
Downloading recovery image from https://pantheon.corp.google.com/storage/browser/chromeos-releases/dev-channel/veyron-rialto/9715.0.0/,
the recovery image is invalid. The GPT table is corrupted because the kernel image starts at offset (bytes) 0xa00 (sector 5) instead of 00a00000 (sector 20480).

The test image in the same bucket is correct.

R50, R59 recovery images are also broken.

To verify, using other board like cyan, the kernel starts at the right offset in the recovery image, but veyron-minnie (https://pantheon.corp.google.com/storage/browser/chromeos-releases/dev-channel/veyron-minnie/7978.42.0/) is incorrect as well.

Comment 1 by gwendal@chromium.org, Jul 5 2017

Status: WontFix (was: Untriaged)
The archives are actually fine, it is an archiver issue:
'tar xf' properly extracts these archives, but fileroller, the goobuntu archiver does not, see https://bugzilla.gnome.org/show_bug.cgi?id=747091
It has been fixed but we are still using 3.10.2.1 which does not seem to have the fix.

Comment 2 by gwendal@chromium.org, Jul 5 2017 

 tar xf ~/Downloads/dev-channel%2Fveyron-minnie%2F7978.42.0%2FChromeOS-recovery-R50-7978.42.0-veyron-minnie.tar.xz

produce:
-rw-r----- 1 gwendal eng 1535082496 Apr  4  2016 /usr/local/google/home/gwendal/Downloads/recovery_image.bin

fileroller with the same file:
-rw-r--r-- 1 gwendal eng  950403072 Apr  4  2016 /usr/local/google/home/gwendal/Downloads/recovery_image.bin

Comment 3 by gwendal@google.com, Jul 5 2017 

Bug fixed in file-roller 3.19.1
►

Sign in to add a comment