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

Issue 605587 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 0
Type: Bug



Sign in to add a comment

cros_make_image_bootable is failing on strago-release-group

Project Member Reported by denniskempin@chromium.org, Apr 21 2016

Issue description

Hi phobbs!

I noticed that cros_make_image_bootable is failing. There are a whole bunch of odd error messages that make me think it might be related to the builder having issues. 
If this is not an infra issue, please assign it back to me so I can find someone to investigate this failure. 

Log:
mount: /dev/loop3: can't read superblock
ERROR   : Thu Apr 21 06:50:13 PDT 2016
ERROR   :  PGID  PPID   PID     ELAPSED     TIME %CPU COMMAND
ERROR   : Arguments of 1707:  '--arch=amd64' '--to=/mnt/host/source/src/build/images/cyan/R52-8222.0.0/chromiumos_base_image.bin' '--from=/mnt/host/source/src/build/images/cyan/R52-8222.0.0/rootfs_dir/boot' '--vmlinuz=/mnt/host/source/src/build/images/cyan/R52-8222.0.0/rootfs_dir/boot/vmlinuz' '--to_offset=127926272' '--to_size=16777216' '--kernel_partition='/mnt/host/source/src/build/images/cyan/R52-8222.0.0/vmlinuz.image'' '--install_syslinux'
ERROR   : Backtrace:  (most recent call is last)
ERROR   :  update_bootloaders.sh:197:main(), called: die_err_trap  
ERROR   : 
ERROR   : Command failed:
ERROR   :   Command 'sudo mount -o ro "${ESP_DEV}" "${ESP_FS_DIR}"' exited with nonzero code: 32
umount: /tmp/esp.ZITuZp: not mounted
WARNING : Initial unmount failed. Possibly crosbug.com/23443. Retrying
umount: /tmp/esp.ZITuZp: not mounted
INFO    : Unmounting image from /mnt/host/source/src/build/images/cyan/R52-8222.0.0/stateful_dir and /mnt/host/source/src/build/images/cyan/R52-8222.0.0/rootfs_dir
Cleaning up /usr/local symlinks for /mnt/host/source/src/build/images/cyan/R52-8222.0.0/stateful_dir/dev_image
ERROR   : Thu Apr 21 06:50:24 PDT 2016
ERROR   :  PGID  PPID   PID     ELAPSED     TIME %CPU COMMAND
ERROR   : Arguments of 32459:  '/mnt/host/source/src/build/images/cyan/R52-8222.0.0' 'chromiumos_base_image.bin' '--adjust_part='
ERROR   : Backtrace:  (most recent call is last)
ERROR   :  cros_make_image_bootable:427:main(), called: make_image_bootable '/mnt/host/source/src/build/images/cyan/R52-8222.0.0/chromiumos_base_image.bin' 
ERROR   :  cros_make_image_bootable:1:make_image_bootable(), called: die 'cros_make_image_bootable failed.' 
ERROR   : 
ERROR   : Error was:
ERROR   :   cros_make_image_bootable failed.
06:50:25: ERROR: 
return code: 1; command: /b/cbuild/internal_master/chromite/bin/cros_sdk 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpYJlXLi' 'USE=-cros-debug chrome_internal afdo_use' 'FEATURES=separatedebug' 'CHROME_ORIGIN=LOCAL_SOURCE' -- ./build_image '--board=cyan' --replace '--version=8222.0.0' base test
cwd=/b/cbuild/internal_master, extra env={'PARALLEL_EMERGE_STATUS_FILE': '/tmp/tmpYJlXLi', 'USE': '-cros-debug chrome_internal afdo_use', 'FEATURES': 'separatedebug', 'CHROME_ORIGIN': 'LOCAL_SOURCE'}
Build: https://uberchromegw.corp.google.com/i/chromeos/builders/strago-release-group/builds/1101

 

Comment 1 by benhenry@google.com, Apr 26 2016

Components: Infra>Client>ChromeOS
Labels: -Infra-ChromeOS
Project Member

Comment 2 by sheriffbot@chromium.org, May 6 2016

Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable?

If a fix is in active development, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: pho...@chromium.org
Owner: shuqianz@chromium.org
Charlene, can you triage this?
Cc: chrome-troopers@google.com
Loop in the chrome infra troopers. Is it something wrong the build disk?
ount: /dev/loop3: can't read superblock
ERROR   : Thu Apr 21 06:50:13 PDT 2016
ERROR   :  PGID  PPID   PID     ELAPSED     TIME %CPU COMMAND
ERROR   : Arguments of 1707:  '--arch=amd64' '--to=/mnt/host/source/src/build/images/cyan/R52-8222.0.0/chromiumos_base_image.bin' '--from=/mnt/host/source/src/build/images/cyan/R52-8222.0.0/rootfs_dir/boot' '--vmlinuz=/mnt/host/source/src/build/images/cyan/R52-8222.0.0/rootfs_dir/boot/vmlinuz' '--to_offset=127926272' '--to_size=16777216' '--

Comment 5 by dnj@google.com, May 9 2016

Cc: -chrome-troopers@google.com
Owner: denniskempin@chromium.org
I think this is not an infra issue, since chrome infra team doesn't think it has something related to the builder.
Labels: rcissue
R51 Cyan just failed in a similar fashion

https://uberchromegw.corp.google.com/i/chromeos_release/builders/strago-release-group%20release-R51-8172.B/builds/23/steps/BuildImage%20%5Bcyan%5D%20%5Bafdo_use%5D/logs/stdio

Instead of a mount error it died on "ERROR   :   Command 'sudo syslinux -d /syslinux "${ESP_DEV}"' exited with nonzero code: 1" but the end result of cros_make_image_bootable failing is the same.

Any ideas on what may be going wrong here?
Project Member

Comment 10 by sheriffbot@chromium.org, May 20 2016

Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable?

If a fix is in active development, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Assigned)
Obsolete bugs

Sign in to add a comment